Hello everyone,
As this is my first post do not hesitate to mak me udpate or move if it is not in the correct sub-topic.
I consider myself as a beginner on Debian.
I setup a server for CFD calculations for our small company with debian 12 on it.
It has a dual Xeon CPU and some RAM on it, it is a second hand hardware.
When I first setup the server a month ago, it seemed as a RAM memory was not seen in the bios, I switched between 2 RAM memories and it worked, so I setup memtest86 in GRUB and checked all the RAM during a few hours and no errors.
But you will see with the current bug I still suspect the RAM.
It worked quite flawlessly the first times, but now it is often freezing (once a day now) when the CPU usage is high (a simulation running).
What I do not understand is that now my memtest86 is not working "error file "EFI/memtest86/BOOTX64.efi" not available. I am currently trying to solve this as the RAM is my first suspect.
When the crashes started to occur I updated the system, I also saw that nvidia drivers could caus crash so I changed them to proprietary drivers.
But it does not change anything.
The logs I have are the following
DEBIAN 12 crash log
sudo journalctl --since "1 hour ago"
~$ inxi -bIf you have any clues it would be very helpful! Thanks
FG
As this is my first post do not hesitate to mak me udpate or move if it is not in the correct sub-topic.
I consider myself as a beginner on Debian.
I setup a server for CFD calculations for our small company with debian 12 on it.
It has a dual Xeon CPU and some RAM on it, it is a second hand hardware.
When I first setup the server a month ago, it seemed as a RAM memory was not seen in the bios, I switched between 2 RAM memories and it worked, so I setup memtest86 in GRUB and checked all the RAM during a few hours and no errors.
But you will see with the current bug I still suspect the RAM.
It worked quite flawlessly the first times, but now it is often freezing (once a day now) when the CPU usage is high (a simulation running).
What I do not understand is that now my memtest86 is not working "error file "EFI/memtest86/BOOTX64.efi" not available. I am currently trying to solve this as the RAM is my first suspect.
When the crashes started to occur I updated the system, I also saw that nvidia drivers could caus crash so I changed them to proprietary drivers.
But it does not change anything.
The logs I have are the following
DEBIAN 12 crash log
sudo journalctl --since "1 hour ago"
Code:
sept. 03 11:35:17 SIL3XHPC01 sshd[6037]: Accepted password for matthieu from 81.220.138.244 port 49916 ssh2sept. 03 11:35:17 SIL3XHPC01 sshd[6037]: pam_unix(sshd:session): session opened for user matthieu(uid=1001) by (uid=0)sept. 03 11:35:17 SIL3XHPC01 systemd-logind[1785]: New session 11 of user matthieu.sept. 03 11:35:17 SIL3XHPC01 systemd[1]: Started session-11.scope - Session 11 of User matthieu.sept. 03 11:35:17 SIL3XHPC01 sshd[6037]: pam_env(sshd:session): deprecated reading of user environment enabledsept. 03 11:37:00 SIL3XHPC01 kernel: hugetlbfs: cs_solver (6656): Using mlock ulimits for SHM_HUGETLB is obsoletesept. 03 11:38:09 SIL3XHPC01 dbus-daemon[3028]: [session uid=1001 pid=3028] Activating service name='org.gnome.gedit' requested by ':1.100' (uid=1001 pid=4415 comm="/usr/bin/nautilus --gapplication-service")sept. 03 11:38:09 SIL3XHPC01 dbus-daemon[3028]: [session uid=1001 pid=3028] Successfully activated service 'org.gnome.gedit'sept. 03 11:38:16 SIL3XHPC01 dbus-daemon[3028]: [session uid=1001 pid=3028] Activating service name='org.gnome.gedit' requested by ':1.100' (uid=1001 pid=4415 comm="/usr/bin/nautilus --gapplication-service")sept. 03 11:38:16 SIL3XHPC01 dbus-daemon[3028]: [session uid=1001 pid=3028] Successfully activated service 'org.gnome.gedit'sept. 03 11:39:36 SIL3XHPC01 dbus-daemon[3028]: [session uid=1001 pid=3028] Activating service name='org.gnome.gedit' requested by ':1.100' (uid=1001 pid=4415 comm="/usr/bin/nautilus --gapplication-service")sept. 03 11:39:36 SIL3XHPC01 dbus-daemon[3028]: [session uid=1001 pid=3028] Successfully activated service 'org.gnome.gedit'sept. 03 11:41:39 SIL3XHPC01 gnome-shell[3360]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5584fe7dc750] is on because it needs an allocation.sept. 03 11:41:39 SIL3XHPC01 gnome-shell[3360]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5584f8fb99a0] is on because it needs an allocation.sept. 03 11:41:45 SIL3XHPC01 dbus-daemon[3028]: [session uid=1001 pid=3028] Activating service name='org.gnome.gedit' requested by ':1.100' (uid=1001 pid=4415 comm="/usr/bin/nautilus --gapplication-service")sept. 03 11:41:45 SIL3XHPC01 dbus-daemon[3028]: [session uid=1001 pid=3028] Successfully activated service 'org.gnome.gedit'sept. 03 11:41:46 SIL3XHPC01 gnome-shell[3360]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5584f80d7f30] is on because it needs an allocation.sept. 03 11:41:46 SIL3XHPC01 gnome-shell[3360]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5584f8fb9610] is on because it needs an allocation.sept. 03 11:44:47 SIL3XHPC01 dbus-daemon[3028]: [session uid=1001 pid=3028] Activating service name='org.gnome.gedit' requested by ':1.100' (uid=1001 pid=4415 comm="/usr/bin/nautilus --gapplication-service")sept. 03 11:44:47 SIL3XHPC01 dbus-daemon[3028]: [session uid=1001 pid=3028] Successfully activated service 'org.gnome.gedit'sept. 03 11:44:48 SIL3XHPC01 gnome-shell[3360]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5584fe7dc750] is on because it needs an allocation.sept. 03 11:44:48 SIL3XHPC01 gnome-shell[3360]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5584f8fb9d30] is on because it needs an allocation.sept. 03 11:45:01 SIL3XHPC01 dbus-daemon[3028]: [session uid=1001 pid=3028] Activating service name='org.gnome.gedit' requested by ':1.100' (uid=1001 pid=4415 comm="/usr/bin/nautilus --gapplication-service")sept. 03 11:45:01 SIL3XHPC01 dbus-daemon[3028]: [session uid=1001 pid=3028] Successfully activated service 'org.gnome.gedit'sept. 03 11:45:02 SIL3XHPC01 gnome-shell[3360]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5584f80d7f30] is on because it needs an allocation.sept. 03 11:45:02 SIL3XHPC01 gnome-shell[3360]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5584f8fb99a0] is on because it needs an allocation.sept. 03 11:45:03 SIL3XHPC01 gnome-shell[3360]: Object .Gjs_ui_messageTray_Notification (0x5584f9255b40), has been already disposed — impossible to emit any signal on it. This might be caused by the object h>sept. 03 11:45:03 SIL3XHPC01 gnome-shell[3360]: == Stack trace for context 0x5584f7734190 ==sept. 03 11:45:03 SIL3XHPC01 gnome-shell[3360]: #0 5584f7ec5418 i resource:///org/gnome/shell/ui/messageTray.js:493 (18e5e6821a10 @ 69)Code:
System: Host: SIL3XHPC01 Kernel: 6.1.0-25-amd64 arch: x86_64 bits: 64 Console: pty pts/0 Distro: Debian GNU/Linux 12 (bookworm)Machine: Type: Desktop System: HP product: HP Z8 G4 Workstation v: SBKPF,DWKSBLF serial: <superuser required> Mobo: HP model: 81C7 v: MVB 0C serial: <superuser required> UEFI: HP v: P60 v02.94 date: 05/17/2024CPU: Info: 2x 28-core Intel Xeon Platinum 8276 [MT MCP SMP] speed (MHz): avg: 1000 min/max: 1000/4000Graphics: Device-1: NVIDIA GP107GL [Quadro P1000] driver: nvidia v: 535.183.01 Display: server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia tty: 208x30 API: OpenGL Message: GL data unavailable in console. Try -G --displayNetwork: Device-1: Intel Ethernet I219-LM driver: e1000e Device-2: Intel Ethernet X722 driver: N/A Device-3: Intel Ethernet X722 for 1GbE driver: i40eDrives: Local Storage: total: 25.55 TiB used: 776.18 GiB (3.0%)Info: Processes: 980 Uptime: 37m Memory: 376.58 GiB used: 5.32 GiB (1.4%) Init: systemd target: graphical (5) Shell: Bash inxi: 3.3.26FG
Statistics: Posted by furby_goulag — 2024-09-03 14:00 — Replies 5 — Views 107