System crashes after waking up from sleep

General system Kernel, boot, graphics & hardware
1

System crashes after waking up from sleep.
After some recent updates system crashes when I try to wake it up. I never seen that type of messages before.
Does anyone know what can cause them to happen?

inxi -Fxxc0z --no-host and screens of error

20240705_182648
20240705_1826481920Ă—1440 399 KB

20240705_182716
20240705_1827161920Ă—1440 543 KB

inxi -Fxxc0z --no-host
System:
Kernel: 6.9.8-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
Desktop: KDE Plasma v: 6.1.2 tk: Qt v: N/A wm: kwin_x11 dm: SDDM
Distro: EndeavourOS base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: H67DE3/SI serial:
BIOS: American Megatrends v: P1.30 date: 02/21/2011
CPU:
Info: quad core model: Intel Core i5-2500 bits: 64 type: MCP
arch: Sandy Bridge rev: 7 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 1599 high: 1600 min/max: 1600/3700 cores: 1: 1600
2: 1596 3: 1600 4: 1600 bogomips: 26348
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: NVIDIA GP107 [GeForce GTX 1050] vendor: Micro-Star MSI
driver: nvidia v: 555.58.02 arch: Pascal pcie: speed: 5 GT/s lanes: 16
ports: active: none off: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 01:00.0
chip-ID: 10de:1c81
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 92
Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: Huawei SSN-24
res: 1920x1080 dpi: 93 diag: 604mm (23.8")
API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 555.58.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1050/PCIe/SSE2
API: Vulkan v: 1.3.279 surfaces: xcb,xlib device: 0 type: discrete-gpu
driver: nvidia device-ID: 10de:1c81
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:1c20
Device-2: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: speed: 5 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:0fb9
API: ALSA v: k6.9.8-arch1-1 status: kernel-api
Server-1: PipeWire v: 1.2.0 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASRock driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
port: d000 bus-ID: 06:00.0 chip-ID: 10ec:8168
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac:
IF-ID-1: outline-tun0 state: down mac: N/A
Drives:
Local Storage: total: 2.73 TiB used: 325.73 GiB (11.7%)
ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-00BBHA0
size: 931.51 GiB speed: 6.0 Gb/s serial:
ID-2: /dev/sdb vendor: Western Digital model: WD10EZEX-08WN4A0
size: 931.51 GiB speed: 6.0 Gb/s serial:
ID-3: /dev/sdc vendor: Samsung model: HD103SJ size: 931.51 GiB
speed: 6.0 Gb/s serial:
Partition:
ID-1: / size: 901.05 GiB used: 325.73 GiB (36.1%) fs: ext4 dev: /dev/sdb1
Swap:
ID-1: swap-1 type: partition size: 15 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sdb2
Sensors:
System Temperatures: cpu: 36.0 C mobo: N/A gpu: nvidia temp: 40 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 45%
Info:
Memory: total: 16 GiB note: est. available: 13.63 GiB used: 3.3 GiB (24.2%)
Processes: 228 Power: uptime: 2h 34m wakeups: 0 Init: systemd v: 256
default: graphical
Packages: 1363 pm: pacman pkgs: 1332 pm: flatpak pkgs: 31 Compilers:
clang: 18.1.8 gcc: 14.1.1 Shell: fish v: 3.7.1 running-in: kitty
inxi: 3.3.35

2
3

Well, I actually already have this file. Is there a way to check if a parameter was successfully added?

4 
cat /proc/cmdline

May do it.

5

That’s all I got:

BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=… rw nowatchdog nvme_load=YES resume=UUID=… loglevel=3 nvidia-drm.modeset=1 nvidia-drm.fbdev=1

6

What is in nvidia-power-management.conf?

:Edit:
It should be this - all on one line:

options nvidia NVreg_PreserveVideoMemoryAllocations=1 NVreg_TemporaryFilePath=/var/tmp
1 Like
7
nvidia-power-management.conf

pm

8

See above.

9

OK, changed it to one line. Now I need to regenerate initramfs?

10

Yes, Dracut? Just run sudo reinstall-kernels

11

Yes, I use Dracut, but for some reason there is no command sudo reinstall-kernels.
I used something like:
sudo dracut --hostonly --no-hostonly-cmdline --force /boot/initramfs-linux.img
for each kernel.
Unfortunately it still crashes with similar message. I can post a bigger photo if needed.

12

Just sudo dracut-rebuild this is EndeavourOS, not Arch?

That is a core dump, something really very wrong.

reinstall-kernels is in:

/usr/bin/reinstall-kernels is owned by kernel-install-for-dracut 1.10.1-1

1 endeavouros/kernel-install-for-dracut 1.10.1-1 (18.3 KiB 20.8 KiB) (Installed)
    Enables systemd-boot automation using kernel-install with dracut
2 Likes
13

This command actually exists but after reboot the problem is still there.

Also there is a message:

:: Building initramfs for linux (6.9.8-arch1-1)
/etc/dracut.conf.d/nvidia.conf: line 1: nvidia: command not found
…

/etc/dracut.conf.d/nvidia.conf/

force_drivers+=” nvidia nvidia-drm nvidia-modeset nvidia-uvm ”

14

Is there anything else I could try?

15

I am out of ideas :frowning:

16

I guess the only way is to wait for the next NVIDIA driver update or downgrade the current one.
Maybe switching to Wayland could help, but I really doubt that.
Still thank you for your help, now I know about sudo dracut-rebuild.

17

The entry in the nvidia-power-management.conf and the command dracut-rebuild solved the problem on my computer.
thanks a lot. :+1:

18
  1. What video card do you have?
  2. Do you use x11 or Wayland?
19

Gtx1070 with driver 555 and wayland.

20

Well, it seems to be working for me too. I had big doubts about Wayland, but now it works. The only thing left to figure out is how to launch apps for x11.