Fwd: How to Diagnose Mysterious System Freeze?
> If you are unable to determine which package your bug report should be filed against, please send e-mail to the Debian user mailing list asking for advice.
Please help!
About once a week my up-to-date Debian system freezes completely.
Graphical interface is unchanged.
System does not respond to ssh.
Mouse remains lit but does not move cursor.
Keyboard LEDs for NumLock and Caps Lock remain on or off and cannot be changed.
Keyboard keypresses seems to have no effect.
Not possible to change to virtual consoles with Ctrl-Alt-F1 .. F6.
SysReq is no use because even when system is working, it does not seem
to have an effect in GUI, only in virtual consoles.
Once-per-second "free -m" output shows about 16GB free RAM. (Virtual
memory generally unused.)
Eventually I force power down system, after about a half hour or more
of waiting.
kdump was installed, but created no dump.
OS: Debian 11.2 KDE system
Hardware: Dell Optiplex 7070 Micro Form Factor
Questions:
1. How do I file a bug report?
2. What can I do to diagnose this, this time or next?
3. Which logs should I inspect?
Xorg has periodically messages like this. They seem to happen
frequently and not only before a freeze, but perhaps they are a hint?
[396395.522] (EE) event4 - PixArt Dell MS116 USB Optical Mouse:
client bug: event processing lagging behind by 16ms, your system is
too slow
[396914.093] (EE) event8 - Chicony USB Keyboard: client bug: event
processing lagging behind by 18ms, your system is too slow
[398959.514] (EE) event8 - Chicony USB Keyboard: client bug: event
processing lagging behind by 11ms, your system is too slow
[399013.586] (EE) event5 - CASUE USB KB: client bug: event processing
lagging behind by 16ms, your system is too slow
[399561.782] (EE) event5 - CASUE USB KB: client bug: event processing
lagging behind by 35ms, your system is too slow
last entry of debug.1
Mar 19 22:57:50 .... rtkit-daemon[1270]: Supervising 8 threads of 4
processes of 1 users.
daemon.log.1
Mar 19 23:10:45 .... smartd[926]: Device: /dev/sda [SAT], SMART Usage
Attribute: 190 Airflow_Temperature_Cel changed from 56 to 58
user.log.1 last entry was 6 hours prior
Mar 19 18:01:18 ... org.kde.krunner[2234315]:
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/Highlight.qml:34:5:
QML Connections: Implicitly defined onFoo properties in Connections
are deprecated. Use this syntax i
nstead: function onFoo(<arguments>) { ... }
Mar 19 18:01:18 .... org.kde.krunner[2234315]:
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/Highlight.qml:34:5:
QML Connections: Implicitly defined onFoo properties in Connections
are deprecated. Use this syntax i
nstead: function onFoo(<arguments>) { ... }
Mar 19 18:01:18 .... org.kde.krunner[2234315]:
QUnifiedTimer::stopAnimationDriver: driver is not running
syslog.1:
Mar 19 23:10:45 .... smartd[926]: Device: /dev/sda [SAT], SMART Usage
Attribute: 190 Airflow_Temperature_Cel changed from 56 to 58
Mar 19 23:17:01 .... CRON[2755516]: (root) CMD ( cd / && run-parts
--report /etc/cron.hourly)
messages.1
Mar 19 18:01:18 .... org.kde.krunner[2234315]:
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/Highlight.qml:34:5:
QML Connections: Implicitly defined onFoo properties in Connections
are deprecated. Use this syntax i
nstead: function onFoo(<arguments>) { ... }
Mar 19 18:01:18 .... org.kde.krunner[2234315]:
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/Highlight.qml:34:5:
QML Connections: Implicitly defined onFoo properties in Connections
are deprecated. Use this syntax i
nstead: function onFoo(<arguments>) { ... }
Mar 19 18:01:18 .... org.kde.krunner[2234315]:
QUnifiedTimer::stopAnimationDriver: driver is not running
kern.log.1:
Mar 19 11:19:56 ... kernel: [360044.004470] IPv6:
ADDRCONF(NETDEV_CHANGE): eno2: link becomes ready
What else should I look for?
Reply to: