Bug 104614 - Display change after hibernate locks the system
Summary: Display change after hibernate locks the system
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-12 23:39 UTC by Ilya
Modified: 2018-11-13 13:47 UTC (History)
1 user (show)

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


Attachments
dmesg output (230.71 KB, text/plain)
2018-01-16 09:59 UTC, Ilya
no flags Details
cpu info (4.48 KB, text/plain)
2018-01-16 22:29 UTC, Ilya
no flags Details
dmesg from kernel 4.13.0 (256.61 KB, text/plain)
2018-07-26 11:09 UTC, Ilya
no flags Details
System info (3.21 KB, text/plain)
2018-07-27 14:22 UTC, Ilya
no flags Details

Description Ilya 2018-01-12 23:39:31 UTC
Notebook: Thinkpad T470s
OS: Linux Mint 18.3
Kernel: 4.13.0-26-generic
Video: 00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02)


To reproduce the problem:

1. Hibernate the system
2. Put it to the dockstation
3. Start the system.

The display appears black, nothing is showing. 
The notebook display is not working in X, but you can switch to the console. Some errors are printed from the kernel (to be submitted... :)

The other way:

1. hibernate
2. put off the dock
3. start

and nothing works. Need to shutdown the notebook with a power knob.


The problem seems to be a regression, because 3-4 weeks ago it was working a lot better. The symptoms of this bug appeared only 1 time of 5-6 times.
Comment 1 Ilya 2018-01-15 12:29:36 UTC
The bug depends on kernel and not on dockstation. I tried now the hibernating without dock station and it hangs.

The older kernel (4.10.0) works fine.

So, this bug can be closed...
Comment 2 Ilya 2018-01-16 09:59:48 UTC
Created attachment 136747 [details]
dmesg output
Comment 3 Ilya 2018-01-16 10:00:40 UTC
Just now the system have hanged on 4.10.0 kernel. The dmesg output seems to be the same as fot 4.13.0 kernel. I attached it.
Comment 4 Elizabeth 2018-01-16 15:50:30 UTC
Hello Ilya, 
Is your device an SNB? If that't the case could you try: https://bugs.freedesktop.org/show_bug.cgi?id=103712#c41?
Thanks.

[124655.711484] WARNING: CPU: 0 PID: 1149 at /build/linux-hwe-0vY49E/linux-hwe-4.10.0/drivers/gpu/drm/i915/intel_display.c:14179 intel_atomic_commit_tail+0xfe4/0x1010 [i915]
[124655.711484] pipe A vblank wait timed out
[124655.711485] Modules linked in: nfnetlink_queue nfnetlink_log nfnetlink hid_generic snd_seq_dummy snd_usb_audio snd_usbmidi_lib acpi_call(OE) rfcomm ccm snd_hda_codec_hdmi uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core btusb videodev btrtl media hid_multitouch bnep binfmt_misc snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_sst_match nls_iso8859_1 arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_codec_realtek pcbc snd_hda_codec_generic aesni_intel snd_soc_core aes_x86_64 crypto_simd glue_helper cryptd iwlmvm snd_compress ac97_bus snd_pcm_dmaengine mac80211 snd_hda_intel snd_hda_codec snd_seq_midi snd_seq_midi_event snd_rawmidi snd_hda_core
[124655.711504]  snd_seq snd_hwdep iwlwifi input_leds joydev snd_pcm serio_raw snd_seq_device cfg80211 thinkpad_acpi snd_timer nvram mei_me shpchp mei snd intel_pch_thermal ucsi hci_uart soundcore btbcm btqca btintel bluetooth intel_lpss_acpi intel_lpss acpi_pad mac_hid parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log usbhid uas usb_storage i915 i2c_algo_bit psmouse drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp nvme pps_core drm nvme_core wmi pinctrl_sunrisepoint pinctrl_intel i2c_hid video hid fjes
[124655.711524] CPU: 0 PID: 1149 Comm: Xorg Tainted: G        W  OE   4.10.0-42-generic #46~16.04.1-Ubuntu
[124655.711525] Hardware name: LENOVO 20HFCTO1WW/20HFCTO1WW, BIOS N1WET41W (1.20 ) 10/17/2017
[124655.711525] Call Trace:
[124655.711528]  dump_stack+0x63/0x90
[124655.711530]  __warn+0xcb/0xf0
[124655.711531]  warn_slowpath_fmt+0x5f/0x80
[124655.711532]  ? finish_wait+0x56/0x70
[124655.711546]  intel_atomic_commit_tail+0xfe4/0x1010 [i915]
[124655.711548]  ? __switch_to+0x3dc/0x530
[124655.711549]  ? wake_atomic_t_function+0x60/0x60
[124655.711561]  intel_atomic_commit+0x3f2/0x520 [i915]
[124655.711569]  drm_atomic_commit+0x4b/0x50 [drm]
[124655.711573]  drm_atomic_helper_set_config+0x82/0xc0 [drm_kms_helper]
[124655.711579]  drm_mode_set_config_internal+0x65/0x110 [drm]
[124655.711584]  drm_mode_setcrtc+0x429/0x4f0 [drm]
[124655.711588]  drm_ioctl+0x21b/0x4d0 [drm]
[124655.711589]  ? __set_task_blocked+0x3c/0xa0
[124655.711594]  ? drm_mode_getcrtc+0x140/0x140 [drm]
[124655.711595]  ? dput+0x34/0x250
[124655.711597]  do_vfs_ioctl+0xa1/0x5f0
[124655.711598]  ? ____fput+0xe/0x10
[124655.711599]  ? task_work_run+0x83/0xa0
[124655.711600]  SyS_ioctl+0x79/0x90
[124655.711602]  entry_SYSCALL_64_fastpath+0x1e/0xad
[124655.711603] RIP: 0033:0x7f1b77d17f07
[124655.711603] RSP: 002b:00007ffcbe3b92e8 EFLAGS: 00003246 ORIG_RAX: 0000000000000010
[124655.711604] RAX: ffffffffffffffda RBX: 00000000000002a8 RCX: 00007f1b77d17f07
[124655.711605] RDX: 00007ffcbe3b93e0 RSI: 00000000c06864a2 RDI: 000000000000000a
[124655.711605] RBP: 0000000000000030 R08: 0000000000000000 R09: 1999999999999999
[124655.711605] R10: 0000000000000000 R11: 0000000000003246 R12: 0000000000000003
[124655.711606] R13: 0000000000000000 R14: 00007f1b79e20000 R15: 000056209125e810
[124655.711607] ---[ end trace a3172a85157e41a0 ]---
[124665.895510] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:31:pipe A] flip_done timed out
[124676.135541] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:31:pipe A] flip_done timed out
Comment 5 Ilya 2018-01-16 15:53:51 UTC
(In reply to Elizabeth from comment #4)
> Hello Ilya, 
> Is your device an SNB?

What is SNB? And how can I check it?
Comment 6 Elizabeth 2018-01-16 16:10:05 UTC
(In reply to Ilya from comment #5)
> (In reply to Elizabeth from comment #4)
> > Hello Ilya, 
> > Is your device an SNB?
> 
> What is SNB? And how can I check it?
Sandy bridge, by your intel core info at https://ark.intel.com
And for the kernel: https://www.kernel.org
Comment 7 Ilya 2018-01-16 22:29:18 UTC
I have i7 7500U, but I can't find, if it has sandy bridge or not. I attach cpuinfo
Comment 8 Ilya 2018-01-16 22:29:39 UTC
Created attachment 136795 [details]
cpu info
Comment 9 Ilya 2018-01-17 12:20:05 UTC
(In reply to Elizabeth from comment #6)
> (In reply to Ilya from comment #5)
> > (In reply to Elizabeth from comment #4)
> > > Hello Ilya, 
> > > Is your device an SNB?


I looked precisely at the Intel web page. My CPU is not Sandy Bridge
Comment 10 Elizabeth 2018-01-17 17:22:15 UTC
Kabylake, indeed. Disregard comment 4, could you attach a dmesg with debug information, "drm.debug=0x1e log_bug_len=2M" parameters on grub command line. Thank you.
Comment 11 Jani Saarinen 2018-03-29 07:11:55 UTC
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 12 Jani Saarinen 2018-04-20 15:52:31 UTC
Closing, please re-open if still occurs.
Comment 13 Ilya 2018-07-26 11:09:23 UTC
Created attachment 140828 [details]
dmesg from kernel  4.13.0
Comment 14 Ilya 2018-07-26 11:11:51 UTC
(In reply to Elizabeth from comment #10)
> Kabylake, indeed. Disregard comment 4, could you attach a dmesg with debug
> information, "drm.debug=0x1e log_bug_len=2M" parameters on grub command
> line. Thank you.

Submitted.

Please, reopen. The bug is really annoying. And for the kernels up of 4.13.0-37 (37 is ubuntu/mint versioning) I'm not capable to use hibernate *and* suspend to ram too! Roughly speaking making the system unusable for my case (travel a lot with a notebook).
Comment 15 Radosław Szwichtenberg 2018-07-27 07:17:06 UTC
Please try to reproduce the error using drm-tip (https://cgit.freedesktop.org/drm-tip) and kernel parameters drm.debug=0x1e log_buf_len=4M, and if the problem persists attach the full dmesg from boot.

Thanks!
Comment 16 Ilya 2018-07-27 07:26:28 UTC
(In reply to Radosław Szwichtenberg from comment #15)
> Please try to reproduce the error using drm-tip
> (https://cgit.freedesktop.org/drm-tip) and kernel parameters drm.debug=0x1e
> log_buf_len=4M, and if the problem persists attach the full dmesg from boot.
> 
> Thanks!

what is drm-trip and how can I use it? Just compile and then?
Comment 17 Denis 2018-07-27 09:11:17 UTC
Hi Ilya, could you also print out these commands and paste outputs here?

cat /proc/meminfo
glxinfo -B
sudo Xorg -version

first one to see, how many RAM and swap do you have, second - to see your current mesa version and the last one - to see X version.
Also, do you use "auto login" to the system or have lock screen before?
_____________________
I have HP ZBook 14u G4 with 16 GB RAM (with 16 GB SWAP and ubuntu 16.04, which is should have same base packages with Mint 18.3), it is quite similar to your's. I configured hibernate using this manual 
>https://askubuntu.com/questions/768136/how-can-i-hibernate-on-ubuntu-16-04
and sending PC to hibernate using this command:
>sudo systemctl hibernate
I made about 10 tries (also tried your steps with dock station, I have it for my laptop) - and all the time laptop is booting up correctly. So I need additional information from you.
Comment 18 Ilya 2018-07-27 14:22:24 UTC
Created attachment 140857 [details]
System info
Comment 19 Ilya 2018-07-27 14:22:59 UTC
(In reply to Denis from comment #17)
> Hi Ilya, could you also print out these commands and paste outputs here?
> 
> cat /proc/meminfo
> glxinfo -B
> sudo Xorg -version
> 

I did submit it as "System info"
Comment 20 Denis 2018-07-30 10:27:23 UTC
could you please update your X to latest available?
https://forums.linuxmint.com/viewtopic.php?t=256149
here is a post, how to do this. In my case, I am using ubuntu with 1.19.6 X version (from ubuntu repo), and it works fine
Comment 21 Denis 2018-08-21 13:26:46 UTC
Any updates, Ilya?
Comment 22 Lakshmi 2018-09-11 09:35:47 UTC
Ilya, do you still have the issue?
Comment 23 Lakshmi 2018-09-12 07:15:14 UTC
Ilya, do you still have the issue with latest kernel?
Reducing the priority to medium as there is no feedback from the reporter from more than 1 month.
Comment 24 Ilya 2018-09-12 13:27:07 UTC
(In reply to Lakshmi from comment #22)
> Ilya, do you still have the issue?

I dont tested the newest kernels. Try to make it in the next time..
Comment 25 Lakshmi 2018-10-11 15:11:09 UTC
Ilya, Have you verified if this issue exists with latest kernel?
Comment 26 Lakshmi 2018-10-24 10:40:28 UTC
Ilya, any updates here?
Comment 27 Lakshmi 2018-11-13 13:47:08 UTC
Latest logs are asked 2 months ago, and no feedback for more than a month. I assume this issue didn't happen to you lately.

Ilya, If this issue persists with latest drm-tip https://cgit.freedesktop.org/drm-tip, please re-open this issue and send dmesg from boot with kernel parameters drm.debug=0x1e log_buf_len=4M?


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.