System freeze in Debian 12

[alienspy]

Hello! I have recently installed Debian 12 on my desktop PC and from time to time i experience unrecoverable full system freeze. The screen is freeze in one state, i can't move a mouse, keyboard doesn't respond. CTRL-ALT-F1... doesn't help. I have to push a restart button on the computer. It happens around 2-3 times a day.

The thing is previously i had MX Linux 21AHS (Debian 11 based) on this computer and few month ago it started to give me such freezes. Then i thought the problem is in MX, as i used it with systemd and GNOME, which i thought was FrankenMX. I have Windows 10 dual-boot here, and Windows works fine all the time. So i don't think it is a hardware.

I don't do nothing special when such freezes, office, Web.

Last time it happened right after boot when i opened Firefox

journalctl --since "1 hour ago"

Code: Select all

Jun 15 15:02:43 debian gnome-shell[1574]: GNOME Shell started at Thu Jun 15 2023 15:02:41 GMT+0300
Jun 15 15:02:43 debian gnome-shell[1574]: Registering session with GDM
Jun 15 15:02:43 debian gnome-software[1880]: enabled plugins: fwupd, os-release, appstream, flatpak, hardcoded-blocklist, modalias, packagekit, rewrite->
Jun 15 15:02:43 debian gnome-software[1880]: disabled plugins: dpkg, dummy, repos, epiphany
Jun 15 15:02:50 debian systemd[1361]: Started app-gnome-firefox\x2desr-2424.scope - Application launched by gnome-shell.
Jun 15 15:02:51 debian systemd[1361]: Reached target gnome-session-x11-services.target - GNOME session X11 services.
Jun 15 15:02:51 debian gnome-shell[2437]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jun 15 15:02:51 debian gnome-shell[2437]: > Warning:          Unsupported maximum keycode 708, clipping.
Jun 15 15:02:51 debian gnome-shell[2437]: >                   X11 cannot support keycodes above 255.
Jun 15 15:02:51 debian systemd[1361]: Starting org.gnome.SettingsDaemon.XSettings.service - GNOME XSettings service...
Jun 15 15:02:51 debian gnome-shell[2437]: Errors from xkbcomp are not fatal to the X server
Jun 15 15:02:51 debian systemd[1361]: Started org.gnome.SettingsDaemon.XSettings.service - GNOME XSettings service.
Jun 15 15:02:51 debian systemd[1361]: Reached target gnome-session-x11-services-ready.target - GNOME session X11 services.
Jun 15 15:02:51 debian gnome-shell[1574]: ATK Bridge is disabled but a11y has already been enabled.
Jun 15 15:02:51 debian firefox-esr.desktop[2424]: ATTENTION: default value of option mesa_glthread overridden by environment.
Jun 15 15:02:51 debian firefox-esr.desktop[2424]: ATTENTION: default value of option mesa_glthread overridden by environment.
Jun 15 15:02:52 debian gnome-shell[1574]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00097
Jun 15 15:02:52 debian gnome-shell[1574]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00097
Jun 15 15:02:52 debian firefox-esr.desktop[2424]: Missing chrome or resource URL: resource://gre/modules/UpdateListener.jsm
Jun 15 15:02:52 debian firefox-esr.desktop[2424]: Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs
Jun 15 15:02:55 debian firefox-esr.desktop[2713]: [2023-06-15T12:02:55Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 15 15:02:55 debian firefox-esr.desktop[2713]: [2023-06-15T12:02:55Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 15 15:02:55 debian firefox-esr.desktop[2713]: [2023-06-15T12:02:55Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 15 15:02:55 debian firefox-esr.desktop[2713]: [2023-06-15T12:02:55Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 15 15:03:11 debian firefox-esr.desktop[2889]: [2023-06-15T12:03:11Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 15 15:03:11 debian firefox-esr.desktop[2889]: [2023-06-15T12:03:11Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 15 15:03:11 debian firefox-esr.desktop[2889]: [2023-06-15T12:03:11Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 15 15:03:11 debian firefox-esr.desktop[2889]: [2023-06-15T12:03:11Z ERROR mp4parse] Found 2 nul bytes in "\0\0"

inxi -b

Code: Select all

System:
  Host: debian Kernel: 6.1.0-9-amd64 arch: x86_64 bits: 64 Desktop: GNOME
    v: 43.4 Distro: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: Gigabyte product: B360 HD3 v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: B360HD3 v: x.x serial: <superuser required>
    UEFI: American Megatrends v: F11 date: 09/17/2018
CPU:
  Info: 6-core Intel Core i5-8400 [MCP] speed (MHz): avg: 800
    min/max: 800/4000
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050] driver: nouveau v: kernel
  Display: wayland server: X.Org v: 1.22.1.9 with: Xwayland v: 22.1.9
    compositor: gnome-shell driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa dri: nouveau gpu: nouveau
    resolution: 1920x1080~75Hz
  API: OpenGL v: 4.3 Mesa 22.3.6 renderer: NV137
Network:
  Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
Drives:
  Local Storage: total: 1.64 TiB used: 40.67 GiB (2.4%)
Info:
  Processes: 271 Uptime: 29m Memory: 15.55 GiB used: 3.01 GiB (19.4%)
  Shell: Bash inxi: 3.3.26

Would be glad to here any ideas.

[None1975]

Hello. It looks like you are using an open source video driver for Nvidia card. Try to install NVIDIA proprietary display driver. You can read how to do this on the Debian wiki.

[Aki]

Hello,

From this log:

Code: Select all

Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050] driver: nouveau v: kernel
  Display: wayland server: X.Org v: 1.22.1.9 with: Xwayland v: 22.1.9
    compositor: gnome-shell driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa dri: nouveau gpu: nouveau
    resolution: 1920x1080~75Hz
  API: OpenGL v: 4.3 Mesa 22.3.6 renderer: NV137

is reported "driver: nouveau" in:

Code: Select all

Device-1: NVIDIA GP107 [GeForce GTX 1050] driver: nouveau v: kernel

and the "dri: nouveau gpu: nouveau" in:

Code: Select all

unloaded: fbdev,modesetting,nouveau,vesa dri: nouveau gpu: nouveau

and "renderer: NV137" in:

Code: Select all

API: OpenGL v: 4.3 Mesa 22.3.6 renderer: NV137

Therefore, it seems that your are running the nouveau kernel module (to drive the nvidia gpu) with the wayland server.

Before replacing the kernel module, you could try to configure Xorg as the default GNOME session: see https://docs.fedoraproject.org/en-US/qu ... e-session/

[alienspy]

Hello. It looks like you are using an open source video driver for Nvidia card. Try to install NVIDIA proprietary display driver. You can read how to do this on the Debian wiki.

Yes, i am. Is it that bad? I tried to install proprietary driver, but failed. I will make a different topic for that.

I have recalled that, while using MX linux i had .510 driver and it worked fine, but after updating to .520 i received "no input" on the monitor and had to switch on open-source (Threrad on MX Forum). Maybe, maybe after that the freezes began. Unfortunately, i don't remember now if tried Xorg instead of Wayland.

[alienspy]

Therefore, it seems that your are running the nouveau kernel module (to drive the nvidia gpu) with the wayland server.

Before replacing the kernel module, you could try to configure Xorg as the default GNOME session: see https://docs.fedoraproject.org/en-US/qu ... e-session/

I have switched to Xorg, thanks. I didn't know that open-source driver doesn't work well with Wayland.

Why should i change kernel? For the new version of Nouveau?

As i wrote above in different answer, yes, maybe the problem is in driver, but unfortunately i didn't manage to successfully install proprietary driver. I will write about it in different topic.

I am trying to remember all the last changes in the PC. For the last couple of month i have changed wi-fi module to TP-Link-Archer-TX50E and bought a new power supply. I don't know if it means something.

[Aki]

Therefore, it seems that your are running the nouveau kernel module (to drive the nvidia gpu) with the wayland server.

Before replacing the kernel module, you could try to configure Xorg as the default GNOME session: see https://docs.fedoraproject.org/en-US/qu ... e-session/

I have switched to Xorg, thanks. I didn't know that open-source driver doesn't work well with Wayland.

Why should i change kernel? For the new version of Nouveau?
[..]

Happy you sorted it out.

I was suggesting not to update the kernel module (a kernel component) for the GPU before testing if switching to Xorg was helpful. In Linux the so called "drivers" (for proprietary OS like Windows) are modules of the kernel.

If the nouveau kernel modules works as is, there's no need to update it or the kernel itself. :-)

[alienspy]

If the nouveau kernel modules works as is, there's no need to update it or the kernel ?

I play SuperTuxKart and Xonotic on Linux and unfortunately its perfomance is very bad with open-source module. So switch to proprietary module is preferable if possible.

UPD. Topic about Nvidia driver

[Aki]

Hi,
Please, if possible, mark the thread as "Solved" adding to tag "[Solved]" to the subject of the first post, for example:

[Solved] System freeze in Debian 12

[alienspy]

Hi,
Please, if possible, mark the thread as "Solved" adding to tag "[Solved]" to the subject of the first post, for example:

[Solved] System freeze in Debian 12

Can i wait for a couple of days to be sure that the problem is in driver/Wayland, if i may?

[Aki]

Hi,
Please, if possible, mark the thread as "Solved" adding to tag "[Solved]" to the subject of the first post, for example:

[Solved] System freeze in Debian 12

Can i wait for a couple of days to be sure that the problem is in driver/Wayland, if i may?

Yes, of course.

[alienspy]

Please, if possible, mark the thread as "Solved" adding to tag "[Solved]" to the subject of the first post, for example:

Oh, no, it happened again Same error

I am on Xorg now

Code: Select all

Jun 17 15:51:29 debian gnome-shell[1693]: GNOME Shell started at Sat Jun 17 2023 15:51:27 GMT+0300
Jun 17 15:51:29 debian gnome-shell[1693]: Registering session with GDM
Jun 17 15:51:33 debian systemd[1371]: Started app-gnome-firefox\x2desr-2409.scope - Application launched by gnome-shell.
Jun 17 15:51:33 debian firefox-esr.desktop[2409]: ATTENTION: default value of option mesa_glthread overridden by environment.
Jun 17 15:51:33 debian firefox-esr.desktop[2409]: ATTENTION: default value of option mesa_glthread overridden by environment.
Jun 17 15:51:33 debian firefox-esr.desktop[2409]: ATTENTION: default value of option mesa_glthread overridden by environment.
Jun 17 15:51:34 debian firefox-esr.desktop[2409]: Missing chrome or resource URL: resource://gre/modules/UpdateListener.jsm
Jun 17 15:51:34 debian firefox-esr.desktop[2409]: Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs
Jun 17 15:51:37 debian firefox-esr.desktop[2670]: [2023-06-17T12:51:37Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 17 15:51:37 debian firefox-esr.desktop[2670]: [2023-06-17T12:51:37Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 17 15:51:37 debian firefox-esr.desktop[2670]: [2023-06-17T12:51:37Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 17 15:51:37 debian firefox-esr.desktop[2670]: [2023-06-17T12:51:37Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 17 15:51:37 debian firefox-esr.desktop[2666]: [2023-06-17T12:51:37Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 17 15:51:37 debian firefox-esr.desktop[2666]: [2023-06-17T12:51:37Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 17 15:51:37 debian firefox-esr.desktop[2666]: [2023-06-17T12:51:37Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Jun 17 15:51:37 debian firefox-esr.desktop[2666]: [2023-06-17T12:51:37Z ERROR mp4parse] Found 2 nul bytes in "\0\0"

But now it looks like a problem with Mozilla itself, right? https://support.mozilla.org/en-US/questions/1403292 and https://bugzilla.mozilla.org/show_bug.cgi?id=1744389

Another problem with the same freeze symptom? Am i cursed?

Is there a possibility that the current version of nouveau just doesn't work fine with my particular GPU?

[fabien]

But now it looks like a problem with Mozilla itself, right?

If so, have you tried disabling hardware acceleration? There are maybe other relevant options in about: config, that's just a lead.

[Aki]

Hello,

Are you running the applications that freeze your computer as flatpacks or appimage ?

I don't see kernel error messages in the log you sent so far, therefore there are no clues that the nouveau kernel module is involved (at least, by now).

[alienspy]

But now it looks like a problem with Mozilla itself, right?

If so, have you tried disabling hardware acceleration? There are maybe other relevant options in about: config, that's just a lead.

Not yet, i will try, thank you.

Are you running the applications that freeze your computer as flatpacks or appimage ?

No, i don't. Ok, i hope it is smth with FF. I will look into it, thank you.

[Random_Troll]

Firefox can only use VA-API for hardware acceleration under Linux and NVIDIA can only use that via CUDA and some custom software, which is not available from the Debian repositories.

If in doubt blame the blob

Can you use the nvidia-open-kernel-dkms package instead of the proprietary driver? Not sure if that will work though, I don't use NVIDIA.

[alienspy]

Can you use the nvidia-open-kernel-dkms package instead of the proprietary driver? Not sure if that will work though, I don't use NVIDIA.

I am already on open-source

Oh, sigh, that's the other TOPIC

Firefox can only use VA-API for hardware acceleration under Linux and NVIDIA can only use that via CUDA

I don't know about such things unfortunately, you mean i can't disable hardware accelaration..?

[Random_Troll]

I mean hardware acceleration is not available for your hardware, no matter what the checkbox in FF says.

I am already on open-source

There are two open source alternatives for NVIDIA cards in bookworm. Have you tried both nouveau and nvidia-open?

[alienspy]

There are two open source alternatives for NVIDIA cards in bookworm. Have you tried both nouveau and nvidia-open?

Wow, i didn't even know about it. I will look into it. Thanks

So hardware acceleration can't be a problem here because there is no such thing in fact here?

[Random_Troll]

There's no hardware acceleration for Firefox. It should work elsewhere though.

[alienspy]

Today i got a freeze, while CLOSING on of the windows of flatpak version of FireFox.

I have installed stable version from the binaries and disabled hardware support (just in case...).

If the error will appear again probably i should start another particular thread.

Should also check performance of other browsers for the sake of experiment, probably.