Bug 91771 - [ivb] pm-hibernate leads to WARNING at drivers/gpu/drm/i915/intel_display.c:1656 ironlake_crtc_disable
Summary: [ivb] pm-hibernate leads to WARNING at drivers/gpu/drm/i915/intel_display.c:1...
Status: RESOLVED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: All Linux
: P3 normal
Assignee: intel-gfx-bugs@lists.freedesktop.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-22 10:16 UTC by Aaditya Bagga
Modified: 2015-02-05 16:09 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.10.64
Subsystem:
Regression: No
Bisected commit-id:


Attachments
part of dmesg.log (3.36 KB, text/plain)
2015-01-22 10:16 UTC, Aaditya Bagga
Details
new dmesg (103.16 KB, text/plain)
2015-02-05 16:07 UTC, Aaditya Bagga
Details

Description Aaditya Bagga 2015-01-22 10:16:21 UTC
Created attachment 164301 [details]
part of dmesg.log

Hello,
Comment 1 Aaditya Bagga 2015-01-22 10:26:53 UTC
Oops, forgot to write the text. It is as follows:

Whenever I hibernate, dmesg shows something about drivers/gpu/drm/i915/intel_display.c which looks like a crash (I have attached that part of the log).

This is reproducable, whenever I run pm-hibernate I get this message in dmesg.

This does not have any affect on my system state though; if I did not look at dmesg output I doubt I would have discovered it.

My system info is as follows:

dmesg
http://sprunge.us/TaMd

lspci -vnn
http://paste2.org/JKAUtaMg

inxi -Fxz
http://paste2.org/ZVGceWN7

I am on a laptop with integrated Intel HD 4000 graphics only.

Using pm-utils version 1.4.1 with upower version 0.9.23

$ pacman -Qs pm-utils
local/pm-quirks 0.20100619-4
    Quirks data for pm-utils
local/pm-utils 1.4.1-6
    Utilities and scripts for suspend and hibernate power management
local/upower-pm-utils 0.9.23-4 (eudev-base)
    Abstraction for enumerating power devices, listening to device events and querying history and statistics
local/xfce4-power-manager-pmu 1.4.2-1 (xfce4)
    Power manager for Xfce desktop, works with upower-pm-utils
Comment 2 Aaditya Bagga 2015-01-22 10:28:05 UTC
I think it would be better to post the relevant part of dmesg.log here for easier visibility:

[19531.870828] ------------[ cut here ]------------
[19531.870858] WARNING: at drivers/gpu/drm/i915/intel_display.c:1656 ironlake_crtc_disable+0x87b/0x890 [i915]()
[19531.870889] Modules linked in: usb_storage loop aufs xt_limit xt_pkttype ipt_REJECT xt_tcpudp xt_LOG xt_conntrack iptable_mangle iptable_nat nf_nat_ipv4 iptable_filter nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ip_tables x_tables nls_cp437 vfat fat vboxdrv(O) uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media ath3k btusb bluetooth i915 snd_hda_codec_hdmi snd_hda_codec_idt intel_agp intel_gtt joydev drm_kms_helper snd_hda_intel arc4 intel_powerclamp snd_hda_codec coretemp ath9k kvm_intel ath9k_common snd_hwdep kvm snd_pcm snd_page_alloc snd_timer crc32_pclmul snd soundcore crc32c_intel ghash_clmulni_intel ath9k_hw ath mac80211 cfg80211 rfkill aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper r8169 iTCO_wdt cryptd
[19531.870902]  iTCO_vendor_support mii drm evdev i2c_algo_bit shpchp i2c_core psmouse serio_raw mei_me mei lpc_ich wmi battery thermal video ac button mperf processor ext4 crc16 mbcache jbd2 sr_mod cdrom sd_mod ahci libahci libata scsi_mod xhci_hcd ehci_pci ehci_hcd usbcore usb_common
[19531.870904] CPU: 0 PID: 8988 Comm: kworker/u16:67 Tainted: G        W  O 3.10.64-1-MANJARO #1
[19531.870904] Hardware name: Hewlett-Packard HP ProBook 4440s/17F3, BIOS 68IRR Ver. F.50 08/04/2014
[19531.870908] Workqueue: events_unbound async_run_entry_fn
[19531.870910]  0000000000000009 ffff8801b51a7ae8 ffffffff814cdeb5 ffff8801b51a7b20
[19531.870912]  ffffffff81055931 ffff8801b1005000 ffff8801b09a4000 ffff8801b09a66d0
[19531.870913]  00000000000e0300 ffff8801b13b3000 ffff8801b51a7b30 ffffffff81055a0a
[19531.870913] Call Trace:
[19531.870917]  [<ffffffff814cdeb5>] dump_stack+0x19/0x1b
[19531.870920]  [<ffffffff81055931>] warn_slowpath_common+0x61/0x80
[19531.870921]  [<ffffffff81055a0a>] warn_slowpath_null+0x1a/0x20
[19531.870927]  [<ffffffffa0ac85bb>] ironlake_crtc_disable+0x87b/0x890 [i915]
[19531.870931]  [<ffffffffa0ac9ac8>] __intel_set_mode+0x4c8/0xd70 [i915]
[19531.870937]  [<ffffffffa0ad3c49>] intel_modeset_setup_hw_state+0x5e9/0xa60 [i915]
[19531.870939]  [<ffffffff814d01a2>] ? mutex_lock+0x12/0x30
[19531.870942]  [<ffffffffa0a9f247>] __i915_drm_thaw+0x117/0x1b0 [i915]
[19531.870946]  [<ffffffffa0a9f680>] i915_resume+0x70/0xc0 [i915]
[19531.870950]  [<ffffffffa0a9f6e6>] i915_pm_resume+0x16/0x20 [i915]
[19531.870953]  [<ffffffff812a8364>] pci_pm_restore+0x64/0xb0
[19531.870954]  [<ffffffff812a8300>] ? pci_pm_suspend_noirq+0x1a0/0x1a0
[19531.870957]  [<ffffffff8136e8d2>] dpm_run_callback+0x42/0x80
[19531.870958]  [<ffffffff8136f096>] device_resume+0xc6/0x1f0
[19531.870959]  [<ffffffff8136f1dd>] async_resume+0x1d/0x50
[19531.870960]  [<ffffffff81081247>] async_run_entry_fn+0x37/0x130
[19531.870962]  [<ffffffff81073ddc>] process_one_work+0x16c/0x400
[19531.870963]  [<ffffffff810747f2>] worker_thread+0x132/0x3e0
[19531.870964]  [<ffffffff810746c0>] ? manage_workers.isra.23+0x2e0/0x2e0
[19531.870966]  [<ffffffff8107a833>] kthread+0xd3/0xe0
[19531.870967]  [<ffffffff8107a760>] ? kthread_create_on_node+0x110/0x110
[19531.870969]  [<ffffffff814db3ec>] ret_from_fork+0x7c/0xb0
[19531.870970]  [<ffffffff8107a760>] ? kthread_create_on_node+0x110/0x110
[19531.870971] ---[ end trace c487f118761a583b ]---
[19531.870974] ------------[ cut here ]------------
Comment 3 Jani Nikula 2015-01-29 10:12:13 UTC
Please add drm.debug=14 module parameter and attach full dmesg from boot to reproducing the problem. Thanks.
Comment 4 Aaditya Bagga 2015-01-29 15:34:36 UTC
Sure.

http://sprunge.us/aTVM

Sequence:
boot -> pm-hibernate -> resume -> dmesg
Comment 5 Jani Nikula 2015-02-05 13:15:33 UTC
Mmh, the kernel's getting pretty old, can you try 3.18 or 3.19-rc7 please?
Comment 6 Aaditya Bagga 2015-02-05 16:07:18 UTC
Created attachment 165931 [details]
new dmesg
Comment 7 Aaditya Bagga 2015-02-05 16:09:02 UTC
I tried with 3.18 and did not get the crash in dmesg, so its solved I guess (dmesg output attached for reference).

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