You are not logged in.
Pages: 1
Hi I’m stuck on linux 4.5.
When updating beyond that (4.6.x or 4.7.1), SDDM freezes or crashes. A boot looks like this:
an initial error:
[drm:intel_dp_start_link_train [i915]] *ERROR* failed to train DP, aborting
If only the new kernel is used, I get driver crashes and SDDM freezes after a second unless I switch to a TTY. When frozen, I can only use SysRq+REISUB to reboot.
When additionally uninstalling xf86-video-intel, SDDM crashes until systemd doesn’t restart it anymore, but the (non-graphical) system stays responsive (stacktraces at the end)
the console and log get flooded with this error (making the system hard to debug as i can’t use an editor or type complex commands)
[drm:intel_psr_work [i915]] *ERROR* Timed out waiting for PSR Idle for re-enable
driver crashes:
Aug 22 12:53:07 NB63540 kernel: ------------[ cut here ]------------
Aug 22 12:53:07 NB63540 kernel: WARNING: CPU: 0 PID: 321 at drivers/gpu/drm/drm_irq.c:1318 drm_wait_one_vblank+0x1b0/0x1c0 [drm]
Aug 22 12:53:07 NB63540 kernel: vblank wait timed out on crtc 0
Aug 22 12:53:07 NB63540 kernel: Modules linked in: snd_hda_codec_hdmi hid_logitech_hidpp hid_logitech_dj hid_cherry uvcvideo btusb videobuf2_vmalloc videobuf2_memops btrt
Aug 22 12:53:07 NB63540 kernel: drm e1000e shpchp snd_hda_intel intel_gtt snd_hda_codec syscopyarea sysfillrect sysimgblt mei_me ptp snd_hda_core fb_sys_fops pps_core me
Aug 22 12:53:07 NB63540 kernel: CPU: 0 PID: 321 Comm: Xorg Not tainted 4.7.1-1-ARCH #1
Aug 22 12:53:07 NB63540 kernel: Hardware name: TOSHIBA PORTEGE Z30-A/PORTEGE Z30-A, BIOS Version 3.70 07/25/2014
Aug 22 12:53:07 NB63540 kernel: 0000000000000286 00000000d64e52c1 ffff88020f4f79c8 ffffffff812eb042
Aug 22 12:53:07 NB63540 kernel: ffff88020f4f7a18 0000000000000000 ffff88020f4f7a08 ffffffff8107a3ab
Aug 22 12:53:07 NB63540 kernel: 0000052600000282 ffff8800db381800 0000000000000000 0000000000000000
Aug 22 12:53:07 NB63540 kernel: Call Trace:
Aug 22 12:53:07 NB63540 kernel: [<ffffffff812eb042>] dump_stack+0x63/0x81
Aug 22 12:53:07 NB63540 kernel: [<ffffffff8107a3ab>] __warn+0xcb/0xf0
Aug 22 12:53:07 NB63540 kernel: [<ffffffff8107a42f>] warn_slowpath_fmt+0x5f/0x80
Aug 22 12:53:07 NB63540 kernel: [<ffffffff810bc7d5>] ? finish_wait+0x55/0x70
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa043d9e0>] drm_wait_one_vblank+0x1b0/0x1c0 [drm]
Aug 22 12:53:07 NB63540 kernel: [<ffffffff810bcc80>] ? wake_atomic_t_function+0x60/0x60
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa0606bd0>] hsw_disable_ips+0x80/0x1a0 [i915]
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa0606d12>] intel_pre_disable_primary+0x22/0x40 [i915]
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa0606e22>] intel_pre_plane_update+0xf2/0x140 [i915]
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa06077ab>] intel_atomic_commit+0x47b/0x1460 [i915]
Aug 22 12:53:07 NB63540 kernel: [<ffffffff811d9ee1>] ? __kmalloc_track_caller+0x31/0x240
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa0456a7d>] ? drm_atomic_check_only+0x18d/0x610 [drm]
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa0456f37>] drm_atomic_commit+0x37/0x60 [drm]
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa0417adc>] drm_atomic_helper_disable_plane+0xac/0xf0 [drm_kms_helper]
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa04557c5>] ? drm_modeset_lock+0x35/0xe0 [drm]
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa044600b>] __setplane_internal+0x17b/0x260 [drm]
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa0455af4>] ? drm_modeset_lock_all_ctx+0xa4/0xb0 [drm]
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa0449bcc>] drm_mode_setplane+0x15c/0x1d0 [drm]
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa043b9a2>] drm_ioctl+0x152/0x540 [drm]
Aug 22 12:53:07 NB63540 kernel: [<ffffffff8121566f>] ? file_update_time+0x5f/0x110
Aug 22 12:53:07 NB63540 kernel: [<ffffffffa0449a70>] ? drm_plane_check_pixel_format+0x50/0x50 [drm]
Aug 22 12:53:07 NB63540 kernel: [<ffffffff811f9694>] ? __vfs_write+0xe4/0x140
Aug 22 12:53:07 NB63540 kernel: [<ffffffff8120ccc2>] do_vfs_ioctl+0xa2/0x5d0
Aug 22 12:53:07 NB63540 kernel: [<ffffffff81217d57>] ? __fget+0x77/0xb0
Aug 22 12:53:07 NB63540 kernel: [<ffffffff8120d269>] SyS_ioctl+0x79/0x90
Aug 22 12:53:07 NB63540 kernel: [<ffffffff815dd772>] entry_SYSCALL_64_fastpath+0x1a/0xa4
Aug 22 12:53:07 NB63540 kernel: ---[ end trace 7a389b8e08394f54 ]---
[...]
Aug 22 12:53:11 NB63540 kernel: ------------[ cut here ]------------
Aug 22 12:53:11 NB63540 kernel: WARNING: CPU: 3 PID: 321 at drivers/gpu/drm/i915/intel_display.c:13562 intel_atomic_commit+0x13af/0x1460 [i915]
Aug 22 12:53:11 NB63540 kernel: pipe A vblank wait timed out
Aug 22 12:53:11 NB63540 kernel: Modules linked in: snd_hda_codec_hdmi hid_logitech_hidpp hid_logitech_dj hid_cherry uvcvideo btusb videobuf2_vmalloc videobuf2_memops btrt
Aug 22 12:53:11 NB63540 kernel: drm e1000e shpchp snd_hda_intel intel_gtt snd_hda_codec syscopyarea sysfillrect sysimgblt mei_me ptp snd_hda_core fb_sys_fops pps_core me
Aug 22 12:53:11 NB63540 kernel: CPU: 3 PID: 321 Comm: Xorg Tainted: G W 4.7.1-1-ARCH #1
Aug 22 12:53:11 NB63540 kernel: Hardware name: TOSHIBA PORTEGE Z30-A/PORTEGE Z30-A, BIOS Version 3.70 07/25/2014
Aug 22 12:53:11 NB63540 kernel: 0000000000000286 00000000d64e52c1 ffff88020f4f7af0 ffffffff812eb042
Aug 22 12:53:11 NB63540 kernel: ffff88020f4f7b40 0000000000000000 ffff88020f4f7b30 ffffffff8107a3ab
Aug 22 12:53:11 NB63540 kernel: 000034fadb3819b0 ffff88007fa10000 0000000000000000 0000000000000000
Aug 22 12:53:11 NB63540 kernel: Call Trace:
Aug 22 12:53:11 NB63540 kernel: [<ffffffff812eb042>] dump_stack+0x63/0x81
Aug 22 12:53:11 NB63540 kernel: [<ffffffff8107a3ab>] __warn+0xcb/0xf0
Aug 22 12:53:11 NB63540 kernel: [<ffffffff8107a42f>] warn_slowpath_fmt+0x5f/0x80
Aug 22 12:53:11 NB63540 kernel: [<ffffffff810bc7d5>] ? finish_wait+0x55/0x70
Aug 22 12:53:11 NB63540 kernel: [<ffffffffa06086df>] intel_atomic_commit+0x13af/0x1460 [i915]
Aug 22 12:53:11 NB63540 kernel: [<ffffffff815daf5f>] ? __ww_mutex_lock+0x4f/0x90
Aug 22 12:53:11 NB63540 kernel: [<ffffffff810bcc80>] ? wake_atomic_t_function+0x60/0x60
Aug 22 12:53:11 NB63540 kernel: [<ffffffffa0456436>] ? drm_atomic_set_crtc_for_connector+0x96/0x100 [drm]
Aug 22 12:53:11 NB63540 kernel: [<ffffffffa0456f37>] drm_atomic_commit+0x37/0x60 [drm]
Aug 22 12:53:11 NB63540 kernel: [<ffffffffa0417efd>] drm_atomic_helper_set_config+0x7d/0xb0 [drm_kms_helper]
Aug 22 12:53:11 NB63540 kernel: [<ffffffffa0444e85>] drm_mode_set_config_internal+0x65/0x110 [drm]
Aug 22 12:53:11 NB63540 kernel: [<ffffffffa044a0bb>] drm_mode_setcrtc+0x47b/0x580 [drm]
Aug 22 12:53:11 NB63540 kernel: [<ffffffffa043b9a2>] drm_ioctl+0x152/0x540 [drm]
Aug 22 12:53:11 NB63540 kernel: [<ffffffffa0449c40>] ? drm_mode_setplane+0x1d0/0x1d0 [drm]
Aug 22 12:53:11 NB63540 kernel: [<ffffffff811f9694>] ? __vfs_write+0xe4/0x140
Aug 22 12:53:11 NB63540 kernel: [<ffffffff8120ccc2>] do_vfs_ioctl+0xa2/0x5d0
Aug 22 12:53:11 NB63540 kernel: [<ffffffff81217d57>] ? __fget+0x77/0xb0
Aug 22 12:53:11 NB63540 kernel: [<ffffffff8120d269>] SyS_ioctl+0x79/0x90
Aug 22 12:53:11 NB63540 kernel: [<ffffffff815dd772>] entry_SYSCALL_64_fastpath+0x1a/0xa4
Aug 22 12:53:11 NB63540 kernel: ---[ end trace 7a389b8e08394f59 ]---
stacktrace of the SDDM crash:
Aug 22 12:11:11 NB63540 sddm[481]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Aug 22 12:11:11 NB63540 kernel: sddm[481]: segfault at 0 ip 00007fe9181e5d63 sp 00007ffca7180b40 error 4 in libQt5Core.so.5.7.0[7fe917f2d000+4c7000]
Aug 22 12:11:11 NB63540 sddm-helper[495]: [PAM] Starting...
Aug 22 12:11:11 NB63540 sddm-helper[495]: [PAM] Authenticating...
Aug 22 12:11:11 NB63540 sddm-helper[495]: [PAM] returning.
Aug 22 12:11:11 NB63540 systemd[1]: Started Process Core Dump (PID 497/UID 0).
Aug 22 12:11:11 NB63540 sddm-helper[495]: Received a wrong opcode instead of AUTHENTICATED: 0
Aug 22 12:11:11 NB63540 systemd[1]: sddm.service: Main process exited, code=dumped, status=11/SEGV
Aug 22 12:11:11 NB63540 systemd[1]: sddm.service: Unit entered failed state.
Aug 22 12:11:11 NB63540 systemd[1]: sddm.service: Failed with result 'core-dump'.
Aug 22 12:11:11 NB63540 systemd-coredump[498]: Process 481 (sddm) of user 0 dumped core.
Stack trace of thread 481:
#0 0x00007fe9181e5d63 _ZN7QObject7connectEPKS_PKcS1_S3_N2Qt14ConnectionTypeE (libQt5Core.so.5)
#1 0x0000000000430575 _ZN4SDDM4Auth7Private9setSocketEP12QLocalSocket (sddm)
#2 0x00000000004320e2 _ZN4SDDM4Auth12SocketServer19handleNewConnectionEv (sddm)
#3 0x00007fe9181df4e9 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
#4 0x00007fe9186e733f n/a (libQt5Network.so.5)
#5 0x00007fe9181df4e9 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
#6 0x00007fe918259c6e _ZN15QSocketNotifier9activatedEiNS_14QPrivateSignalE (libQt5Core.so.5)
#7 0x00007fe9181ec192 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5)
#8 0x00007fe9181b3c6b _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
#9 0x00007fe918208a2d n/a (libQt5Core.so.5)
#10 0x00007fe914488dd7 g_main_context_dispatch (libglib-2.0.so.0)
#11 0x00007fe914489040 n/a (libglib-2.0.so.0)
#12 0x00007fe9144890ec g_main_context_iteration (libglib-2.0.so.0)
#13 0x00007fe91820857f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5
#14 0x00007fe9181b20da _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#15 0x00007fe9181ba5cc _ZN16QCoreApplication4execEv (libQt5Core.so.5)
#16 0x000000000041b711 main (sddm)
#17 0x00007fe917610291 __libc_start_main (libc.so.6)
#18 0x000000000041ba09 _start (sddm)
Stack trace of thread 482:
#0 0x00007fe9176cf48d poll (libc.so.6)
#1 0x00007fe914488fd6 n/a (libglib-2.0.so.0)
#2 0x00007fe9144890ec g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007fe91820857f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5
#4 0x00007fe9181b20da _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5 0x00007fe917fd50f3 _ZN7QThread4execEv (libQt5Core.so.5)
#6 0x00007fe918f79e75 n/a (libQt5DBus.so.5)
#7 0x00007fe917fd9d78 n/a (libQt5Core.so.5)
#8 0x00007fe9173da454 start_thread (libpthread.so.0)
#9 0x00007fe9176d87df __clone (libc.so.6)
Last edited by flying sheep (2016-08-22 11:11:56)
Offline
Question for you. Did you run 'sudo mkinitcpio -p linux' after updating kernel and/or drivers?
Offline
I wonder if your issue might be related to https://bbs.archlinux.org/viewtopic.php?id=215809
Mike C
Offline
Question for you. Did you run 'sudo mkinitcpio -p linux' after updating kernel and/or drivers?
no, i thought the hooks should take care of that…
now i did and the only thing that changed is that the freeze happens about ⅔ through the SDDM progress bar instead of before i manage to enter my password
I wonder if your issue might be related to https://bbs.archlinux.org/viewtopic.php?id=215809
maybe, but your bug surfaced in 4.7, while mine exists since 4.6 this thread also seems related.
i just wanted to give one persistent comprehensive case, not a sea of related issues that may or may not be fixed in 4.7
Last edited by flying sheep (2016-08-23 07:39:56)
Offline
Pages: 1