Bug 1184161 - [abrt] WARNING: CPU: 0 PID: 0 at drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xdb/0xf0 [i915]()
Summary: [abrt] WARNING: CPU: 0 PID: 0 at drivers/gpu/drm/i915/intel_display.c:9713 in...
Keywords:
Status: CLOSED DUPLICATE of bug 1168439
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:9d03c52ce3f9f18f89304961d06...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-20 17:17 UTC by wincc
Modified: 2015-05-27 15:04 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-05-27 15:04:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (70.77 KB, text/plain)
2015-01-20 17:17 UTC, wincc
no flags Details

Description wincc 2015-01-20 17:17:24 UTC
Additional info:
reporter:       libreport-2.2.3
WARNING: CPU: 0 PID: 0 at drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xdb/0xf0 [i915]()
Kicking stuck page flip: queued at 95076, now 95084
Modules linked in: ccm fuse ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw cpufreq_stats arc4 iwldvm mac80211 iTCO_wdt iTCO_vendor_support kvm_intel kvm snd_hda_codec_hdmi samsung_laptop snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller iwlwifi snd_hda_codec coretemp cfg80211 btusb snd_hwdep snd_seq bluetooth intel_rapl uvcvideo iosf_mbi x86_pkg_temp_thermal snd_seq_device videobuf2_vmalloc videobuf2_core uas joydev videobuf2_memops v4l2_common videodev r8169 snd_pcm usb_storage serio_raw mii media rfkill snd_timer mei_me tpm_tis tpm mei snd lpc_ich shpchp i2c_i801 soundcore mfd_core wmi btrfs xor raid6_pq dm_crypt i915 i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul drm crc32c_intel ghash_clmulni_intel video
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.19.0-0.rc4.git2.2.fc22.x86_64 #1
Hardware name: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D/NP900X3E-A01SE, BIOS P05ABK 02/26/2013
 0000000000000000 a48f326b34794995 ffff88011f203d08 ffffffff8176f3b2
 0000000000000000 ffff88011f203d60 ffff88011f203d48 ffffffff8109be5a
 ffff88011f203d48 ffff880036ce4800 ffff880036961000 0000000000000000
Call Trace:
 <IRQ>  [<ffffffff8176f3b2>] dump_stack+0x45/0x57
 [<ffffffff8109be5a>] warn_slowpath_common+0x8a/0xc0
 [<ffffffff8109bee5>] warn_slowpath_fmt+0x55/0x70
 [<ffffffffa0128d0b>] intel_check_page_flip+0xdb/0xf0 [i915]
 [<ffffffffa00f6838>] ironlake_irq_handler+0x428/0xff0 [i915]
 [<ffffffff8110464c>] ? __hrtimer_start_range_ns+0x2fc/0x450
 [<ffffffff810f34d7>] handle_irq_event_percpu+0x77/0x1a0
 [<ffffffff810f363b>] handle_irq_event+0x3b/0x60
 [<ffffffff810f681e>] handle_edge_irq+0x6e/0x120
 [<ffffffff81017594>] handle_irq+0x74/0x140
 [<ffffffff810bbdda>] ? atomic_notifier_call_chain+0x1a/0x20
 [<ffffffff81778b3f>] do_IRQ+0x4f/0xf0
 [<ffffffff8177692d>] common_interrupt+0x6d/0x6d
 <EOI>  [<ffffffff8160a216>] ? cpuidle_enter_state+0x66/0x160
 [<ffffffff8160a201>] ? cpuidle_enter_state+0x51/0x160
 [<ffffffff8160a3f7>] cpuidle_enter+0x17/0x20
 [<ffffffff810deaf1>] cpu_startup_entry+0x361/0x410
 [<ffffffff817649f7>] rest_init+0x77/0x80
 [<ffffffff81d4f02c>] start_kernel+0x4a4/0x4c5
 [<ffffffff81d4e120>] ? early_idt_handlers+0x120/0x120
 [<ffffffff81d4e4d7>] x86_64_start_reservations+0x2a/0x2c
 [<ffffffff81d4e62b>] x86_64_start_kernel+0x152/0x175

Comment 1 wincc 2015-01-20 17:17:29 UTC
Created attachment 981946 [details]
File: dmesg

Comment 3 Adam Jackson 2015-05-27 15:04:37 UTC

*** This bug has been marked as a duplicate of bug 1168439 ***


Note You need to log in before you can comment on or make changes to this bug.