You are not logged in.

#51 2021-05-03 15:00:59

evil.genius
Member
Registered: 2016-02-13
Posts: 7

Re: nvidia driver causes kernel panic

ammonium wrote:

Could it be the resolution or the signal? When I look at the nvidia-settings on the DP-X specific page it says that the signal is TMDS, is this different from normal?

Both of my monitors are running at 1440p over DP. One works and one doesn't, so I don't think resolution is the issue. The only difference between the two is that one is using four lanes and the other (non-working) one uses two.

I think TMDS is only for HDMI and not DP, so likely not relevant. I'm not sure though.

This thread on the nvidia forum seems to be the same problem and has received a response from an nvidia dev:
https://forums.developer.nvidia.com/t/4 … t/175782/8

Offline

#52 2021-05-03 16:22:49

ShayBox
Member
Registered: 2021-05-03
Posts: 3

Re: nvidia driver causes kernel panic

Same problem
Previously: 1080p DP, 720p DP to VGA, 2nd 720p HDMI to VGA, Valve Index DP
Now: 1440p DP, 1080p DP, 720p HDMI to VGA, Valve Index DP
Seems to be when the total size of the X screen exceeds a size not the connector type, but I could be wrong.

Offline

#53 2021-05-03 22:16:58

ammonium
Member
Registered: 2021-04-21
Posts: 4

Re: nvidia driver causes kernel panic

ammonium wrote:

So I tested again now using a "DP to HDMI converter" (using the DP-out from the GPU and converting it to HDMI) and again it worked fine. Unfortunately this adapter/converter is limited to 1080p and the monitor is 1440p

Just an update: Testing with another 'DP to HDMI adapter' it also works with the monitor's native resolution. I'm using 4k over HDMI + 1440p over DP converted to HDMI and everything is working correctly with kernel 5.11.16-arch1-1 and Nvidia driver 465.27. Weird workaround but that's what we got for now

Offline

#54 2021-05-04 08:20:03

O_o
Member
Registered: 2021-05-04
Posts: 1

Re: nvidia driver causes kernel panic

Not a kernel panic but related: after an upgrade on April 29, my machine started freezing randomly, with a pattern of most freezes happening when the display went to sleep. This happened 2-3 times an hour, so it meant either a hardware issue or an upgrade issue.

Found this thread and downgraded packages as per MetalMatze's comment #24 and this fixed things for me.

AMD Ryzen 7 2700X with GeForce RTX 3070
Problematic packages: nvidia-465.27-2 (the probable culprit) and linux-5.11.16

Offline

#55 2021-05-04 14:49:50

cs_95cc64dd
Member
Registered: 2020-10-29
Posts: 3

Re: nvidia driver causes kernel panic

I had the same problem, copy pasta to fix was:

#!/bin/bash

for x in \
  nvidia-460.67-5-x86_64.pkg.tar.zst \
  nvidia-dkms-460.67-1-x86_64.pkg.tar.zst \
  nvidia-settings-460.67-1-x86_64.pkg.tar.zst \
  nvidia-utils-460.67-1-x86_64.pkg.tar.zst \
; do

  test -f $x || \
    wget https://archive.archlinux.org/repos/2021/04/08/extra/os/x86_64/$x
done

for x in \
  linux-5.11.13.arch1-1-x86_64.pkg.tar.zst \
  linux-headers-5.11.13.arch1-1-x86_64.pkg.tar.zst \
; do

  test -f $x || \
    wget https://archive.archlinux.org/repos/2021/04/15/core/os/x86_64/$x
done


pacman -U *.zst

Offline

#56 2021-05-04 17:34:06

ShayBox
Member
Registered: 2021-05-03
Posts: 3

Re: nvidia driver causes kernel panic

Easier command:
downgrade nvidia-dkms nvidia-utils nvidia-settings lib32-nvidia-utils

Last edited by ShayBox (2021-05-04 17:34:34)

Offline

#57 2021-05-06 09:05:05

dummys
Member
Registered: 2015-12-29
Posts: 8

Re: nvidia driver causes kernel panic

now news about this issue ? I don't want to downgrade...

Offline

#58 2021-05-06 18:33:12

Twister915
Member
Registered: 2021-05-06
Posts: 1

Re: nvidia driver causes kernel panic

I've tried to upgrade every few days for the last month, and each time I use latest packages I get a kernel panic loading nvidia.

I only have to downgrade nvidia packages to 460.67-4, and have not downgraded the kernel. I downgrade nvidia, nvidia-dkms, nvidia-utils, and then my system boots. I am on kernel 5.11.16-arch1-1.

The following is the kernel panic on boot with latest nvidia packages (version 465.27-4):

BUG: kernel NULL pointer dereference, address: 000000000000001c
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 0 P4D 0 
Oops: 0000 [#1] PREEMPT SMP NOPTI
CPU: 11 PID: 812 Comm: systemd-udevd Tainted: P           OE     5.11.16-arch1-1 #1
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Pro4, BIOS P3.00 06/17/2020
RIP: 0010:_nv032271rm+0xe/0x80 [nvidia]
Code: 89 d2 e8 45 88 f7 c4 48 83 c4 08 48 83 c5 50 c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 85 ff 74 5f 48 8b 17 48 89 f8 48 8b 0a <39> 71 04 74 53 8b 52 10 48 29 d0 48 8b 10 48 8b 12 39 72 04 74 42
RSP: 0018:ffff97b24389f578 EFLAGS: 00010282
RAX: ffff88fd439e8008 RBX: ffff88fd439e8008 RCX: 0000000000000018
RDX: ffffffffc4742400 RSI: 0000000000497031 RDI: ffff88fd439e8008
RBP: ffff88fd439d5c40 R08: 0000000000000020 R09: ffff88fd439d5c68
R10: ffff88fd058a0008 R11: 0000000010000010 R12: 00000000007ef3cb
R13: 0000000000000000 R14: 00000000000927c0 R15: ffff88fd058a0008
FS:  00007fcff5050a40(0000) GS:ffff890beecc0000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000001c CR3: 0000000106c38000 CR4: 0000000000350ee0
Call Trace:
 ? _nv032275rm+0x15/0x90 [nvidia]
 ? _nv039682rm+0x18/0xc0 [nvidia]
 ? _nv039641rm+0xf1/0x1f0 [nvidia]
 ? _nv018507rm+0xc2/0x180 [nvidia]
 ? _nv018462rm+0x19a/0x750 [nvidia]
 ? _nv032436rm+0x14b/0x200 [nvidia]
 ? _nv032436rm+0xab/0x200 [nvidia]
 ? _nv000859rm+0x2a5/0x470 [nvidia]
 ? _nv009647rm+0x4c3/0x650 [nvidia]
 ? _nv032313rm+0x11f/0x270 [nvidia]
 ? _nv032310rm+0x15d/0x1a0 [nvidia]
 ? _nv015534rm+0x232/0x330 [nvidia]
 ? _nv015556rm+0x7fd/0x1020 [nvidia]
 ? _nv027155rm+0x22c/0x4f0 [nvidia]
 ? _nv017787rm+0x303/0x5e0 [nvidia]
 ? _nv017788rm+0x30/0xa0 [nvidia]
 ? _nv017789rm+0xe1/0x220 [nvidia]
 ? _nv022829rm+0xed/0x220 [nvidia]
 ? _nv023065rm+0x30/0x60 [nvidia]
 ? _nv000704rm+0x16da/0x22b0 [nvidia]
 ? rm_init_adapter+0xc5/0xe0 [nvidia]
 ? kthread_create_on_node+0x51/0x70
 ? nv_open_device+0x122/0x8a0 [nvidia]
 ? nvidia_dev_get+0x63/0xb0 [nvidia]
 ? nvkms_open_gpu+0x4e/0x90 [nvidia_modeset]
 ? _nv000010kms+0x40/0x260 [nvidia_modeset]
 ? printk+0x68/0x7f
 ? security_kernfs_init_security+0x2a/0x40
 ? nv_drm_load+0xac/0x3ae [nvidia_drm]
 ? nv_drm_master_drop+0x60/0x60 [nvidia_drm]
 ? drm_dev_register+0xc8/0x1b0 [drm]
 ? nv_drm_probe_devices+0x184/0x210 [nvidia_drm]
 ? 0xffffffffc0a8e000
 ? do_one_initcall+0x57/0x220
 ? do_init_module+0x5c/0x270
 ? load_module+0x243e/0x2610
 ? __do_sys_init_module+0x136/0x1b0
 ? do_syscall_64+0x33/0x40
 ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
Modules linked in: nvidia_drm(POE+) nvidia_modeset(POE) ucsi_ccg typec_ucsi intel_rapl_msr typec wmi_bmof nvidia(POE) snd_hda_codec_realtek snd_hda_codec_generic iwlmvm ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg m>
 i2c_nvidia_gpu soundcore fb_sys_fops curve25519_x86_64 rfkill dca libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 ip6_udp_tunnel wmi udp_tunnel libcurve25519_generic libchacha libblake2s_generic pinctrl_am>
CR2: 000000000000001c
---[ end trace b5ea4402a89e97ae ]---
RIP: 0010:_nv032271rm+0xe/0x80 [nvidia]
Code: 89 d2 e8 45 88 f7 c4 48 83 c4 08 48 83 c5 50 c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 85 ff 74 5f 48 8b 17 48 89 f8 48 8b 0a <39> 71 04 74 53 8b 52 10 48 29 d0 48 8b 10 48 8b 12 39 72 04 74 42
RSP: 0018:ffff97b24389f578 EFLAGS: 00010282
RAX: ffff88fd439e8008 RBX: ffff88fd439e8008 RCX: 0000000000000018
RDX: ffffffffc4742400 RSI: 0000000000497031 RDI: ffff88fd439e8008
RBP: ffff88fd439d5c40 R08: 0000000000000020 R09: ffff88fd439d5c68
R10: ffff88fd058a0008 R11: 0000000010000010 R12: 00000000007ef3cb
R13: 0000000000000000 R14: 00000000000927c0 R15: ffff88fd058a0008
FS:  00007fcff5050a40(0000) GS:ffff890beecc0000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000001c CR3: 0000000106c38000 CR4: 0000000000350ee0

Any workarounds? How do I keep CUDA working?

Offline

#59 2021-05-06 19:37:57

seth
Member
Registered: 2012-09-03
Posts: 20,462

Re: nvidia driver causes kernel panic

The workaround is to use 460 and there's not going to be a solution until nvidia releases an update for the driver.
CUDA should™ still work, though? It's not bound to the exact driver version.

Offline

#60 2021-05-07 03:09:48

ShayBox
Member
Registered: 2021-05-03
Posts: 3

Re: nvidia driver causes kernel panic

CUDA still works for me on 460

Offline

#61 2021-05-10 20:35:37

Jubijub
Member
From: Lausanne, Switzerland
Registered: 2018-04-04
Posts: 22
Website

Re: nvidia driver causes kernel panic

same issue (1080Ti, with AMD Ryzen 5950X, also with a screen connected via DP (Dell U3419W))

I manage to install the drivers and boot to tty if I don't use the modeset in the bootloader parameters / don't load the nvidia modules in mkinitcpio.conf. In which state a simple nvidia-smi hangs the system.

Offline

#62 2021-05-10 21:35:18

walmartshopper
Member
Registered: 2010-03-31
Posts: 33

Re: nvidia driver causes kernel panic

Also affected here with an RTX 3080. I'm running four 1440p monitors and using all the ports on the GPU, so I can't just switch from DP to HDMI.  However  downgrading to the last 460 release and ignoring all nvidia packages in pacman.conf is still working and the dkms version still builds on the latest kernel.

Offline

#63 2021-05-10 22:29:55

Cavsfan
Member
From: USA
Registered: 2015-07-08
Posts: 93

Re: nvidia driver causes kernel panic

This exact same thing has been happening to me. I noticed my fans were not turning awhile back. Luckily I found this thread.
This as mentioned temporarily fixed the problem:

sudo pacman -U nvidia-460.67-5-x86_64.pkg.tar.zst nvidia-utils-460.67-1-x86_64.pkg.tar.zst nvidia-settings-460.67-1-x86_64.pkg.tar.zst linux-5.11.11.arch1-1-x86_64.pkg.tar.zst linux-headers-5.11.11.arch1-1-x86_64.pkg.tar.zst

I spent a lot of time re-installing nvidia drivers, etc. and nothing worked until I seen ^
I was hoping this thread was not closed as the problem is definitely still there.

So, far other updates have gone smoothly.

Edit: I guess it was more than just the fans for most. The fans were all I lost but, still one needs fans.

Last edited by Cavsfan (2021-05-11 02:54:44)

Offline

Board footer

Powered by FluxBB