Bug 86105 - [C220] Display goes blank with PCH PWM1 enabled warning in intel_display.c:7376/6900
Summary: [C220] Display goes blank with PCH PWM1 enabled warning in intel_display.c:73...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-10 11:08 UTC by Catalin Hritcu
Modified: 2017-07-24 22:50 UTC (History)
5 users (show)

See Also:
i915 platform: HSW
i915 features: power/Other


Attachments
results of uname -a (90 bytes, text/plain)
2014-11-10 11:08 UTC, Catalin Hritcu
no flags Details
results of lspci (1.90 KB, text/plain)
2014-11-10 11:09 UTC, Catalin Hritcu
no flags Details
results of lshw (17.71 KB, text/plain)
2014-11-10 11:10 UTC, Catalin Hritcu
no flags Details
results of xrandr (5.08 KB, text/plain)
2014-11-10 11:12 UTC, Catalin Hritcu
no flags Details
dmesg (default configuration, hope to obtain one with drm.debug=14 soon) (496.84 KB, text/plain)
2014-11-10 11:15 UTC, Catalin Hritcu
no flags Details
Xorg.0.log (146.23 KB, text/plain)
2014-11-10 11:16 UTC, Catalin Hritcu
no flags Details
dmesg (default configuration, turned drm.debug=14 on only at the very end of the trace, will try to produce a better trace as soon as problem happens again) (510.00 KB, text/plain)
2014-11-10 12:14 UTC, Catalin Hritcu
no flags Details
dmesg (drm.debug=14 + issuing 'xset dpms force off' at the end; problem not triggered) (2.23 MB, text/plain)
2014-11-19 10:20 UTC, Catalin Hritcu
no flags Details
i915_power_domain_info (860 bytes, text/plain)
2015-04-04 22:38 UTC, Wouter Van Hemel
no flags Details
system log output for one of the screen blanks (15.59 KB, text/plain)
2015-04-04 22:40 UTC, Wouter Van Hemel
no flags Details

Description Catalin Hritcu 2014-11-10 11:08:46 UTC
Created attachment 109208 [details]
results of uname -a

This bug report refers to the following intel-gfx thread:
http://lists.freedesktop.org/archives/intel-gfx/2014-November/055179.html

The problem starts intermittently at arbitrary intervals after I boot
the machine. With kernel 3.15 it was every couple of days, with kernel
3.17 every couple of weeks. The display goes blank, and moving the
mouse or typing on the keyboard brings everything back. So far this
might be just normal behavior (e.g. a screen server, although I have
disabled it). However, once the problem is triggered the screen can go
blank at any point when not typing or moving the mouse. So even after
stopping typing for a couple of seconds the screen could potentially
go blank and come back either on its own at some point or after typing
or moving the mouse again. Once this starts the only way to I know to
stop the arbitrary blanking is to reboot, which is hugely annoying.

Each time the screen goes blank because of this problem the following
gets printed to dmesg:
[649516.344356] ------------[ cut here ]------------
[649516.344360] WARNING: CPU: 2 PID: 7718 at
drivers/gpu/drm/i915/intel_display.c:7376 hsw_enable_pc8+0x633/0x640
[i915]()
[649516.344361] PCH PWM1 enabled
[649516.344361] Modules linked in: nls_utf8 udf crc_itu_t uas
usb_storage hid_generic usbhid hid nls_iso8859_1 nls_cp437 vfat fat
mmc_block ctr ccm fuse snd_hda_codec_hdmi joydev mousedev arc4
snd_hda_codec_realtek snd_hda_codec_generic ext4 uvcvideo
videobuf2_vmalloc videobuf2_memops videobuf2_core mbcache v4l2_common
videodev jbd2 media ecb coretemp intel_rapl x86_pkg_temp_thermal
intel_powerclamp btusb bluetooth crc16 kvm_intel iTCO_wdt iwlmvm
iTCO_vendor_support kvm mac80211 crct10dif_pclmul crc32_pclmul
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper
ablk_helper cryptd evdev iwlwifi mac_hid thinkpad_acpi serio_raw
psmouse nvram cfg80211 pcspkr i915 led_class rfkill hwmon tpm_tis
thermal rtsx_pci_ms tpm battery ac memstick wmi processor video
snd_hda_intel snd_hda_controller drm_kms_helper
[649516.344381]  snd_hda_codec drm e1000e snd_hwdep snd_pcm intel_gtt
snd_timer i2c_i801 i2c_algo_bit snd mei_me ie31200_edac ptp mei
i2c_core soundcore edac_core pps_core lpc_ich button shpchp pci_stub
vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) acpi_call(O) btrfs
xor raid6_pq sd_mod sr_mod cdrom crc_t10dif crct10dif_common
rtsx_pci_sdmmc mmc_core atkbd libps2 xhci_hcd ahci libahci
crc32c_intel libata ehci_pci ehci_hcd scsi_mod rtsx_pci usbcore
usb_common i8042 serio
[649516.344393] CPU: 2 PID: 7718 Comm: kworker/2:1 Tainted: G        W
 O   3.17.1-1-ARCH #1
[649516.344394] Hardware name: LENOVO 20ANCTO1WW/20ANCTO1WW, BIOS
GLET68WW (2.22 ) 03/24/2014
[649516.344395] Workqueue: pm pm_runtime_work
[649516.344396]  0000000000000000 0000000074ed01fa ffff880112517bf8
ffffffff81536850
[649516.344397]  ffff880112517c40 ffff880112517c30 ffffffff8107054d
ffff88041fe80000
[649516.344398]  ffff880422e44b58 ffff880422e44b68 ffff880422e44800
ffff880427e0e098
[649516.344400] Call Trace:
[649516.344401]  [<ffffffff81536850>] dump_stack+0x4d/0x6f
[649516.344403]  [<ffffffff8107054d>] warn_slowpath_common+0x7d/0xa0
[649516.344404]  [<ffffffff810705cc>] warn_slowpath_fmt+0x5c/0x80
[649516.344411]  [<ffffffffa0555093>] hsw_enable_pc8+0x633/0x640 [i915]
[649516.344415]  [<ffffffffa04faaa5>] intel_runtime_suspend+0x1a5/0x8c0 [i915]
[649516.344416]  [<ffffffff810136b2>] ? __switch_to+0x1b2/0x5e0
[649516.344419]  [<ffffffff812e64bf>] pci_pm_runtime_suspend+0x5f/0x150
[649516.344420]  [<ffffffff812e6460>] ? pci_legacy_suspend_late+0xe0/0xe0
[649516.344422]  [<ffffffff813b50d2>] __rpm_callback+0x32/0x70
[649516.344423]  [<ffffffff813b5136>] rpm_callback+0x26/0xa0
[649516.344425]  [<ffffffff813b5681>] rpm_suspend+0x121/0x680
[649516.344426]  [<ffffffff810d69e8>] ? add_timer+0x18/0x30
[649516.344428]  [<ffffffff81087d3b>] ? __queue_delayed_work+0x8b/0x1c0
[649516.344430]  [<ffffffff813b6efa>] pm_runtime_work+0x7a/0xd0
[649516.344431]  [<ffffffff81088b85>] process_one_work+0x145/0x400
[649516.344433]  [<ffffffff8108914b>] worker_thread+0x6b/0x4a0
[649516.344434]  [<ffffffff810890e0>] ? init_pwq.part.22+0x10/0x10
[649516.344435]  [<ffffffff8108e06a>] kthread+0xea/0x100
[649516.344437]  [<ffffffff81070000>] ? register_exec_domain+0x20/0xa0
[649516.344438]  [<ffffffff8108df80>] ? kthread_create_on_node+0x1b0/0x1b0
[649516.344440]  [<ffffffff8153c77c>] ret_from_fork+0x7c/0xb0
[649516.344441]  [<ffffffff8108df80>] ? kthread_create_on_node+0x1b0/0x1b0
[649516.344442] ---[ end trace 9bd13e838200ae2c ]---

The line number in intel_display.c has shifted between kernel 3.15
(line 6900) and 3.17 (line 7376), but, other than this, the problem
appears with both versions.

Seems that other people are having the problem too:
https://bbs.archlinux.org/viewtopic.php?pid=1465265
https://retrace.fedoraproject.org/faf/reports/372862/
https://retrace.fedoraproject.org/faf/reports/401310/
but I wasn't able to find any bug report about this.

So I've started gathering data about my configuration for filing a new
bug report. I'm on a Lenovo Thinkpad 440p using Intel HD Graphics 4600
integrated graphics card. The laptop also has an NVidia card inside,
but it's completely turned off (nvidia and nouveau drivers are
blacklisted in modprobe.conf).

-- chipset: C220
-- system architecture: x86_64
-- xf86-video-intel/xserver/mesa/libdrm version:
   xf86-video-intel 2.99.916
   X.Org X Server 1.16.1
   Mesa 10.3.3
   libdrm 2.4.58
-- kernel version: 3.17.1-1-ARCH
-- Linux distribution: Arch
-- Machine or mobo model: Lenovo ThinkPad T440p (product: 20ANCTO1WW)
-- Display connector: problem happens both with laptop's monitor and
   with external monitor connected over HDMI

I'm attaching further configuration information and logs. I don't have
any xorg.conf file. I'll try to produce a dmesg trace with drm.debug=14
as soon as this happens again. Please let me know what if there is any
additional information that would be useful for tracing or reproducing it.
Comment 1 Catalin Hritcu 2014-11-10 11:09:53 UTC
Created attachment 109209 [details]
results of lspci
Comment 2 Catalin Hritcu 2014-11-10 11:10:59 UTC
Created attachment 109210 [details]
results of lshw
Comment 3 Catalin Hritcu 2014-11-10 11:12:48 UTC
Created attachment 109213 [details]
results of xrandr
Comment 4 Catalin Hritcu 2014-11-10 11:15:01 UTC
Created attachment 109215 [details]
dmesg (default configuration, hope to obtain one with drm.debug=14 soon)
Comment 5 Catalin Hritcu 2014-11-10 11:16:28 UTC
Created attachment 109216 [details]
Xorg.0.log
Comment 6 Catalin Hritcu 2014-11-10 12:14:50 UTC
Created attachment 109217 [details]
dmesg (default configuration, turned drm.debug=14 on only at the very end of the trace, will try to produce a better trace as soon as problem happens again)
Comment 7 Daniel Vetter 2014-11-11 14:57:16 UTC
Can you please grab the output of the following files:

/sys/module/snd_hda_intel/parameters/power_save
/sys/bus/pci/devices/0000:00:03.0/power/control
/sys/devices/pci0000:00/0000:00:02.0/power/autosuspend_delay_ms
/sys/devices/pci0000:00/0000:00:02.0/power/control

For debugging pls set autosuspend_delay_ms to "0", all control files to "auto" and power_save to "1" with echo, e.g.

echo "1" > /sys/module/snd_hda_intel/parameters/power_save

If this is indeed a runtime pm bug then the above values should make it a lot easier to reproduce, which would be a good hint for further debugging.
Comment 8 Jani Nikula 2014-11-12 14:37:47 UTC
Possible dupe bug 86000.
Comment 9 Catalin Hritcu 2014-11-12 14:53:37 UTC
@Daniel:

Here Are the old values of these files:

$ cat /sys/module/snd_hda_intel/parameters/power_save
0
$ cat /sys/bus/pci/devices/0000:00:03.0/power/control
on
$ cat /sys/devices/pci0000:00/0000:00:02.0/power/autosuspend_delay_ms
10000
$ cat /sys/devices/pci0000:00/0000:00:02.0/power/control
on

I've now set them as you advised:

# echo "1" > /sys/module/snd_hda_intel/parameters/power_save
# echo "auto" > /sys/bus/pci/devices/0000:00:03.0/power/control
# echo "0" > /sys/devices/pci0000:00/0000:00:02.0/power/autosuspend_delay_ms
# echo "auto" > /sys/devices/pci0000:00/0000:00:02.0/power/control

Hope this will make this easier to reproduce. Will let you know as soon as it happens again.
Comment 10 Daniel Vetter 2014-11-19 10:03:25 UTC
Strange, the backtrace is in runtime pm code but with that config you shouldn't be able to do runtime pm. In any case with the new settings we should runtime pm much more aggressively.

Aside if this is really runtime pm then switching screens off with

$ xset force dpms off

while no one is using audio devices (at least no hdmi/dp audio) should go into runtime pm almost immediately. Mouse-wiggling will wake the screens as usual.

But we have tests for that so the actual bug is probably somewhere else.
Comment 11 Catalin Hritcu 2014-11-19 10:15:24 UTC
I've tried running the command you probably meant:

$ xset dpms force off

and indeed it blanks off the screen until moving the mouse.

This doesn't seem to trigger the bug though. I wasn't able to trigger it for a week now, but I've seen such "periods of silence" before.

I'll upload the dmesg output around the xset command.
Comment 12 Catalin Hritcu 2014-11-19 10:20:26 UTC
Created attachment 109720 [details]
dmesg (drm.debug=14 + issuing 'xset dpms force off' at the end; problem not triggered)
Comment 13 Daniel Vetter 2014-11-20 15:15:03 UTC
Once you have the bug again pls do the dpms command again. Just to check the theory that this is indeed a runtime pm issue. But yeah sounds like something else is the ingredient, which means this could get rather painful.
Comment 14 Lasse Dissing 2014-11-23 16:57:17 UTC
I have the exact same bug on my Macbook running Debian 3.16-2, except it happens every other day. Is there any logs or other info I can provide to help?
Comment 15 Catalin Hritcu 2014-12-12 17:41:48 UTC
(Un)fortunately I couldn't longer reproduce this for one whole month now. Lasse, can you provide a drm.debug=14 dmesg trace with this bug happening?

PS: Some of my packages got updated in the meanwhile, while others stayed the same:
Linux 3.17.4-1-ARCH (updated)
libdrm 2.4.58-1 (same)
Mesa 10.3.5 (updated)
xf86-video-intel 2.99.916 (same)
xorg-server 1.16.2.901 (same)
I'm not sure whether the updates has anything to do with this problem not happening in the last month though.
Comment 16 Wouter Van Hemel 2014-12-20 23:49:33 UTC
I have been experiencing the same bug the last months on Debian Testing (upcoming Jessie) with the stock kernel on a Thinkpad T440s.

After the computer has been on for a few days, the screen starts blanking out randomly every n seconds (say every 1-60 seconds); sometimes the contents re-appears by itself immediately, but it always comes back after pushing a button - as if a power-saving screensaver randomly triggers. The problem never goes away once it has manifested itself (until a reboot).

The logs show a warning at intel_display.c, line 7256 in my case.



root@debian:~# uname -a
Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.7-2 (2014-11-06) x86_64 GNU/Linux


root@debian:~# cat /sys/module/snd_hda_intel/parameters/power_save
0
root@debian:~# cat /sys/bus/pci/devices/0000:00:03.0/power/control
on
root@debian:~# cat /sys/devices/pci0000:00/0000:00:02.0/power/autosuspend_delay_ms
10000
root@debian:~# cat /sys/devices/pci0000:00/0000:00:02.0/power/control
on



Dec 20 17:21:59 debian kernel: ------------[ cut here ]------------
Dec 20 17:21:59 debian kernel: WARNING: CPU: 0 PID: 19001 at /build/linux-Y9HjRe/linux-3.16.7/drivers/gpu/drm/i915/intel_display.c:7256 hsw_enable_pc8+0x463/0x5e0 [i915]()
Dec 20 17:21:59 debian kernel: CRTC for pipe A enabled
Dec 20 17:21:59 debian kernel: Modules linked in: usb_storage nfnetlink_queue nfnetlink_log nfnetlink cpuid ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c dm_mod ctr ccm bnep binfmt_misc pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ecb uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common btusb videodev media bluetooth 6lowpan_iphc joydev btrfs xor iTCO_wdt iTCO_vendor_support mspro_block nls_utf8 nls_cp437 arc4 vfat fat rtsx_pci_sdmmc rtsx_pci_ms mmc_core memstick raid6_pq x86_pkg_temp_thermal intel_powerclamp intel_rapl coretemp kvm_intel kvm crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd
Dec 20 17:21:59 debian kernel:  evdev psmouse efi_pstore serio_raw pcspkr efivars i2c_i801 sg wmi iwlmvm mac80211 snd_hda_intel snd_hda_controller iwlwifi i915 cfg80211 ac battery ehci_pci thinkpad_acpi tpm_tis xhci_hcd ehci_hcd nvram rtsx_pci tpm e1000e drm_kms_helper snd_hda_codec rfkill drm snd_hwdep intel_smartconnect button snd_pcm video i2c_algo_bit i2c_core usbcore lpc_ich snd_timer ptp usb_common mfd_core pps_core mei_me shpchp snd mei soundcore processor fuse autofs4 ext4 crc16 mbcache jbd2 sd_mod crc_t10dif crct10dif_generic ahci crct10dif_pclmul crct10dif_common libahci libata scsi_mod thermal thermal_sys
Dec 20 17:21:59 debian kernel: CPU: 0 PID: 19001 Comm: kworker/0:0 Tainted: G        W  O  3.16.0-4-amd64 #1 Debian 3.16.7-2
Dec 20 17:21:59 debian kernel: Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET64WW (2.14 ) 11/12/2013
Dec 20 17:21:59 debian kernel: Workqueue: pm pm_runtime_work
Dec 20 17:21:59 debian kernel:  0000000000000009 ffffffff81506b43 ffff88011b75fca8 ffffffff81065717
Dec 20 17:21:59 debian kernel:  ffff880211aa0000 ffff88011b75fcf8 ffff880037af2b70 ffff880214c0d098
Dec 20 17:21:59 debian kernel:  0000000000000000 ffffffff8106577c ffffffffa0525824 ffff880200000020
Dec 20 17:21:59 debian kernel: Call Trace:
Dec 20 17:21:59 debian kernel:  [<ffffffff81506b43>] ? dump_stack+0x41/0x51
Dec 20 17:21:59 debian kernel:  [<ffffffff81065717>] ? warn_slowpath_common+0x77/0x90
Dec 20 17:21:59 debian kernel:  [<ffffffff8106577c>] ? warn_slowpath_fmt+0x4c/0x50
Dec 20 17:21:59 debian kernel:  [<ffffffffa04bdf02>] ? lpt_disable_clkout_dp+0x62/0xc0 [i915]
Dec 20 17:21:59 debian kernel:  [<ffffffffa04ce843>] ? hsw_enable_pc8+0x463/0x5e0 [i915]
Dec 20 17:21:59 debian kernel:  [<ffffffffa047a895>] ? intel_runtime_suspend+0x185/0x860 [i915]
Dec 20 17:21:59 debian kernel:  [<ffffffff812dfc89>] ? pci_pm_runtime_suspend+0x59/0x120
Dec 20 17:21:59 debian kernel:  [<ffffffff813a6fac>] ? __rpm_callback+0x2c/0x80
Dec 20 17:21:59 debian kernel:  [<ffffffff813a701f>] ? rpm_callback+0x1f/0x80
Dec 20 17:21:59 debian kernel:  [<ffffffff813a7187>] ? rpm_suspend+0x107/0x5f0
Dec 20 17:21:59 debian kernel:  [<ffffffff8107042a>] ? internal_add_timer+0x2a/0x70
Dec 20 17:21:59 debian kernel:  [<ffffffff81072667>] ? mod_timer+0x127/0x1e0
Dec 20 17:21:59 debian kernel:  [<ffffffff813a8622>] ? pm_runtime_work+0x72/0xa0
Dec 20 17:21:59 debian kernel:  [<ffffffff8107f4b2>] ? process_one_work+0x172/0x420
Dec 20 17:21:59 debian kernel:  [<ffffffff8107fb45>] ? worker_thread+0x115/0x520
Dec 20 17:21:59 debian kernel:  [<ffffffff81508f61>] ? __schedule+0x2b1/0x710
Dec 20 17:21:59 debian kernel:  [<ffffffff8107fa30>] ? rescuer_thread+0x2d0/0x2d0
Dec 20 17:21:59 debian kernel:  [<ffffffff81085ddd>] ? kthread+0xbd/0xe0
Dec 20 17:21:59 debian kernel:  [<ffffffff81085d20>] ? kthread_create_on_node+0x180/0x180
Dec 20 17:21:59 debian kernel:  [<ffffffff8150cb7c>] ? ret_from_fork+0x7c/0xb0
Dec 20 17:21:59 debian kernel:  [<ffffffff81085d20>] ? kthread_create_on_node+0x180/0x180
Dec 20 17:21:59 debian kernel: ---[ end trace 853201e081f87534 ]---
Comment 17 kamek 2014-12-30 06:11:38 UTC
I'm also experiencing this.
It only happens after a suspend and stops on reboot.

kamek [~] > uname -a
Linux ghost 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64 GNU/Linux


[ 6024.635003] ------------[ cut here ]------------
[ 6024.635009] WARNING: CPU: 3 PID: 3204 at drivers/gpu/drm/i915/intel_display.c:7376 hsw_enable_pc8+0x633/0x640 [i915]()
[ 6024.635010] PCH PWM1 enabled
[ 6024.635010] Modules linked in: msr cpufreq_stats fuse snd_hda_codec_hdmi iTCO_wdt iTCO_vendor_support nls_ascii nls_cp437 vfat fat ecb btusb bluetooth hid_generic joydev hid_apple mousedev uas usb_storage mac_hid evdev usbhid hid bcm5974 wl(PO) coretemp ip6t_REJECT intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel nf_log_ipv6 kvm xt_hl crct10dif_pclmul crc32_pclmul crc32c_intel ip6t_rt ghash_clmulni_intel applesmc led_class input_polldev hwmon aesni_intel cfg80211 aes_x86_64 lrw gf128mul glue_helper ablk_helper nf_conntrack_ipv6 cryptd nf_defrag_ipv6 pcspkr lpc_ich rfkill snd_hda_codec_cirrus i2c_i801 snd_hda_codec_generic i915 ipt_REJECT drm_kms_helper xt_comment snd_hda_intel snd_hda_controller sbs nf_log_ipv4 battery nf_log_common sbshc snd_hda_codec drm snd_hwdep intel_gtt i2c_algo_bit
[ 6024.635033]  snd_pcm ac apple_bl i2c_core video xt_LOG button mei_me snd_timer mei snd shpchp processor soundcore xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables sch_fq_codel ext4 crc16 mbcache jbd2 sd_mod crc_t10dif crct10dif_common ahci libahci libata scsi_mod xhci_hcd usbcore usb_common
[ 6024.635048] CPU: 3 PID: 3204 Comm: kworker/3:2 Tainted: P        W  O   3.17.6-1-ARCH #1
[ 6024.635049] Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS MBP111.88Z.0138.B11.1408291433 08/29/2014
[ 6024.635051] Workqueue: pm pm_runtime_work
[ 6024.635051]  0000000000000000 00000000f2be5ac9 ffff8802622bfbf8 ffffffff81537c3e
[ 6024.635053]  ffff8802622bfc40 ffff8802622bfc30 ffffffff8107079d ffff88025fed0000
[ 6024.635055]  ffff8802620b1b58 ffff8802620b1b68 ffff8802620b1800 ffff880263649098
[ 6024.635056] Call Trace:
[ 6024.635058]  [<ffffffff81537c3e>] dump_stack+0x4d/0x6f
[ 6024.635060]  [<ffffffff8107079d>] warn_slowpath_common+0x7d/0xa0
[ 6024.635062]  [<ffffffff8107081c>] warn_slowpath_fmt+0x5c/0x80
[ 6024.635070]  [<ffffffffa03d91a3>] hsw_enable_pc8+0x633/0x640 [i915]
[ 6024.635075]  [<ffffffffa037eaa5>] intel_runtime_suspend+0x1a5/0x8c0 [i915]
[ 6024.635077]  [<ffffffff810136b2>] ? __switch_to+0x1b2/0x5e0
[ 6024.635080]  [<ffffffff812e6cff>] pci_pm_runtime_suspend+0x5f/0x150
[ 6024.635083]  [<ffffffff812e6ca0>] ? pci_legacy_suspend_late+0xe0/0xe0
[ 6024.635085]  [<ffffffff813b5812>] __rpm_callback+0x32/0x70
[ 6024.635087]  [<ffffffff813b5876>] rpm_callback+0x26/0xa0
[ 6024.635089]  [<ffffffff813b5dc1>] rpm_suspend+0x121/0x680
[ 6024.635091]  [<ffffffff810d6db8>] ? add_timer+0x18/0x30
[ 6024.635093]  [<ffffffff81087fbb>] ? __queue_delayed_work+0x8b/0x1c0
[ 6024.635095]  [<ffffffff813b764a>] pm_runtime_work+0x7a/0xd0
[ 6024.635097]  [<ffffffff81088e05>] process_one_work+0x145/0x400
[ 6024.635099]  [<ffffffff810893cb>] worker_thread+0x6b/0x4a0
[ 6024.635101]  [<ffffffff81089360>] ? init_pwq.part.22+0x10/0x10
[ 6024.635103]  [<ffffffff8108e2ea>] kthread+0xea/0x100
[ 6024.635105]  [<ffffffff81070000>] ? unregister_exec_domain+0x50/0x90
[ 6024.635106]  [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
[ 6024.635108]  [<ffffffff8153dbbc>] ret_from_fork+0x7c/0xb0
[ 6024.635110]  [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
[ 6024.635111] ---[ end trace 6754af2bd15a3ada ]---
Comment 18 Jani Nikula 2014-12-30 07:50:02 UTC
Shot in the dark, please attach /sys/kernel/debug/dri/0/i915_power_domain_info when this happens.
Comment 19 kamek 2014-12-31 04:40:32 UTC
Here we go again :



kamek [~] > dmesg
[ 1306.813242] ------------[ cut here ]------------
[ 1306.813252] WARNING: CPU: 0 PID: 4 at drivers/gpu/drm/i915/intel_display.c:7376 hsw_enable_pc8+0x633/0x640 [i915]()
[ 1306.813253] PCH PWM1 enabled
[ 1306.813254] Modules linked in: msr cpufreq_stats fuse snd_hda_codec_hdmi nls_ascii nls_cp437 vfat fat ecb btusb bluetooth hid_generic joydev mousedev hid_apple coretemp intel_rapl x86_pkg_temp_thermal intel_powerclamp iTCO_wdt iTCO_vendor_support wl(PO) kvm_intel kvm bcm5974 evdev crct10dif_pclmul crc32_pclmul crc32c_intel usbhid hid mac_hid ghash_clmulni_intel ip6t_REJECT nf_log_ipv6 applesmc aesni_intel led_class input_polldev hwmon aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd xt_hl pcspkr snd_hda_codec_cirrus cfg80211 snd_hda_codec_generic ip6t_rt i915 rfkill i2c_i801 lpc_ich shpchp nf_conntrack_ipv6 nf_defrag_ipv6 drm_kms_helper snd_hda_intel snd_hda_controller drm snd_hda_codec ipt_REJECT intel_gtt snd_hwdep i2c_algo_bit sbs mei_me snd_pcm battery i2c_core sbshc xt_comment mei snd_timer
[ 1306.813292]  snd nf_log_ipv4 nf_log_common soundcore video apple_bl processor ac button xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables sch_fq_codel ext4 crc16 mbcache jbd2 sd_mod crc_t10dif crct10dif_common uas usb_storage ahci libahci libata scsi_mod xhci_hcd usbcore usb_common
[ 1306.813314] CPU: 0 PID: 4 Comm: kworker/0:0 Tainted: P        W  O   3.17.6-1-ARCH #1
[ 1306.813316] Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS MBP111.88Z.0138.B11.1408291433 08/29/2014
[ 1306.813319] Workqueue: pm pm_runtime_work
[ 1306.813320]  0000000000000000 000000009482c0e9 ffff880263a8bbf8 ffffffff81537c3e
[ 1306.813323]  ffff880263a8bc40 ffff880263a8bc30 ffffffff8107079d ffff88025e5b0000
[ 1306.813325]  ffff88026248a358 ffff88026248a368 ffff88026248a000 ffff880263649098
[ 1306.813328] Call Trace:
[ 1306.813331]  [<ffffffff81537c3e>] dump_stack+0x4d/0x6f
[ 1306.813334]  [<ffffffff8107079d>] warn_slowpath_common+0x7d/0xa0
[ 1306.813337]  [<ffffffff8107081c>] warn_slowpath_fmt+0x5c/0x80
[ 1306.813350]  [<ffffffffa03fd1a3>] hsw_enable_pc8+0x633/0x640 [i915]
[ 1306.813358]  [<ffffffffa03a2aa5>] intel_runtime_suspend+0x1a5/0x8c0 [i915]
[ 1306.813361]  [<ffffffff810136b2>] ? __switch_to+0x1b2/0x5e0
[ 1306.813366]  [<ffffffff812e6cff>] pci_pm_runtime_suspend+0x5f/0x150
[ 1306.813369]  [<ffffffff812e6ca0>] ? pci_legacy_suspend_late+0xe0/0xe0
[ 1306.813373]  [<ffffffff813b5812>] __rpm_callback+0x32/0x70
[ 1306.813376]  [<ffffffff813b5876>] rpm_callback+0x26/0xa0
[ 1306.813380]  [<ffffffff813b5dc1>] rpm_suspend+0x121/0x680
[ 1306.813383]  [<ffffffff810d6db8>] ? add_timer+0x18/0x30
[ 1306.813386]  [<ffffffff81087fbb>] ? __queue_delayed_work+0x8b/0x1c0
[ 1306.813390]  [<ffffffff813b764a>] pm_runtime_work+0x7a/0xd0
[ 1306.813393]  [<ffffffff81088e05>] process_one_work+0x145/0x400
[ 1306.813396]  [<ffffffff810893cb>] worker_thread+0x6b/0x4a0
[ 1306.813399]  [<ffffffff81089360>] ? init_pwq.part.22+0x10/0x10
[ 1306.813402]  [<ffffffff8108e2ea>] kthread+0xea/0x100
[ 1306.813404]  [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
[ 1306.813408]  [<ffffffff8153dbbc>] ret_from_fork+0x7c/0xb0
[ 1306.813410]  [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
[ 1306.813412] ---[ end trace c6138abb0f381238 ]---



kamek [~] > sudo cat /sys/kernel/debug/dri/0/i915_power_domain_info
Power well/domain         Use count
always-on                 0
  PIPE_A                  1
  TRANSCODER_EDP          1
  PORT_DDI_A_2_LANES      0
  PORT_DDI_A_4_LANES      -2
  PORT_DDI_B_2_LANES      0
  PORT_DDI_B_4_LANES      0
  PORT_DDI_C_2_LANES      0
  PORT_DDI_C_4_LANES      0
  PORT_DDI_D_2_LANES      0
  PORT_DDI_D_4_LANES      0
  PORT_CRT                0
  PLLS                    0
  INIT                    0
display                   0
  PIPE_B                  0
  PIPE_C                  0
  PIPE_A_PANEL_FITTER     0
  PIPE_B_PANEL_FITTER     0
  PIPE_C_PANEL_FITTER     0
  TRANSCODER_A            0
  TRANSCODER_B            0
  TRANSCODER_C            0
  PORT_DSI                0
  PORT_OTHER              0
  VGA                     0
  AUDIO                   0
  INIT                    0
Comment 20 Kiril Vladimiroff 2015-01-28 12:05:36 UTC
Just to confirm that I can reproduce it on 3.18, too. I could provide additional info if you need more.
Comment 21 Catalin Hritcu 2015-01-28 12:55:33 UTC
@Kiril: Yes, please provide the versions of all the relevant packages + a dmesg trace with drm.debug=14. I can no longer reproduce this myself.
Comment 22 Kiril Vladimiroff 2015-02-02 09:34:11 UTC
Two days ago I've upgraded to 3.18.4. Since then I haven't experienced this. It was either fixed or I'm just being lucky so far.

If it happens again however will provide information about it.
Comment 23 Wouter Van Hemel 2015-04-04 22:38:09 UTC
Created attachment 114870 [details]
i915_power_domain_info

i915_power_domain_info values when screen is blanking randomly.
Comment 24 Wouter Van Hemel 2015-04-04 22:40:10 UTC
Created attachment 114871 [details]
system log output for one of the screen blanks

system log output that goes with the previous i915_power_domain_info attachment.
Comment 25 Jani Nikula 2015-10-23 10:20:35 UTC
Presumed fixed upstream, closing. Please reopen if the problem persists with latest kernels.
Comment 26 Catalin Hritcu 2015-10-23 10:26:55 UTC
Didn't encounter this problem any more since January 2015, seems indeed fair to close it.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.