Re: Frequent freezing around login screens
On 27/03/2025 14:34, W. Pepperdine wrote:
dmesg (http://paste.debian.net/1365575/)
I am confused. I have impression that you described your trouble as
rather severe freeze with no reaction on keyboard an mouse. Am I wrong?
How have you managed to get dmesg output in that state?
/var/log/kern.log has wall time timestamp, not monotonic ones.
[ 35.014008] systemd-journald[289]: Time jumped backwards, rotating.
Some applications may have bugs related to backward time jumps. How much
that jump was? It might be something wrong with time configuration
timedatectl
There is a little chance that RTC battery might be discharged (causing
issues with BIOS settings).
[ 35.040339] systemd-journald[289]: Failed to read journal file /var/log/journal/c113f4b56932414d90d5b7ade9c142d9/user-1001.journal for rotation, trying to move it out of the way: Device or resource busy
[ 35.040583] systemd-journald[289]: Failed to read journal file /var/log/journal/c113f4b56932414d90d5b7ade9c142d9/user-1000.journal for rotation, trying to move it out of the way: Device or resource busy
I have not seen this kind of messages so far. At least they give some
keywords for search queries.
May it happen that no space left on some partition?
df -h
journalctl -b -p3 (http://paste.debian.net/1365578/)
Just "-b" without additional argument like "-1" means current boot. It
is useless. Get logs for some boot when you experienced a hang. Do not
use "-p" filtering. If it is not comfortable for you to post detailed logs
journalctl -e -b ID_OF_FAILED_BOOT
then try to figure out suspicious entries (not necessary errors)
yourself. Repeat the same without "-e" to get all logs for that boot.
Reply to: