You are not logged in.

#1 2022-09-09 10:53:39

Asdrubale112
Member
Registered: 2021-11-08
Posts: 11

Kernel panic after suspend

Hello everyone,
recently I have one issue that prevent me from waking up the pc after suspending it.
I recently installed open source nvidia drivers (version 515.65.01-10) and now I cannot suspend the pc because if I try to waking it up, the caps lock starts to blink and the screen stays black.
The strange part is that if I try to suspend the device and waking it up after about 5 seconds the system works, but if I wait like a minute the system will not work and the caps lock will start blinking.
After rebooting I don't know how to troubleshoot this because "sudo journalctl -b -1" end like this:

Sep 09 12:23:49 user systemd[1]: Starting System Suspend...

I have configured

options nvidia-drm modeset=1

in my "/etc/modprobe.d/" folder

Thanks in advance.

Offline

#2 2022-09-09 10:57:04

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,263

Re: Kernel panic after suspend

That's a known problem with nvidia-open. Try to check/reproduce with the normal nvidia package.

Offline

#3 2022-09-09 12:50:10

Asdrubale112
Member
Registered: 2021-11-08
Posts: 11

Re: Kernel panic after suspend

Thank you for your replay.
I'm trying to switch to the proprietary drivers but I cannot understand why the kernel keeps loading the nouveau drivers.
Before installing the drivers I upgraded the system with "pacman -Syu". After rebooting "lspci -v" shows:

01:00.0 3D controller: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] (rev a1)
	Subsystem: Dell Device 0a5d
	Flags: bus master, fast devsel, latency 0, IRQ 255
	Memory at a9000000 (32-bit, non-prefetchable) [size=16M]
	Memory at 6000000000 (64-bit, prefetchable) [size=4G]
	Memory at 6100000000 (64-bit, prefetchable) [size=32M]
	I/O ports at 3000 [disabled] [size=128]
	Expansion ROM at <ignored> [disabled]
	Capabilities: <access denied>
	Kernel modules: nouveau, nvidia_drm, nvidia

and "nvidia-smi" exits with the error:

NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

After that I tried appending to the initramfs

MODULES=(btrfs nvidia nvidia_modeset nvidia_uvm nvidia_drm)

, run "mkinitcpio -P" and reboot but it doesn't work.
I checked "lsmod | grep nvidia" and the result is only this row

nvidia              45387776  1

Lastly these are the nvidia packages that I have currenty on my system

local/egl-wayland 2:1.1.11-2
    EGLStream-based Wayland external platform
local/libnvidia-container 1.10.0-1
    NVIDIA container runtime library
local/libnvidia-container-tools 1.10.0-1
    NVIDIA container runtime library
local/libvdpau 1.5-1
    Nvidia VDPAU library
local/nvidia 515.65.01-12
    NVIDIA drivers for linux
local/nvidia-container-runtime 3.10.0-2
    NVIDIA opencontainer runtime fork to expose GPU devices to containers.
local/nvidia-container-toolkit 1.10.0-1
    NVIDIA container runtime toolkit
local/nvidia-docker 2.11.0-1
    Build and run Docker containers leveraging NVIDIA GPUs
local/nvidia-prime 1.0-4
    NVIDIA Prime Render Offload configuration and utilities
local/nvidia-utils 515.65.01-2
    NVIDIA drivers utilities

I don't know what I'm missing.
Thanks in advance

Offline

#4 2022-09-09 15:40:16

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,263

Re: Kernel panic after suspend

Add ibt=off to your kernel parameters, see the blue note box https://wiki.archlinux.org/title/NVIDIA#Installation

Offline

Board footer

Powered by FluxBB