Bug#1110854: linux-image-amd64: i915 timeout errors after kernel upgrade
Hi there,
I experimented a bit further trying to find a workaround.
First I noticed that there is even a kernel warning about the hangig
task (see attached log file):
INFO: task Xorg:1336 blocked for more than 1208 seconds.
I then tested various kernel options, without success:
* i915.modeset=0 (disables HDMI completely)
* intremap=off (no effect)
* module_blacklist.snd_hda_codec_hdmi (no effect)
* nomodeset (yields 640x480 only)
* ibt=off (no effect)
* i915.enable_dc=0 i915.enable_dp_mst=false (no effect)
Finally, I tested the old xserver-xorg-video-intel driver with success!
I just installed the package and added an Xorg config
in /etc/X11/xorg.conf.d/20-intel.conf:
Section "Device"
Identifier "Intel"
Driver "intel"
EndSection
So, the basic issue definitely seems to be related to the newer driver
used by default.
Best,
Maximilian
[ 2055.368532] INFO: task Xorg:1336 blocked for more than 1208 seconds.
[ 2055.368574] Tainted: G W 6.12.43+deb12-amd64 #1 Debian 6.12.43-1~bpo12+1
[ 2055.368593] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2055.368604] task:Xorg state:D stack:0 pid:1336 tgid:1336 ppid:1330 flags:0x00404002
[ 2055.368643] Call Trace:
[ 2055.368658] <TASK>
[ 2055.368680] __schedule+0x4fb/0xc00
[ 2055.368728] schedule+0x27/0xf0
[ 2055.368759] drm_vblank_work_flush+0x96/0x100 [drm]
[ 2055.369155] ? __pfx_autoremove_wake_function+0x10/0x10
[ 2055.369191] intel_wait_for_vblank_workers+0x5d/0x90 [i915]
[ 2055.370824] intel_atomic_commit_tail+0x85a/0x11c0 [i915]
[ 2055.372337] ? __wait_for_common+0x170/0x1c0
[ 2055.372485] ? __kmalloc_cache_noprof+0x111/0x310
[ 2055.372534] intel_atomic_commit+0x2d0/0x310 [i915]
[ 2055.374035] drm_atomic_commit+0xab/0xe0 [drm]
[ 2055.374405] ? __pfx___drm_printfn_info+0x10/0x10 [drm]
[ 2055.374812] drm_mode_obj_set_property_ioctl+0x15a/0x3d0 [drm]
[ 2055.375241] ? tomoyo_init_request_info+0x99/0xc0
[ 2055.375274] ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm]
[ 2055.375701] drm_ioctl_kernel+0xb2/0x100 [drm]
[ 2055.376139] drm_ioctl+0x276/0x4c0 [drm]
[ 2055.376662] ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm]
[ 2055.377115] __x64_sys_ioctl+0x94/0xd0
[ 2055.377152] do_syscall_64+0x82/0x190
[ 2055.377185] ? _copy_to_user+0x36/0x50
[ 2055.377209] ? drm_ioctl+0x2a0/0x4c0 [drm]
[ 2055.377642] ? __pfx_drm_mode_createblob_ioctl+0x10/0x10 [drm]
[ 2055.378048] ? syscall_exit_to_user_mode+0x164/0x210
[ 2055.378080] ? do_syscall_64+0x8e/0x190
[ 2055.378107] ? ptep_set_access_flags+0x32/0x40
[ 2055.378133] ? wp_page_reuse+0x8d/0xa0
[ 2055.378163] ? do_wp_page+0x8c4/0xc90
[ 2055.378188] ? __pte_offset_map+0x1b/0x180
[ 2055.378213] ? __handle_mm_fault+0xaf8/0xf90
[ 2055.378247] ? __count_memcg_events+0x53/0xf0
[ 2055.378275] ? count_memcg_events.constprop.0+0x1a/0x30
[ 2055.378304] ? handle_mm_fault+0xae/0x2d0
[ 2055.378331] ? do_user_addr_fault+0x379/0x670
[ 2055.378358] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 2055.378390] RIP: 0033:0x7fa6a4b1bd5b
[ 2055.378413] RSP: 002b:00007ffdd753ab40 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 2055.378441] RAX: ffffffffffffffda RBX: 00007ffdd753b010 RCX: 00007fa6a4b1bd5b
[ 2055.378459] RDX: 00007ffdd753abd0 RSI: 00000000c01864ba RDI: 0000000000000010
[ 2055.378475] RBP: 00007ffdd753abd0 R08: 0000000000000065 R09: 000056045aaa7ff4
[ 2055.378490] R10: 00007fa6a512b2b8 R11: 0000000000000246 R12: 00000000c01864ba
[ 2055.378506] R13: 0000000000000010 R14: 000056045a290690 R15: 000056045a28fbc0
[ 2055.378534] </TASK>
[ 2055.378547] Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings
Reply to: