I’ve been away from my PC for a week or so, and of course coming back and running the updated command I find 400+ Mb of updates. The latest kernel is 5.5.5-200 and after login I’m getting the following errors reported:
A kernel problem occurred, but your kernel has been tainted (flags:POE). Explanation:
P - Proprietary module has been loaded.
O - Out-of-tree module has been loaded.
E - Unsigned module has been loaded.
Kernel maintainers are unable to diagnose tainted reports. Tainted modules: nvidia_drm,nvidia_modeset,nvidia_uvm,nvidia.
Anything special happened during the last week or particularly with this kernel update?
I’m using Fedora 31, Gnome shell.
dmesg | grep -i taint might reveal the reason
Maybe you rather need to blacklist the offending modules to “un-taint” the Kernel, and then make a bug report.
Here is the response…
[xxx@wasteland ~]$ dmesg | grep -i taint
[ 6.864489] nvidia: loading out-of-tree module taints kernel.
[ 6.864495] nvidia: module license 'NVIDIA' taints kernel.
[ 6.864496] Disabling lock debugging due to kernel taint
[ 6.892318] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[ 8.202928] CPU: 0 PID: 462 Comm: plymouthd Tainted: P OE 5.5.5-200.fc31.x86_64 #1
I’m not sure why you’re seeing this recently. The message means the proprietary kernel module is being used, but since it isn’t signed, this taints the kernel. That’s not an inherently bad thing, it’s just an info message that this isn’t a signed module. I’ve asked a few more technical questions on the kernel list about this here.
I’ve had the propriety Nvidia drivers till about ~6 months ago or longer, but since the I’ve installed the ones recommended by fedora:
I thought I got rid of the old proprietary driver… (to be honest I don’t remember how I uninstalled it )
P.S. Thanks for asking about this on the kernel list.
Hello! I have the same problem atm. Kernel upgrade to 5.5.5 leads to the same crash. I have optimus laptop and need Nvidia drivers for work. It is installed from Fusion repo. Worked before 5.5.5 and it’s not fixed with recent 5.5.6.
[ 7.503213] CPU: 1 PID: 414 Comm: plymouthd Tainted: P OE 5.5.6-201.fc31.x86_64 #1
[ 7.503218] Hardware name: Micro-Star International Co., Ltd. PS42 Modern 8RC/MS-14B2, BIOS E14B2IMS.106 12/06/2018
[ 7.503230] RIP: 0010:refcount_warn_saturate+0xa6/0xf0
[ 7.503239] Code: 05 fe 09 2e 01 01 e8 bb 92 bc ff 0f 0b c3 80 3d ec 09 2e 01 00 75 95 48 c7 c7 08 95 3c bb c6 05 dc 09 2e 01 01 e8 9c 92 bc ff <0f> 0b c3 80 3d cb 09 2e 01 00 0f 85 72 ff ff ff 48 c7 c7 60 95 3c
[ 7.503244] RSP: 0018:ffffb290407cbcb8 EFLAGS: 00010286
[ 7.503250] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000007
[ 7.503254] RDX: 0000000000000007 RSI: 0000000000000086 RDI: ffff97732ec59cc0
[ 7.503258] RBP: ffff9773150874e8 R08: 0000000000000382 R09: 0000000000000003
[ 7.503262] R10: 0000000000000000 R11: 0000000000000001 R12: ffff9773257282e8
[ 7.503265] R13: ffff977325728000 R14: 0000000000000000 R15: ffff977325750a00
[ 7.503272] FS: 00007fe4f52e9f00(0000) GS:ffff97732ec40000(0000) knlGS:0000000000000000
[ 7.503276] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 7.503280] CR2: 00007f7ed9315a30 CR3: 0000000464a1e001 CR4: 00000000003606e0
[ 7.503284] Call Trace:
[ 7.503313] nv_drm_atomic_helper_disable_all+0xec/0x290 [nvidia_drm]
[ 7.503333] nv_drm_master_drop+0x22/0x60 [nvidia_drm]
[ 7.503396] drm_drop_master+0x1e/0x30 [drm]
[ 7.503452] drm_dropmaster_ioctl+0x4c/0x90 [drm]
[ 7.503506] ? drm_setmaster_ioctl+0xb0/0xb0 [drm]
[ 7.503565] drm_ioctl_kernel+0xaa/0xf0 [drm]
[ 7.503631] drm_ioctl+0x208/0x390 [drm]
[ 7.503686] ? drm_setmaster_ioctl+0xb0/0xb0 [drm]
[ 7.503701] ? do_filp_open+0xa5/0x100
[ 7.503718] do_vfs_ioctl+0x461/0x6d0
[ 7.503743] ksys_ioctl+0x5e/0x90
[ 7.503756] __x64_sys_ioctl+0x16/0x20
[ 7.503769] do_syscall_64+0x5b/0x1c0
[ 7.503785] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 7.503794] RIP: 0033:0x7fe4f55a738b
[ 7.503802] Code: 0f 1e fa 48 8b 05 fd 9a 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d cd 9a 0c 00 f7 d8 64 89 01 48
[ 7.503806] RSP: 002b:00007ffc4d2ede78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 7.503813] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe4f55a738b
[ 7.503817] RDX: 0000000000000000 RSI: 000000000000641f RDI: 000000000000000b
[ 7.503821] RBP: 000000000000641f R08: 0000555981b9bd50 R09: 00007fe4f56ba380
[ 7.503824] R10: 0000000000000000 R11: 0000000000000246 R12: 0000555981b9bd80
[ 7.503828] R13: 000000000000000b R14: 0000000000000000 R15: 0000000000000000
[ 7.503839] —[ end trace fe605e9abea0643f ]—
We can’t report bugs when a kernel is tainted so let’s hope Nvidia guys could fix it in the future.
The good news that this crash is happening only once during initial boot. Everything is working fine after the initial boot.
As for tainted condition it’s not an error in our case, you could find a good explanation here https://unix.stackexchange.com/questions/118116/what-is-a-tainted-kernel-in-linux
This very crash is related to plymouthd
~/# dnf list installed akmod-nvidia
akmod-nvidia.x86_64 3:440.59-1.fc31 @rpmfusion-nonfree-updates
I feel this thread is related
And we got crash in nv_drm_atomic_helper_disable_all function during plymouth init.
Is there any update on this? I have the exact same problem. Just installed the nvidia drivers via rpm fusion and get this now everytime after I logged in.
You are posting to a thread that was closed ~9 months ago. Please open a new thread, and read the “Start Here” topic for what is suggested to assist us to guide you.