Bug 94628 - Xorg fails to thaw from hibernate with intel errors
Summary: Xorg fails to thaw from hibernate with intel errors
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-19 19:15 UTC by JM9
Modified: 2017-06-27 14:10 UTC (History)
1 user (show)

See Also:
i915 platform: HSW
i915 features: power/suspend-resume


Attachments
dmesg with drm.debug=0xe (125.85 KB, text/plain)
2016-05-27 17:51 UTC, JM9
no flags Details

Description JM9 2016-03-19 19:15:50 UTC
After a successful hibernation from X, attempting to thaw does not work.

Debugged using commands:

# echo devices > /sys/power/pm_test
# echo platform > /sys/power/disk
# echo disk > /sys/power/state

here is trace from demesg:

[  241.128358] PM: freeze of devices complete after 370.606 msecs
[  241.128361] hibernation debug: Waiting for 5 seconds.
[  246.225380] usb usb1: root hub lost power or was reset
[  246.225383] usb usb3: root hub lost power or was reset
[  246.225384] usb usb2: root hub lost power or was reset
[  246.225943] usb usb4: root hub lost power or was reset
[  246.229275] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[  246.229824] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[  246.230048] iwlwifi 0000:3d:00.0: L1 Enabled - LTR Enabled
[  246.230567] iwlwifi 0000:3d:00.0: L1 Enabled - LTR Enabled
[  246.231472] sd 0:0:0:0: [sda] Starting disk
[  246.231491] sd 4:0:0:0: [sdb] Starting disk
[  246.281850] ------------[ cut here ]------------
[  246.281871] WARNING: CPU: 3 PID: 85 at drivers/gpu/drm/i915/intel_uncore.c:619 hsw_unclaimed_reg_debug+0x69/0x90 [i915]()
[  246.281872] Unclaimed register detected after reading register 0x70008
[  246.281874] Modules linked in: sha256_ssse3 sha256_generic hmac drbg ansi_cprng ctr ccm mousedev joydev bbswitch(O) iTCO_wdt iTCO_vendor_support hp_wmi mxm_wmi ppdev arc4 sparse_keymap intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd input_leds psmouse pcspkr serio_raw i2c_i801 snd_hda_codec_realtek snd_hda_codec_generic iwlmvm tpm_infineon mac80211 iwlwifi rtsx_pci_ms lpc_ich memstick cfg80211 snd_hda_intel uvcvideo snd_hda_codec videobuf2_vmalloc snd_hda_core btusb videobuf2_memops videobuf2_v4l2 snd_hwdep btrtl snd_pcm videobuf2_core btbcm btintel v4l2_common bluetooth e1000e snd_timer videodev snd media rfkill soundcore ptp pps_core mei_me mei
[  246.281909]  shpchp ie31200_edac edac_core hp_accel led_class lis3lv02d input_polldev parport_pc thermal hp_wireless wmi parport fjes tpm_tis evdev battery tpm mac_hid ac processor sch_fq_codel nfs lockd grace sunrpc fscache acpi_call(O) ip_tables x_tables ext4 crc16 mbcache jbd2 sr_mod cdrom sd_mod rtsx_pci_sdmmc mmc_core atkbd libps2 ahci ehci_pci libahci libata i915 i2c_algo_bit scsi_mod xhci_pci drm_kms_helper syscopyarea sysfillrect sysimgblt ehci_hcd xhci_hcd fb_sys_fops rtsx_pci drm usbcore usb_common intel_gtt i8042 serio video button
[  246.281937] CPU: 3 PID: 85 Comm: kworker/u16:2 Tainted: G           O    4.4.5-1-ARCH #1
[  246.281938] Hardware name: Hewlett-Packard HP Zbook 17 G2/2255, BIOS M70 Ver. 01.12 09/23/2015
[  246.281942] Workqueue: events_unbound async_run_entry_fn
[  246.281944]  0000000000000086 000000005ffc1828 ffff880022073b50 ffffffff812cb391
[  246.281945]  ffff880022073b98 ffffffffa02e4b30 ffff880022073b88 ffffffff810776e2
[  246.281947]  ffff880888a70000 ffff880888a70080 0000000000000000 0000000000070008
[  246.281949] Call Trace:
[  246.281954]  [<ffffffff812cb391>] dump_stack+0x63/0x82
[  246.281957]  [<ffffffff810776e2>] warn_slowpath_common+0x82/0xc0
[  246.281959]  [<ffffffff8107777c>] warn_slowpath_fmt+0x5c/0x80
[  246.281968]  [<ffffffffa0254d79>] hsw_unclaimed_reg_debug+0x69/0x90 [i915]
[  246.281976]  [<ffffffffa0259901>] gen6_read32+0xd1/0x1c0 [i915]
[  246.281984]  [<ffffffffa025b0f0>] ? hsw_write64+0x160/0x160 [i915]
[  246.281994]  [<ffffffffa028014e>] intel_modeset_setup_hw_state+0x67e/0xdd0 [i915]
[  246.282003]  [<ffffffffa028355f>] intel_display_resume+0xff/0x150 [i915]
[  246.282009]  [<ffffffffa01ff1cb>] i915_drm_resume+0xcb/0x160 [i915]
[  246.282015]  [<ffffffffa01ff285>] i915_pm_resume+0x25/0x30 [i915]
[  246.282017]  [<ffffffff813117c9>] pci_pm_restore+0x79/0xb0
[  246.282019]  [<ffffffff81311750>] ? pci_pm_suspend_noirq+0x180/0x180
[  246.282022]  [<ffffffff813fb470>] dpm_run_callback+0x50/0x170
[  246.282023]  [<ffffffff813fba43>] device_resume+0xd3/0x1f0
[  246.282025]  [<ffffffff813fbb7d>] async_resume+0x1d/0x50
[  246.282027]  [<ffffffff81097b38>] async_run_entry_fn+0x48/0x150
[  246.282029]  [<ffffffff8108f5bb>] process_one_work+0x14b/0x480
[  246.282031]  [<ffffffff8108f938>] worker_thread+0x48/0x4a0
[  246.282033]  [<ffffffff8108f8f0>] ? process_one_work+0x480/0x480
[  246.282035]  [<ffffffff810953d8>] kthread+0xd8/0xf0
[  246.282037]  [<ffffffff81095300>] ? kthread_worker_fn+0x170/0x170
[  246.282039]  [<ffffffff8159743f>] ret_from_fork+0x3f/0x70
[  246.282040]  [<ffffffff81095300>] ? kthread_worker_fn+0x170/0x170
[  246.282041] ---[ end trace 2d8b1761ab26421e ]---
[  246.328529] pciehp 0000:3c:03.0:pcie24: Device 0000:5f:00.0 already exists at 0000:5f:00, cannot hot-add
[  246.328535] pciehp 0000:3c:03.0:pcie24: Cannot add device at 0000:5f:00
[  246.430537] iwlwifi 0000:3d:00.0: L1 Enabled - LTR Enabled
[  246.430972] iwlwifi 0000:3d:00.0: L1 Enabled - LTR Enabled
[  246.502254] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
Comment 1 Jani Nikula 2016-04-25 10:06:14 UTC
(In reply to JM9 from comment #0)
> After a successful hibernation from X, attempting to thaw does not work.

You don't specify the kernel version... please try v4.5 or v4.6-rc5 or later.

Please add drm.debug=14 module parameter, and attach dmesg all the way from boot to the problem.
Comment 2 JM9 2016-05-04 17:17:40 UTC
My kernel version is:
4.5.1-1-ARCH #1 SMP PREEMPT Thu Apr 14 19:19:32 CEST 2016 x86_64 GNU/Linux

I tried 4.6-rc5 as suggested. Still no dice.
Comment 3 Ville Syrjala 2016-05-25 19:50:42 UTC
Still need that dmesg with drm.debug=0xe...
Comment 4 JM9 2016-05-27 17:51:05 UTC
Created attachment 124131 [details]
dmesg with drm.debug=0xe

I've attached the full dmesg with elevated debug level.
Comment 5 JM9 2016-08-09 07:37:08 UTC
Is this information enough? It is a real pain when you lose state if notebook accidentally runs out of battery and hibernates. Any chance of this bug getting fixed?

Let me know if you need more logs/debug info.

thanks!
Comment 6 Ville Syrjala 2016-08-09 08:11:45 UTC
(In reply to JM9 from comment #4)
> Created attachment 124131 [details]
> dmesg with drm.debug=0xe
> 
> I've attached the full dmesg with elevated debug level.

Not seeing anything really wrong there. It seems to resume just find, and the display should be up and running.

I did notice that the backlight a perhaps a bit dim after resume:
[    8.231922] [drm:intel_panel_actually_set_backlight] set backlight PWM = 244
whereas before suspend it was at max (4882).

You may want to try to force it to the max to see if that "fixes" things for you:
# cat /sys/class/backlight/intel_backlight/max_brightness > /sys/class/backlight/intel_backlight/brightness

The unclaimed register errors look harmless (I think they might be coming from the code that resets the frame start delays, as that code doesn't do the necessary power domain checks).
Comment 7 JM9 2016-08-15 03:14:32 UTC
Unfortunately, that is not it. I get a black screen (looks like no backlight) when I thaw. I can't get the screen to turn on even entering commands blindly. I was hoping this way of simulating a hibernation (per kernel documentation) would turn up something. If the unclaimed registers has nothing to do with hibernation then I'm afraid I don't know how to get any useful info when the thaw turns up a blank screen.

Any help in trying to retrieve useful info will be appreciated.

journalctl --boot=-1 did not turn up anything suspicious.
Comment 8 Jari Tahvanainen 2017-03-28 13:02:35 UTC
We seem to have neglected the bug quite a bit, apologies.

jhnmlkvch9@gmail.com, since there has been quite a lot improvements pushed in kernel that will benefit to your system, please re-test with latest kernel and mark as REOPENED if you can reproduce (and attach kernel log) and RESOLVED/* if you cannot reproduce.

This same comment can be found in bug 93574.
Comment 9 Ricardo 2017-06-23 16:25:18 UTC
based on the lack of activity the bug will be closed as invalid. also a comment from Ville looks like is not a issue. If you encounter the problem again please make sure you open a new bug


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.