Bug 108108 - kernel: [drm:i915_gem_idle_work_handler [i915]] *ERROR* Timeout waiting for engines to idle
Summary: kernel: [drm:i915_gem_idle_work_handler [i915]] *ERROR* Timeout waiting for e...
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: Triaged
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-01 06:08 UTC by shaleen.jain95
Modified: 2018-12-28 09:14 UTC (History)
1 user (show)

See Also:
i915 platform: KBL
i915 features:

Attachments

Description shaleen.jain95 2018-10-01 06:08:33 UTC 
GPU hangs after the laptop lid is opened while is system is already running.
The display never turns on or remains black forcing me to hard reset the system.
No `/sys/class/drm/card0/error` was created or lost after reboot.

$ uname -m
x86_64

$ uname -r
4.14.72-1-lts

Linux distribution: Arch Linux
Mesa: 18.2.1-1

dmesg:
pipe A vblank wait timed out
Oct 01 11:20:49 shalzz-galp2 kernel: ------------[ cut here ]------------
Oct 01 11:20:49 shalzz-galp2 kernel: WARNING: CPU: 1 PID: 1859 at drivers/gpu/drm/i915/intel_display.c:12202 intel_atomic_commit_tail.col>
Oct 01 11:20:49 shalzz-galp2 kernel: Modules linked in: loop udf crc_itu_t snd_seq_dummy snd_seq snd_seq_device nls_utf8 isofs sd_mod uas>
Oct 01 11:20:49 shalzz-galp2 kernel:  iwlwifi snd_hda_core i2c_algo_bit drm_kms_helper snd_hwdep aesni_intel drm aes_x86_64 crypto_simd g>
Oct 01 11:20:49 shalzz-galp2 kernel: CPU: 1 PID: 1859 Comm: systemd-logind Tainted: G           O    4.14.72-1-lts #1
Oct 01 11:20:49 shalzz-galp2 kernel: Hardware name: System76 Galago Pro/Galago Pro, BIOS 1.05.12-0 09/05/2018
Oct 01 11:20:49 shalzz-galp2 kernel: task: ffff88c0e6b2bb00 task.stack: ffffb464c381c000
Oct 01 11:20:49 shalzz-galp2 kernel: RIP: 0010:intel_atomic_commit_tail.cold.188+0x12b/0x132 [i915]
Oct 01 11:20:49 shalzz-galp2 kernel: RSP: 0018:ffffb464c381f920 EFLAGS: 00010246
Oct 01 11:20:49 shalzz-galp2 kernel: RAX: 000000000000001c RBX: 0000000000000000 RCX: 000000000000001c
Oct 01 11:20:49 shalzz-galp2 kernel: RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000246
Oct 01 11:20:49 shalzz-galp2 kernel: RBP: ffff88c0e4b18000 R08: 00001c22ebd66a6a R09: 000000000000001c
Oct 01 11:20:49 shalzz-galp2 kernel: R10: 00000000000006d9 R11: 000000000005d970 R12: 0000000000000000
Oct 01 11:20:49 shalzz-galp2 kernel: R13: ffff88c0e377c800 R14: 00000000002f570e R15: 0000000000000001
Oct 01 11:20:49 shalzz-galp2 kernel: FS:  00007f55a8da0940(0000) GS:ffff88c0fec80000(0000) knlGS:0000000000000000
Oct 01 11:20:49 shalzz-galp2 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 01 11:20:49 shalzz-galp2 kernel: CR2: 00007ffcefb87fc8 CR3: 00000005649c0002 CR4: 00000000003606e0
Oct 01 11:20:49 shalzz-galp2 kernel: Call Trace:
Oct 01 11:20:49 shalzz-galp2 kernel:  ? wait_woken+0x80/0x80
Oct 01 11:20:49 shalzz-galp2 kernel:  intel_atomic_commit+0x1d7/0x230 [i915]
Oct 01 11:20:49 shalzz-galp2 kernel:  restore_fbdev_mode_atomic+0x188/0x1f0 [drm_kms_helper]
Oct 01 11:20:49 shalzz-galp2 kernel:  drm_fb_helper_restore_fbdev_mode_unlocked.part.32+0x23/0x70 [drm_kms_helper]
Oct 01 11:20:49 shalzz-galp2 kernel:  drm_fb_helper_set_par+0x41/0x70 [drm_kms_helper]
Oct 01 11:20:49 shalzz-galp2 kernel:  intel_fbdev_set_par+0x16/0x60 [i915]
Oct 01 11:20:49 shalzz-galp2 kernel:  fb_set_var+0x212/0x3e0
Oct 01 11:20:49 shalzz-galp2 kernel:  fbcon_blank+0x24b/0x320
Oct 01 11:20:49 shalzz-galp2 kernel:  do_unblank_screen+0x9b/0x150
Oct 01 11:20:49 shalzz-galp2 kernel:  vt_ioctl+0x36c/0x11b0
Oct 01 11:20:49 shalzz-galp2 kernel:  tty_ioctl+0x21c/0x880
Oct 01 11:20:49 shalzz-galp2 kernel:  ? __seccomp_filter+0x3b/0x250
Oct 01 11:20:49 shalzz-galp2 kernel:  ? tty_unlock+0x21/0x30
Oct 01 11:20:49 shalzz-galp2 kernel:  do_vfs_ioctl+0xa4/0x610
Oct 01 11:20:49 shalzz-galp2 kernel:  ? syscall_trace_enter+0xd6/0x270
Oct 01 11:20:49 shalzz-galp2 kernel:  SyS_ioctl+0x74/0x80
Oct 01 11:20:49 shalzz-galp2 kernel:  do_syscall_64+0x67/0x100
Oct 01 11:20:49 shalzz-galp2 kernel:  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Oct 01 11:20:49 shalzz-galp2 kernel: RIP: 0033:0x7f55abcf779b
Oct 01 11:20:49 shalzz-galp2 kernel: RSP: 002b:00007ffdb607a258 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Oct 01 11:20:49 shalzz-galp2 kernel: RAX: ffffffffffffffda RBX: 000055a2f23f72d0 RCX: 00007f55abcf779b
Oct 01 11:20:49 shalzz-galp2 kernel: RDX: 0000000000000000 RSI: 0000000000004b3a RDI: 000000000000000c
Oct 01 11:20:49 shalzz-galp2 kernel: RBP: 000000000000000c R08: 00007ffdb607a190 R09: 0000000000000002
Oct 01 11:20:49 shalzz-galp2 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000024
Oct 01 11:20:49 shalzz-galp2 kernel: R13: 00007ffdb607a370 R14: 00007f55a8da0858 R15: 00007ffdb607a390
Oct 01 11:20:49 shalzz-galp2 kernel: Code: 0f 0b e9 a4 bf f8 ff 48 c7 c7 f5 8a b9 c0 e8 30 35 58 c6 0f 0b e9 74 be f8 ff 41 8d 74 24 41 4>
Oct 01 11:20:49 shalzz-galp2 kernel: ---[ end trace cd5bbcdd837c2757 ]---
Comment 1 Chris Wilson 2018-10-01 07:18:39 UTC 
Please use a recent kernel.
Comment 2 shaleen.jain95 2018-10-01 07:39:33 UTC 
Hi,

This is a LTS kernel, I don't see why I should more away from an LTS kernel because of a bug like this.

If the bug fix is not backported please backport it or atleast point to the fix so that it can be backported at the disto-level.
Comment 3 Chris Wilson 2018-10-01 10:00:12 UTC 
Your LTS is over a year behind in bugfixes. You are welcome to maintain it, but it is not upsteam.
Comment 4 Lakshmi 2018-10-16 08:19:05 UTC 
Shaleen, Have you verified with latest kernel? If not Please try to reproduce the issue using drm-tip (https://cgit.freedesktop.org/drm-tip).
If problem exists with latest drm-tip, set kernel parameters drm.debug=0x1e log_buf_len=4M and reboot.
Try to reproduce the issue and attach the dmesg log. This way we see more information about the bug.
Comment 5 Francesco Balestrieri 2018-12-28 09:14:12 UTC 
Closing with no feedback from the reporter, please reopen if you think the issue persists.

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.