Bug 1066662

Summary: [abrt] WARNING: CPU: 0 PID: 2767 at drivers/gpu/drm/i915/intel_uncore.c:125 gen6_gt_check_fifodbg.isra.9+0x38/0x50 [i915]()
Product: [Fedora] Fedora Reporter: Johan Broman <jbroman>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ajax, autarch, dspurek, gansalmon, h1k6zn2m, herve, itamar, jonathan, jrooth, kernel-maint, ksuzumur, madhu.chinakonda, rbinkhor, stefw, vijayvenkat4u, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/c89d3016f08c02bb7e8a7e3fdea8d04fee3346be
Whiteboard: abrt_hash:eaf709690a063133580ea9bc48228ef74356e6b5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-18 19:48:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: dmesg none

Description Johan Broman 2014-02-18 20:40:55 UTC 
Description of problem:
Resume after suspend.

Additional info:
reporter:       libreport-2.1.12
WARNING: CPU: 0 PID: 2767 at drivers/gpu/drm/i915/intel_uncore.c:125 gen6_gt_check_fifodbg.isra.9+0x38/0x50 [i915]()
MMIO read or write has been dropped ffffffff
Modules linked in: ccm rfcomm ip6t_rpfilter ip6t_REJECT 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 bnep snd_hda_codec_hdmi snd_hda_codec_conexant iTCO_wdt iTCO_vendor_support x86_pkg_temp_thermal coretemp snd_hda_intel kvm_intel snd_hda_codec arc4 kvm snd_hwdep iwldvm snd_seq uvcvideo microcode mac80211 videobuf2_vmalloc e1000e joydev videobuf2_memops serio_raw snd_seq_device videobuf2_core snd_pcm iwlwifi videodev sdhci_pci ptp media sdhci btusb pps_core cfg80211 snd_page_alloc bluetooth mmc_core i2c_i801 lpc_ich mfd_core snd_timer mei_me mei shpchp thinkpad_acpi snd tpm_tis wmi soundcore rfkill tpm nfsd auth_rpcgss nfs_acl lockd sunrpc dm_crypt i915 crct10dif_pclmul crc32_pclmul crc32c_intel i2c_algo_bit drm_kms_helper drm ghash_clmulni_intel i2c_core video
CPU: 0 PID: 2767 Comm: kworker/u16:6 Not tainted 3.13.3-201.fc20.x86_64 #1
Hardware name: LENOVO 4174BH4/4174BH4, BIOS 8CET58WW (1.38 ) 07/18/2013
Workqueue: i915 gen6_force_wake_work [i915]
 0000000000000009 ffff8800ba183d38 ffffffff81686b48 ffff8800ba183d80
 ffff8800ba183d70 ffffffff8106d47d ffff880036a28020 ffff880036a28028
 0000000000000216 ffff880036bd6700 0000000000000200 ffff8800ba183dd0
Call Trace:
 [<ffffffff81686b48>] dump_stack+0x45/0x56
 [<ffffffff8106d47d>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff8106d4ec>] warn_slowpath_fmt+0x4c/0x50
 [<ffffffff8109e157>] ? try_to_wake_up+0xe7/0x290
 [<ffffffffa0129b78>] gen6_gt_check_fifodbg.isra.9+0x38/0x50 [i915]
 [<ffffffffa0129bb8>] __gen6_gt_force_wake_put+0x28/0x30 [i915]
 [<ffffffffa0129947>] gen6_force_wake_work+0x37/0x50 [i915]
 [<ffffffff81087b86>] process_one_work+0x176/0x430
 [<ffffffff810887bb>] worker_thread+0x11b/0x3a0
 [<ffffffff810886a0>] ? rescuer_thread+0x350/0x350
 [<ffffffff8108f242>] kthread+0xd2/0xf0
 [<ffffffff8108f170>] ? insert_kthread_work+0x40/0x40
 [<ffffffff81695a7c>] ret_from_fork+0x7c/0xb0
 [<ffffffff8108f170>] ? insert_kthread_work+0x40/0x40
Comment 1 Johan Broman 2014-02-18 20:41:04 UTC 
Created attachment 864789 [details]
File: dmesg
Comment 2 Jonathan Kamens 2014-02-28 18:02:26 UTC 
This appears to be new in 3.13.3.

It has user-visible impact: it is impossible to change the brightness of the laptop screen after this occurs. The brightness controls move but do nothing.

It is probably related to bug 1032978.
Comment 4 Adam Jackson 2014-11-18 19:48:39 UTC 

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