On 04.01.2021 04:41, David Christensen wrote:
On 2021-01-03 06:51, Alexander V. Makartsev wrote:
On 03.01.2021 02:52, David Christensen wrote:
Any suggestions for trouble-shooting the crashes?
Have you checked the systemd journal?
Even after you reboot frozen system you can see last syslog messages
easily from previous boot with this command:
$ sudo journalctl -b -1
Journald keeps logs from multiple previous boots.
$ sudo journalctl --list-boots
You can select them by index. ( "0" is current boot, "-1" is previous
boot, etc. )
2021-01-03 14:01:19 root@dipsy ~
# journalctl -b -1
Specifying boot ID or boot offset has no effect, no persistent journal
was found.
2021-01-03 14:01:29 root@dipsy ~
# journalctl --list-boots
0 8b60854b67c243679bec112a7050f054 Sun 2021-01-03 14:01:00
PST<E2><80><94>Sun 2
No of much use (?).
Sorry, I completely forgot this feature isn't yet [1] enabled by default.
This is what I get on my system:
$ journalctl --list-boots | tail -n3
-2 e9c28f25bcbe4e26a93e519d231e046e Fri 2021-01-01 19:42:32 +05—Sat
2021-01-02 03:28:07 +05
-1 766d50af660f4904839a3f6b1aa5b2c2 Sat 2021-01-02 11:31:12 +05—Sun
2021-01-03 06:46:03 +05
0 a65baabd511b490eb65d2e8c69e70700 Sun 2021-01-03 12:37:32 +05—Mon
2021-01-04 05:00:01 +05
Start Firefox, browse YouTube, play video "Relaxing Christmas Jazz
Music 10 Hours" (not in full screen) -- crashes after ~50 minutes:
2021-01-03 15:35:15 root@dipsy ~
# journalctl -b -1
Specifying boot ID or boot offset has no effect, no persistent journal
was found.
2021-01-03 15:35:18 root@dipsy ~
# journalctl --list-boots
0 8b60854b67c243679bec112a7050f054 Sun 2021-01-03 14:01:00
PST<E2><80><94>Sun 2
Again, not of much use (?). How do I get information out of the
systemd journal?
You can read a brief tutorial on journal here. [2]
For now, until you enable persistent journal, you have only current boot
journal:
$ journalctl -b 0
dmesg(1) has some information, both about boot and the crash:
2021-01-03 15:40:11 root@dipsy ~
# dmesg | grep nouveau | tail
[ 2964.485920] nouveau 0000:01:00.0: Xorg[731]: nv50cal_space: -16
[ 2964.542072] nouveau 0000:01:00.0: Xorg[731]: nv50cal_space: -16
[ 2964.598799] nouveau 0000:01:00.0: Xorg[731]: nv50cal_space: -16
[ 2964.654669] nouveau 0000:01:00.0: Xorg[731]: nv50cal_space: -16
[ 2964.710811] nouveau 0000:01:00.0: Xorg[731]: nv50cal_space: -16
[ 2964.767008] nouveau 0000:01:00.0: Xorg[731]: nv50cal_space: -16
[ 2964.822927] nouveau 0000:01:00.0: Xorg[731]: nv50cal_space: -16
[ 2964.879084] nouveau 0000:01:00.0: Xorg[731]: nv50cal_space: -16
[ 2964.935106] nouveau 0000:01:00.0: Xorg[731]: nv50cal_space: -16
[ 2964.991455] nouveau 0000:01:00.0: Xorg[731]: nv50cal_space: -16
2021-01-03 15:40:14 root@dipsy ~
# dmesg | grep nouveau | wc
519 3686 34789
Suggestions?
It looks like "nouveau" deadlock bug. [3] Have you tried to install
proprietary driver?
Last supported driver version for your VGA is 390, so you will need to
install "nvidia-legacy-390xx-driver" package from Debian non-free repo.
$ sudo apt install nvidia-legacy-390xx-driver
nvidia-legacy-390xx-kernel-dkms nvidia-legacy-390xx-kernel-support
[1] https://lists.debian.org/debian-devel/2020/02/msg00000.html
[2]
https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs
[3] https://bugs.freedesktop.org/show_bug.cgi?id=81690
--
With kindest regards, Alexander.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀
