Debian Testing random freeze (ANACRON)

[Danielsan]

Hi guys, I wouldn't do cross posting, but I have to break down the issue which may have a multi factorial origins.

One point I found in common analyzing the logs is the forced reboot happens after the anacron jobs.

Code: Select all

Sep 14 08:00:33 motile systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab...
Sep 14 08:00:42 motile fstrim[2945]: /home: 162 GiB (173904515072 bytes) trimmed on /dev/nvme0n1p2
Sep 14 08:00:42 motile fstrim[2945]: /boot/efi: 43.4 MiB (45495296 bytes) trimmed on /dev/sda1
Sep 14 08:00:42 motile fstrim[2945]: /: 47.9 GiB (51415863296 bytes) trimmed on /dev/nvme0n1p1
Sep 14 08:00:42 motile systemd[1]: fstrim.service: Succeeded.
Sep 14 08:00:42 motile systemd[1]: Finished Discard unused blocks on filesystems from /etc/fstab.
Sep 14 08:03:58 motile rsyslogd[807]: [origin software="rsyslogd" swVersion="8.2008.0" x-pid="807" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
Sep 14 08:03:58 motile anacron[790]: Job `cron.weekly' started
Sep 14 08:03:58 motile anacron[3068]: Updated timestamp for job `cron.weekly' to 2020-09-14
Sep 14 08:03:58 motile anacron[790]: Job `cron.weekly' terminated
Sep 14 08:03:58 motile anacron[790]: Normal exit (2 jobs run)
Sep 14 08:03:58 motile systemd[1]: anacron.service: Succeeded.
Sep 14 08:08:58 motile systemd[1]: Starting Cleanup of Temporary Directories...
Sep 14 08:08:58 motile systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Sep 14 08:08:58 motile systemd[1]: Finished Cleanup of Temporary Directories.
Sep 14 08:09:18 motile pulseaudio[1750]: E: [alsa-sink-ALC269VC Analog] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Sep 14 08:09:18 motile pulseaudio[1750]: E: [alsa-sink-ALC269VC Analog] alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Sep 14 08:09:18 motile pulseaudio[1750]: E: [alsa-sink-ALC269VC Analog] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Sep 14 08:11:50 motile pulseaudio[1750]: E: [alsa-source-ALC269VC Analog] alsa-source.c: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Sep 14 08:11:50 motile pulseaudio[1750]: E: [alsa-source-ALC269VC Analog] alsa-source.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Sep 14 08:11:50 motile pulseaudio[1750]: E: [alsa-source-ALC269VC Analog] alsa-source.c: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Sep 14 08:16:53 motile rtkit-daemon[1109]: Supervising 5 threads of 3 processes of 1 users.
Sep 14 08:16:53 motile rtkit-daemon[1109]: Supervising 5 threads of 3 processes of 1 users.
Sep 14 08:16:57 motile rtkit-daemon[1109]: Supervising 5 threads of 3 processes of 1 users.
Sep 14 08:16:57 motile rtkit-daemon[1109]: Supervising 5 threads of 3 processes of 1 users.
Sep 14 08:16:57 motile rtkit-daemon[1109]: Supervising 5 threads of 3 processes of 1 users.
Sep 14 08:16:57 motile rtkit-daemon[1109]: Supervising 5 threads of 3 processes of 1 users.
Sep 14 08:16:57 motile rtkit-daemon[1109]: Successfully made thread 3233 of process 2646 owned by '1002' RT at priority 10.
Sep 14 08:16:57 motile rtkit-daemon[1109]: Supervising 6 threads of 4 processes of 1 users.
Sep 14 08:17:01 motile CRON[3251]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 14 08:17:01 motile CRON[3252]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Sep 14 08:17:01 motile CRON[3251]: pam_unix(cron:session): session closed for user root
Sep 14 08:30:01 motile CRON[3612]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 14 08:30:01 motile CRON[3613]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Sep 14 08:30:01 motile CRON[3612]: pam_unix(cron:session): session closed for user root
Sep 14 08:32:49 motile systemd[1]: Started Run anacron jobs.
Sep 14 08:32:49 motile anacron[3671]: Anacron 2.3 started on 2020-09-14
Sep 14 08:32:49 motile anacron[3671]: Normal exit (0 jobs run)
Sep 14 08:32:49 motile systemd[1]: anacron.service: Succeeded.
reboot

I should take a look at which tasks are taking care those anacron jobs...

[Danielsan]

Another freeze... Another cron job involved, at least it seems to me.

Code: Select all

Sep 15 12:17:01 motile CRON[15150]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 15 12:17:01 motile CRON[15151]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Sep 15 12:17:01 motile CRON[15150]: pam_unix(cron:session): session closed for user root
Sep 15 12:30:01 motile CRON[15198]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 15 12:30:01 motile CRON[15199]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Sep 15 12:30:01 motile CRON[15198]: pam_unix(cron:session): session closed for user root
Sep 15 12:34:42 motile systemd[1]: Started Run anacron jobs.
Sep 15 12:34:42 motile anacron[15214]: Anacron 2.3 started on 2020-09-15
Sep 15 12:34:42 motile anacron[15214]: Normal exit (0 jobs run)
Sep 15 12:34:42 motile systemd[1]: anacron.service: Succeeded.
Sep 15 13:02:41 motile kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
Sep 15 13:02:41 motile kernel: atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.
Sep 15 13:02:41 motile kernel: atkbd serio0: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0).
Sep 15 13:02:41 motile kernel: atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.
Sep 15 13:17:01 motile CRON[15665]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 15 13:17:01 motile CRON[15666]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Sep 15 13:17:01 motile CRON[15665]: pam_unix(cron:session): session closed for user root
Sep 15 13:30:01 motile CRON[15804]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 15 13:30:01 motile CRON[15805]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Sep 15 13:30:01 motile CRON[15804]: pam_unix(cron:session): session closed for user root
Sep 15 13:31:42 motile systemd[1]: Started Run anacron jobs.
Sep 15 13:31:42 motile anacron[15873]: Anacron 2.3 started on 2020-09-15
Sep 15 13:31:42 motile anacron[15873]: Normal exit (0 jobs run)
Sep 15 13:31:42 motile systemd[1]: anacron.service: Succeeded.
Sep 15 13:38:02 motile rtkit-daemon[1129]: Supervising 9 threads of 5 processes of 2 users.
Sep 15 13:38:02 motile rtkit-daemon[1129]: Supervising 9 threads of 5 processes of 2 users.
Sep 15 13:38:05 motile rtkit-daemon[1129]: Supervising 9 threads of 5 processes of 2 users.
Sep 15 13:38:05 motile rtkit-daemon[1129]: Supervising 9 threads of 5 processes of 2 users.
Sep 15 13:38:05 motile rtkit-daemon[1129]: Supervising 9 threads of 5 processes of 2 users.
Sep 15 13:38:05 motile rtkit-daemon[1129]: Supervising 9 threads of 5 processes of 2 users.
Sep 15 13:38:05 motile rtkit-daemon[1129]: Successfully made thread 15953 of process 14364 owned by '1002' RT at priority 10.
Sep 15 13:38:05 motile rtkit-daemon[1129]: Supervising 10 threads of 6 processes of 2 users.
Sep 15 14:10:30 motile rtkit-daemon[1129]: Supervising 9 threads of 5 processes of 2 users.
Sep 15 14:10:30 motile rtkit-daemon[1129]: Supervising 9 threads of 5 processes of 2 users.
Sep 15 14:17:01 motile CRON[16772]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 15 14:17:01 motile CRON[16773]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Sep 15 14:17:01 motile CRON[16772]: pam_unix(cron:session): session closed for user root
-- Reboot --

[Danielsan]

This morning two frozen in a row within 5 minutes, I had to go on Windows since my son had a diagnostic test. There were years that I hadn't those kind of issues with Debian, I am very frustrated...

[sgosnell]

If you need a reliable system that will work every day, why are you running Testing? It's called Testing for a reason. For a stable, reliable system, you should be running Stable. It is not unusual for Testing to be in an unbootable state for a few days. It does break, and is not designed for use in critical systems.

[Danielsan]

My guess is this is a kind of issue that would probably appears on stable too. However testing has its sense, if I can isolated the issue I can report the bug and helping for the next stable release.

I just noticed a lot of people are suffering the same issue, but the messages are pretty confused, I haven't found yet a potential workaround even though the BIOS of this laptop has very limited functionalities...

https://bugzilla.kernel.org/show_bug.cgi?id=196683#c650

I'll check the bios and I'll try to update it.

https://www.reddit.com/r/motile/comment ... 06_safely/
http://www.motilecustomerservice.com/m141.html

[LE_746F6D617A7A69]

Your logs are completely different from those listed under the link that You have referenced (https://bugzilla.kernel.org/show_bug.cgi?id=196683#c650) - Your case seems to be totally unrelated ...
I would say that instability of Your OS has nothing to do with the Cron - there's no apparent evidence ...
I think that You should take into account the hardware problems (like insufficient cooling and/or unstable power, bad RAM, etc) or a problem with the testing version of Debian.

Regarding the BIOS update: this is a risky operation, because BIOSes are never truly tested, and so the update can cause even more unidentified problems/crashes. Never update the BIOS unless You are completely sure that the newer version indeed fixes something ... (this is not a joke)

[Danielsan]

Those guys are reporting crashes from kern logs, while I am posting from Journalclt, I'll go take a look over the kern.log again.

This laptop hasn't had an hiccup with windows hence I exclude hardware issues, there is something that isn't playing right on the kernel even though the kernel is quite updated.

[sgosnell]

What are you running hourly as root?

[Danielsan]

What are you running hourly as root?

I don't know it is a system cron job, I didn't setup anything about that...

[Danielsan]

While the computer was getting stuck kern.log didn't register anything:

Code: Select all

Sep 17 07:50:05 motile kernel: [   24.688083] fuse: init (API version 7.31)
Sep 17 07:50:06 motile kernel: [   25.519696] Lockdown: systemd-logind: hibernation is restricted; see https://wiki.debian.org/SecureBoot
Sep 17 07:50:06 motile kernel: [   25.524791] Lockdown: systemd-logind: hibernation is restricted; see https://wiki.debian.org/SecureBoot
Sep 17 07:50:06 motile kernel: [   25.525622] Lockdown: systemd-logind: hibernation is restricted; see https://wiki.debian.org/SecureBoot
Sep 17 08:02:27 motile kernel: [    0.000000] Linux version 5.8.0-1-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.0-6) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.7-1 (2020-09-05)

And this is the last minute of journalctl:

Code: Select all

Sep 17 07:52:12 motile systemd[1]: Reloading.
Sep 17 07:52:12 motile systemd[1]: /lib/systemd/system/smartmontools.service:10: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Sep 17 07:52:12 motile systemd[1]: Reloading.
Sep 17 07:52:12 motile systemd[1]: /lib/systemd/system/smartmontools.service:10: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Sep 17 07:52:12 motile systemd[1]: Stopping LSB: exim Mail Transport Agent...
Sep 17 07:52:12 motile exim4[3251]: Stopping MTA: exim4_listener.
Sep 17 07:52:12 motile systemd[1]: exim4.service: Succeeded.
Sep 17 07:52:12 motile systemd[1]: Stopped LSB: exim Mail Transport Agent.
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[1740]: [session uid=1002 pid=1740] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[1740]: [session uid=1002 pid=1740] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[1740]: [session uid=1002 pid=1740] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[1740]: [session uid=1002 pid=1740] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[1740]: [session uid=1002 pid=1740] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[1740]: [session uid=1002 pid=1740] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[1740]: [session uid=1002 pid=1740] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[1740]: [session uid=1002 pid=1740] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[1740]: [session uid=1002 pid=1740] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[1740]: [session uid=1002 pid=1740] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[2328]: [session uid=1000 pid=2328] Reloaded configuration
Sep 17 07:52:18 motile dbus-daemon[1740]: [session uid=1002 pid=1740] Reloaded configuration
Sep 17 07:52:20 motile systemd[1]: Reloading.
Sep 17 07:52:21 motile systemd[1]: /lib/systemd/system/smartmontools.service:10: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Sep 17 07:52:21 motile systemd[1]: Reloading.
Sep 17 07:52:21 motile systemd[1]: /lib/systemd/system/smartmontools.service:10: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Sep 17 07:52:21 motile systemd[1]: exim4-base.timer: Succeeded.
Sep 17 07:52:21 motile systemd[1]: Stopped Daily exim4-base housekeeping.
Sep 17 07:52:21 motile systemd[1]: Stopping Daily exim4-base housekeeping.
Sep 17 07:52:21 motile systemd[1]: Started Daily exim4-base housekeeping.
Sep 17 07:52:22 motile systemd[1]: Reloading.
Sep 17 07:52:23 motile systemd[1]: /lib/systemd/system/smartmontools.service:10: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Sep 17 07:52:23 motile systemd[1]: Starting LSB: exim Mail Transport Agent...
Sep 17 07:52:23 motile exim4[4152]: Starting MTA: exim4.
Sep 17 07:52:23 motile systemd[1]: Started LSB: exim Mail Transport Agent.
Sep 17 07:52:23 motile systemd[1]: Reloading.
Sep 17 07:52:23 motile systemd[1]: /lib/systemd/system/smartmontools.service:10: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Sep 17 07:52:25 motile sudo[2611]: pam_unix(sudo:session): session closed for user root
Sep 17 07:52:31 motile sudo[4678]:   papino : TTY=tty1 ; PWD=/home/papino ; USER=root ; COMMAND=/usr/bin/apt autoremove
Sep 17 07:52:31 motile sudo[4678]: pam_unix(sudo:session): session opened for user root by papino(uid=0)
Sep 17 07:52:34 motile sudo[4678]: pam_unix(sudo:session): session closed for user root
Sep 17 07:52:38 motile sudo[4714]:   papino : TTY=tty1 ; PWD=/home/papino ; USER=root ; COMMAND=/usr/bin/apt clean
Sep 17 07:52:38 motile sudo[4714]: pam_unix(sudo:session): session opened for user root by papino(uid=0)
Sep 17 07:52:38 motile sudo[4714]: pam_unix(sudo:session): session closed for user root
Sep 17 07:52:40 motile systemd[1]: Started Getty on tty6.
Sep 17 07:52:40 motile login[824]: pam_unix(login:session): session closed for user papino
Sep 17 07:52:40 motile systemd[1]: getty@tty1.service: Succeeded.
Sep 17 07:52:40 motile systemd[1]: session-4.scope: Succeeded.
Sep 17 07:52:40 motile systemd-logind[764]: Session 4 logged out. Waiting for processes to exit.
Sep 17 07:52:40 motile systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 1.
Sep 17 07:52:40 motile systemd[1]: Stopped Getty on tty1.
Sep 17 07:52:40 motile systemd[1]: Started Getty on tty1.
Sep 17 07:52:40 motile systemd-logind[764]: Removed session 4.
Sep 17 07:52:40 motile bluetoothd[1054]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSink/sbc
Sep 17 07:52:40 motile bluetoothd[1054]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/sbc
Sep 17 07:52:40 motile systemd[2302]: pulseaudio.service: Succeeded.
Sep 17 07:52:48 motile rtkit-daemon[1097]: Supervising 6 threads of 4 processes of 2 users.
Sep 17 07:52:48 motile rtkit-daemon[1097]: Supervising 6 threads of 4 processes of 2 users.
Sep 17 07:52:50 motile systemd[1]: Stopping User Manager for UID 1000...
Sep 17 07:52:50 motile systemd[2302]: Stopped target Main User Target.
Sep 17 07:52:50 motile gvfsd[2339]: A connection to the bus can't be made
Sep 17 07:52:50 motile systemd[2302]: Stopping D-Bus User Message Bus...
Sep 17 07:52:50 motile systemd[2302]: Stopping Virtual filesystem service...
Sep 17 07:52:50 motile systemd[2302]: Stopping Multimedia Service...
Sep 17 07:52:50 motile systemd[2302]: dbus.service: Succeeded.
Sep 17 07:52:51 motile systemd[2302]: Stopped D-Bus User Message Bus.
Sep 17 07:52:51 motile systemd[2302]: gvfs-daemon.service: Succeeded.
Sep 17 07:52:51 motile systemd[2302]: Stopped Virtual filesystem service.
Sep 17 07:52:51 motile systemd[2302]: pipewire.service: Succeeded.
Sep 17 07:52:51 motile systemd[2302]: Stopped Multimedia Service.
Sep 17 07:52:51 motile systemd[2302]: Stopped target Basic System.
Sep 17 07:52:51 motile systemd[2302]: Stopped target Paths.
Sep 17 07:52:51 motile systemd[2302]: Stopped target Sockets.
Sep 17 07:52:51 motile systemd[2302]: Stopped target Timers.
Sep 17 07:52:51 motile systemd[2302]: dbus.socket: Succeeded.
Sep 17 07:52:51 motile systemd[2302]: Closed D-Bus User Message Bus Socket.
Sep 17 07:52:51 motile systemd[2302]: dirmngr.socket: Succeeded.
Sep 17 07:52:51 motile systemd[2302]: Closed GnuPG network certificate management daemon.
Sep 17 07:52:51 motile systemd[2302]: gpg-agent-browser.socket: Succeeded.
Sep 17 07:52:51 motile systemd[2302]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 17 07:52:51 motile systemd[2302]: gpg-agent-extra.socket: Succeeded.
Sep 17 07:52:51 motile systemd[2302]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Sep 17 07:52:51 motile systemd[2302]: gpg-agent-ssh.socket: Succeeded.
Sep 17 07:52:51 motile systemd[2302]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Sep 17 07:52:51 motile systemd[2302]: gpg-agent.socket: Succeeded.
Sep 17 07:52:51 motile systemd[2302]: Closed GnuPG cryptographic agent and passphrase cache.
Sep 17 07:52:51 motile systemd[2302]: pipewire.socket: Succeeded.
Sep 17 07:52:51 motile systemd[2302]: Closed Multimedia System.
Sep 17 07:52:51 motile systemd[2302]: pulseaudio.socket: Succeeded.
Sep 17 07:52:51 motile systemd[2302]: Closed Sound System.
Sep 17 07:52:51 motile systemd[2302]: Reached target Shutdown.
Sep 17 07:52:51 motile systemd[2302]: systemd-exit.service: Succeeded.
Sep 17 07:52:51 motile systemd[2302]: Finished Exit the Session.
Sep 17 07:52:51 motile systemd[2302]: Reached target Exit the Session.
Sep 17 07:52:51 motile systemd[1]: user@1000.service: Succeeded.
Sep 17 07:52:51 motile systemd[1]: Stopped User Manager for UID 1000.
Sep 17 07:52:51 motile systemd[1]: Stopping User Runtime Directory /run/user/1000...
Sep 17 07:52:51 motile systemd[1714]: run-user-1000.mount: Succeeded.
Sep 17 07:52:51 motile systemd[1]: run-user-1000.mount: Succeeded.
Sep 17 07:52:51 motile systemd[1]: user-runtime-dir@1000.service: Succeeded.
Sep 17 07:52:51 motile systemd[1]: Stopped User Runtime Directory /run/user/1000.
Sep 17 07:52:51 motile systemd[1]: Removed slice User Slice of UID 1000.
Sep 17 07:54:43 motile anacron[745]: Job `cron.daily' started
Sep 17 07:54:43 motile anacron[4877]: Updated timestamp for job `cron.daily' to 2020-09-17
Sep 17 07:54:43 motile anacron[745]: Job `cron.daily' terminated
Sep 17 07:54:43 motile anacron[745]: Normal exit (1 job run)
Sep 17 07:54:43 motile systemd[1]: anacron.service: Succeeded.
Sep 17 07:59:15 motile rtkit-daemon[1097]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 07:59:15 motile rtkit-daemon[1097]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 07:59:43 motile rsyslogd[762]: [origin software="rsyslogd" swVersion="8.2008.0" x-pid="762" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
-- Reboot --

syslog:

Code: Select all

Sep 17 07:54:43 motile systemd[1]: anacron.service: Succeeded.
Sep 17 07:59:15 motile rtkit-daemon[1097]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 07:59:15 motile rtkit-daemon[1097]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 07:59:43 motile rsyslogd: [origin software="rsyslogd" swVersion="8.2008.0" x-pid="762" x-info="https://www.rsyslog.com"] rsyslogd was HUPed

Exactly a minute later (8:03 am) after the first forced reboot the computer freezes again:

Journalctl:

Code: Select all

Sep 17 08:03:01 motile rtkit-daemon[1063]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 08:03:01 motile rtkit-daemon[1063]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 08:03:03 motile rtkit-daemon[1063]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 08:03:03 motile rtkit-daemon[1063]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 08:03:03 motile rtkit-daemon[1063]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 08:03:03 motile rtkit-daemon[1063]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 08:03:03 motile rtkit-daemon[1063]: Successfully made thread 2526 of process 2381 owned by '1002' RT at priority 10.
Sep 17 08:03:03 motile rtkit-daemon[1063]: Supervising 6 threads of 4 processes of 1 users.
Sep 17 08:03:07 motile xdg-desktop-por[1632]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list
Sep 17 08:10:03 motile pulseaudio[1502]: E: [alsa-sink-ALC269VC Analog] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Sep 17 08:10:03 motile pulseaudio[1502]: E: [alsa-sink-ALC269VC Analog] alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Sep 17 08:10:03 motile pulseaudio[1502]: E: [alsa-sink-ALC269VC Analog] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
-- Reboot --

Kern.log didn't register anything:

Code: Select all

Sep 17 08:02:38 motile kernel: [   13.862224] Lockdown: systemd-logind: hibernation is restricted; see https://wiki.debian.org/SecureBoot
Sep 17 14:15:21 motile kernel: [    0.000000] Linux version 5.8.0-1-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.0-6) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.7-1 (2020-09-05)

Syslog registered an issue with Alsa but I didn't recall that Alsa can lock or freeze a computer:

Code: Select all

Sep 17 08:03:01 motile rtkit-daemon[1063]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 08:03:01 motile rtkit-daemon[1063]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 08:03:03 motile rtkit-daemon[1063]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 08:03:03 motile rtkit-daemon[1063]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 08:03:03 motile rtkit-daemon[1063]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 08:03:03 motile rtkit-daemon[1063]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 08:03:03 motile rtkit-daemon[1063]: Successfully made thread 2526 of process 2381 owned by '1002' RT at priority 10.
Sep 17 08:03:03 motile rtkit-daemon[1063]: Supervising 6 threads of 4 processes of 1 users.
Sep 17 08:03:07 motile xdg-desktop-por[1632]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list
Sep 17 08:10:03 motile pulseaudio[1502]: E: [alsa-sink-ALC269VC Analog] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Sep 17 08:10:03 motile pulseaudio[1502]: E: [alsa-sink-ALC269VC Analog] alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Sep 17 08:10:03 motile pulseaudio[1502]: E: [alsa-sink-ALC269VC Analog] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Sep 17 14:15:21 motile kernel: [    0.000000] Linux version 5.8.0-1-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.0-6) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.7-1 (2020-09-05)

debug log show the rtkit-daemon running before the first freeze

Code: Select all

Sep 17 07:59:15 motile rtkit-daemon[1097]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 07:59:15 motile rtkit-daemon[1097]: Supervising 5 threads of 3 processes of 1 users.

I am really confused...

[sickpig]

However testing has its sense, if I can isolated the issue I can report the bug and helping for the next stable release.

But it doesn't seem that you can isolate the issue.
It seems like you want others to isolate the issue based on the logs that you provide.

"Testing is recommended for advanced users who want new software on their desktops and who are capable of reporting and fixing bugs to help Debian."

from ref:- https://wiki.debian.org/DebianReleases#Choosing

I am really confused...

So, if you are confused and can't isolate or identify the bug then it would be helpful to use stable.

edited - for clarity

[sgosnell]

Sep 15 14:17:01 motile CRON[16772]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 15 14:17:01 motile CRON[16773]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Sep 15 14:17:01 motile CRON[16772]: pam_unix(cron:session): session closed for user root
-- Reboot --

[Danielsan]

So, if you are confused and can't isolate or identify the bug then it would be helpful to use stable.

edited - for clarity

I am confused because and I don't see where the issue is hidden, I have been using Debian testing for ten years so far and this is the first time I have a computer completely frozen without a clear trace. Usually there is some hint in the logs that has always lead me to a solution. The only point is albeit AMD is enough opensource friendly there is long list of issues with the Ryzen cpu, that is why in absence of a clear cause I thought updating the bios might resolve it...

[sickpig]

The only point is albeit AMD is enough opensource friendly there is long list of issues with the Ryzen cpu, that is why in absence of a clear cause I thought updating the bios might resolve it...

Updating bios is not trivial. There is risk of bricking your system.
If you feel the error is due to cron/anacron you can make a note of all cron tasks and then simply uninstall cron and anacron. And check if that fixes it. Then you can re-create the essential tasks or simply create systemd.timers for them.

[Deb-fan]

Big +1 @sickpig, the logs did catch it apparently and a good eye by @sgosnell for weeding through them, any way had some brainfarts to add to this mess, running xyz-jobs manually, one-by-one, if while doing so you experience a reboot/freeze or crash, clearly you need to rework that cron-job, script ... whatever.

Something else which popped into bean is adding something like echo "cronjob xyz ran $(date)" >> /path/to/logfile to the beginning of them, not like folks should really have 400 cronjobs set on any given system but still the idea is obvious, they log each time they're run, or add a lil bit more to it and entry could include whether the job successfully completed too, though should definitely execute the parts necessary to complete the logging, then if you experience a crash + check that log file, there's probably your culprit, investigate further and check out what's going wrong with and fix it.

Lastly of course agree, with things like systemd timers around now, am definitely considering getting rid of cron and anacron altogether, when better tools get introduced makes no sense not to use them, why have multiple redundant services/daemons running, at least in my view and only a pointless 2 cents on it. Mostly just wanted to note that hair brained concept above, as it could have some interesting uses.