Package: bugs.debian.org
Severity: important
Tags: upstream
Dear Maintainers,
because the kernel logs show clock errors for amdgpu and segfaults in the gnome
shell, I'm not sure which package I have to refer to. Please feel free to ask
for other log files or hardware configurations that might be of interest to
you.
First Scenario
==
I observed several freezes of my system in October/November. They occured,
when
* the screen was locked or
* when the monitors were switched off.
The screen froze not every time, but in the majority of the times I did this.
Over the last months I "solved" this issue by not locking the screen or turning
off the monitors while the system was running. During this time I did not
observe any freezes like this. Yesterday I switched off the monitors and when
I returned, I observed a freezing of the system again.
The follwing actions did not seem to have any effect:
* on mouse movement, the cursor does not move
* Ctrl+Shift+F3 doesn't switch to a terminal
* Ctrl+Shift+Del holding for 10+ seconds does not reboot.
I missed to do press Alt+Print+K, next time I will test this too.
The only solution to recover is to press the power button on the tower for
several seconds and to reboot the system.
Here a short excerpt from /var/log/kern.log from yesterday:
Mar 14 10:19:24 mundus kernel: [ 5483.172863]
[drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery tried 5
times
Mar 14 10:19:24 mundus kernel: [ 5483.172879]
[drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
Mar 14 12:44:50 mundus kernel: [14209.555905] gnome-shell[1254]: segfault
at 38 ip 7ff9ec3f8f70 sp 7ffe1cf6aaf8 error 4 in
libmutter-1.so.0.0.0[7ff9ec398000+15]
Mar 14 12:44:51 mundus kernel: [14209.583537] rfkill: input handler enabled
Mar 14 12:44:51 mundus kernel: [14209.755875]
[drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status
failed
Mar 14 12:44:51 mundus kernel: [14209.755896]
[drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
Mar 14 12:44:51 mundus kernel: [14209.932953]
[drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status
failed
Mar 14 12:44:51 mundus kernel: [14209.932973]
[drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
Mar 14 12:44:51 mundus kernel: [14210.120708]
[drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status
failed
Mar 14 12:44:51 mundus kernel: [14210.120728]
[drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
Mar 14 12:44:51 mundus kernel: [14210.297755]
[drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status
failed
Mar 14 12:44:51 mundus kernel: [14210.297774]
[drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
Mar 14 12:53:19 mundus kernel: [14718.348671] rfkill: input handler
disabled
Mar 14 13:43:18 mundus kernel: [17716.735394] gnome-shell[14938]: segfault
at 55ba0af83c18 ip 7fb6aebe2676 sp 7ffda3cf9020 error 4 in
libst-1.0.so[7fb6aebc2000+4d000]
Mar 14 13:43:18 mundus kernel: [17716.783243] rfkill: input handler enabled
Mar 14 13:43:25 mundus kernel: [17723.744111] rfkill: input handler
disabled
Second Scenario
===
Because in this second scenario the behaviour is different, I was not sure if
it is relevant to you. But since it also results in a reset of the user
session, I wanted to mention it.
The screen freezes during normal usage at random. This happens every two or
three days. After let's say 30 seconds the log in screen is shown and a new
session is started. This also occured during the phase when I did not lock the
screen.
Again a short excerpt from /var/log/kern.log regarding the second scenario:
Mar 15 05:35:32 mundus kernel: [ 2026.148912] show_signal_msg: 17 callbacks
suppressed
Mar 15 05:35:32 mundus kernel: [ 2026.148914] gnome-shell[1257]: segfault
at 562055805a68 ip 7fbae1b7b676 sp 7fff83108b90 error 4 in
libst-1.0.so[7fbae1b5b000+4d000]
Mar 15 05:35:32 mundus kernel: [ 2026.195608] rfkill: input handler enabled
Mar 15 05:35:39 mundus kernel: [ 2033.100377] rfkill: input handler
disabled
In this specific case I was moving a window via Super+Shift+Left from one
monitor to another when the GUI crashed. After logging in I was able to use
the system as normal.
Kind Regards
Hermann
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.0-3-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
