Proxmox kernel tainted

A

Asim

New Member
Aug 21, 2022
7
0
1
I have a proxmox installation that works great but somehow my mikrotik/CHR would randomly stop working and when rebooted, would report kernel panic

inspected and found out that the proxmox kernel is tainted (its a fresh install a week ago)

Code: 
root@pm03:~# cat /proc/sys/kernel/tainted
4097

I found a way to know the modules that may be the cause of it and here is the list
Code: 
root@pm03:~# bash find_taint.sh
zfs
zunicode
zzstd
zlua
zavl
icp
zcommon
znvpair
spl

Now the question is, can I blacklist all or some of these modules? I am not using zfs

Output from pveversion -v
Code: 
root@pm03:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.39-4-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-9
pve-kernel-helper: 7.2-9
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.15.39-3-pve: 5.15.39-3
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-8
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.5-1
proxmox-backup-file-restore: 2.2.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-5
pve-firmware: 3.5-1
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.5-pve1
 
Hi,
Asim said:
inspected and found out that the proxmox kernel is tainted (its a fresh install a week ago)

Code: 
root@pm03:~# cat /proc/sys/kernel/tainted
4097
Click to expand...
This is very much expected, the bits for how the kernel is tainted are 0 and 12 (2^0+2^12=4097) and they mean proprietary module was loaded and externally-built (“out-of-tree”) module was loaded (docs). Running a tainted kernel is usually not problematic by itself (also mentioned in the docs).
Asim said:
I found a way to know the modules that may be the cause of it and here is the list
Code: 
root@pm03:~# bash find_taint.sh
zfs
zunicode
zzstd
zlua
zavl
icp
zcommon
znvpair
spl

Now the question is, can I blacklist all or some of these modules? I am not using zfs
Click to expand...
Why do you think that the issue has anything to do with ZFS? Can you post the stack trace of the panic?

Asim said:
Output from pveversion -v
Code: 
root@pm03:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.39-4-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-9
pve-kernel-helper: 7.2-9
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.15.39-3-pve: 5.15.39-3
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-8
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.5-1
proxmox-backup-file-restore: 2.2.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-5
pve-firmware: 3.5-1
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.5-pve1
Click to expand...
 
  • Like
Reactions: janssensm
Asim said:
@fiona The issue is that the tainted kernel causes the CHR/Mikrotik router to loose network connectivity (by displaying kernel panic caused by the underlying hardware issue)
Click to expand...
Why do you think the fact that the kernel is tainted is responsible? What is the underlying hardware issue? Please share the details of the kernel panic.
 
You must log in or register to reply here.
Top Bottom