Opt-in Linux 6.2 Kernel for Proxmox VE 7.x available

Hi,
mowat said:
Any news on possible 6.4 kernel?
Click to expand...
that kernel does not exist yet ;) Linus released the 6.3 kernel ten days ago. We base our kernels on the ones from Ubuntu and I don't think they have 6.3 yet.
 
You can run Ubuntu with the mainline kernel app. It is up to 6.3.1 as of now. I don't need that but maybe others do?

Thanks
 
Last edited:
fiona said:
Hi,

that kernel does not exist yet ;) Linus released the 6.3 kernel ten days ago. We base our kernels on the ones from Ubuntu and I don't think they have 6.3 yet.
Click to expand...
Is there any news about the pve 6.3 kernel?
 
With kernel 6.2 I can no longer see partitions on the front facing nvme drive. The device file is there, but no partitions are visible.
Drive is readable on other machines, and with older kernel.

[root@pegasus ~]# ll /dev/ | grep nvme crw------- 1 root root 240, 0 May 4 20:55 nvme0 brw-rw---- 1 root disk 259, 0 May 4 20:55 nvme0n1 brw-rw---- 1 root disk 259, 1 May 4 20:55 nvme0n1p1 brw-rw---- 1 root disk 259, 2 May 4 20:55 nvme0n1p2 brw-rw---- 1 root disk 259, 3 May 4 20:55 nvme0n1p3 crw------- 1 root root 240, 1 May 4 20:55 nvme1 [root@pegasus ~]# [root@pegasus ~]# zpool status rpool pool: rpool state: DEGRADED status: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the device using 'zpool replace'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J scan: scrub repaired 0B in 00:00:03 with 0 errors on Sun Oct 10 00:24:05 2021 config: NAME STATE READ WRITE CKSUM rpool DEGRADED 0 0 0 mirror-0 DEGRADED 0 0 0 nvme-ADATA_SWORDFISH_2L0329QKNKUC-part3 ONLINE 0 0 0 4737682860907798044 UNAVAIL 0 0 0 was /dev/disk/by-id/nvme-ADATA_SWORDFISH_2L032L2K85JY-part3 errors: No known data errors [root@pegasus ~]#


I have another identical machine with the same problem on 6.2, that is currently booted to the old kernel 5.15.102-1-pve, and the drive is visible again. ZFS has automatically re-silvered the drive as soon as it was detected, and after clearing the errors on the pool is healthy.

[root@galactica ~]# ll /dev/ | grep nvme crw------- 1 root root 241, 0 May 4 20:13 nvme0 brw-rw---- 1 root disk 259, 0 May 4 20:13 nvme0n1 brw-rw---- 1 root disk 259, 2 May 4 20:13 nvme0n1p1 brw-rw---- 1 root disk 259, 3 May 4 20:13 nvme0n1p2 brw-rw---- 1 root disk 259, 4 May 4 20:13 nvme0n1p3 crw------- 1 root root 241, 1 May 4 20:13 nvme1 brw-rw---- 1 root disk 259, 1 May 4 20:13 nvme1n1 brw-rw---- 1 root disk 259, 5 May 4 20:13 nvme1n1p1 brw-rw---- 1 root disk 259, 6 May 4 20:13 nvme1n1p2 brw-rw---- 1 root disk 259, 7 May 4 20:13 nvme1n1p3 [root@galactica ~]# [root@galactica ~]# zpool status rpool pool: rpool state: ONLINE status: Some supported and requested features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: resilvered 980M in 00:00:02 with 0 errors on Thu May 4 20:13:18 2023 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 nvme-ADATA_SWORDFISH_2L032L2997DH-part3 ONLINE 0 0 0 nvme-ADATA_SWORDFISH_2K50292DK9R1-part3 ONLINE 0 0 0 errors: No known data errors [root@galactica ~]#

Proxmox: 7.4-3
Kernel: 6.2.11-1-pve
Motherboard: ASROCK B550 Phantom Gaming-ITX/ax
CPU: AMD Ryzen 7 5700G
 
Deafboy said:
With kernel 6.2 I can no longer see partitions on the front facing nvme drive. The device file is there, but no partitions are visible.
Drive is readable on other machines, and with older kernel.
Click to expand...
Older kernel means here one of the previous 5.19 or 6.1 opt-in or current default 5.15?

Anything in the journal, or rather kernel log, e.g. for a quick check use:
journalctl -k -o short-precise --no-hostname -p warning..emerg -x

To show only kernel messages with level warning or higher and precise time stamps, maybe we can figure out something from an message there. Otherwise it might make sense to check unfiltered journalctl -b (or dmesg) output for any references to nvme or PCI that sound like it could indicate something w.r.t. this issue.
 
This looks like a HW problem that has started to take effect since vanilla 5.19 - https://bugzilla.kernel.org/show_bug.cgi?id=216394
The same issue has been encountered and patched in unraid - https://forums.unraid.net/topic/137442-solvednew-nvme-not-visible-globally-duplicate-ids/

journal from 6.2 vs 5.15:

Code: 
[root@galactica ~]# journalctl -k -o short-precise --no-hostname -p warning..emerg -x
-- Journal begins at Tue 2021-09-28 23:07:12 CEST, ends at Wed 2023-05-10 11:38:25 CEST. --
May 10 11:37:33.405987 kernel:   #9 #10 #11 #12 #13 #14 #15
May 10 11:37:33.415154 kernel: tpm tpm0: AMD fTPM version 0x3003a00000005 causes system stutter; hwrng disabled
May 10 11:37:33.415344 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
May 10 11:37:33.415431 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
May 10 11:37:33.415468 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
May 10 11:37:33.415504 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
May 10 11:37:33.415544 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
May 10 11:37:33.415580 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
May 10 11:37:33.415618 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
May 10 11:37:33.415655 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
May 10 11:37:33.415692 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
May 10 11:37:33.415728 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
May 10 11:37:33.417190 kernel: nvme nvme1: failed to set APST feature (2)
May 10 11:37:33.417235 kernel: nvme nvme0: failed to set APST feature (2)
May 10 11:37:33.417459 kernel: nvme nvme0: globally duplicate IDs for nsid 1
May 10 11:37:33.417503 kernel: nvme nvme0: VID:DID 10ec:5765 model:ADATA SWORDFISH firmware:VC0S0285
May 10 11:37:33.418462 kernel: ata6: failed to resume link (SControl 0)
May 10 11:37:33.423205 kernel: spl: loading out-of-tree module taints kernel.
May 10 11:37:33.423209 kernel: znvpair: module license 'CDDL' taints kernel.
May 10 11:37:33.423214 kernel: Disabling lock debugging due to kernel taint
May 10 11:37:34.721012 kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
May 10 11:37:34.721813 kernel: iwlwifi 0000:05:00.0: api flags index 2 larger than supported by driver
May 10 11:37:34.722619 kernel: thermal thermal_zone0: failed to read out thermal zone (-61)
May 10 11:37:34.722682 kernel: iwlwifi 0000:05:00.0: reporting RF_KILL (radio disabled)
May 10 11:37:34.725357 kernel: amdgpu 0000:07:00.0: amdgpu: PSP runtime database doesn't exist
May 10 11:37:34.725424 kernel: amdgpu 0000:07:00.0: amdgpu: PSP runtime database doesn't exist
May 10 11:37:35.528234 kernel: amdgpu: SRAT table not found
[root@galactica ~]# uname -a
Linux galactica 6.2.11-1-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.11-1 (2023-04-20T09:59Z) x86_64 GNU/Linux
[root@galactica ~]#

Code: 
[root@galactica ~]# journalctl -k -o short-precise --no-hostname -p warning..emerg -x
-- Journal begins at Tue 2021-09-28 23:07:12 CEST, ends at Wed 2023-05-10 11:55:38 CEST. --
May 10 11:55:07.403715 kernel:   #9 #10 #11 #12 #13 #14 #15
May 10 11:55:07.413913 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
May 10 11:55:07.414040 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
May 10 11:55:07.414100 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
May 10 11:55:07.414153 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
May 10 11:55:07.414203 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
May 10 11:55:07.414261 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
May 10 11:55:07.414325 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
May 10 11:55:07.414372 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
May 10 11:55:07.414440 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
May 10 11:55:07.414512 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
May 10 11:55:07.420368 kernel: nvme nvme1: failed to set APST feature (2)
May 10 11:55:07.420424 kernel: nvme nvme0: failed to set APST feature (2)
May 10 11:55:07.420832 kernel: ata1.00: ATA Identify Device Log not supported
May 10 11:55:07.420843 kernel: ata1.00: ATA Identify Device Log not supported
May 10 11:55:07.422572 kernel: ata2.00: ATA Identify Device Log not supported
May 10 11:55:07.422581 kernel: ata2.00: ATA Identify Device Log not supported
May 10 11:55:07.423439 kernel: ata6: failed to resume link (SControl 0)
May 10 11:55:07.424013 kernel: spl: loading out-of-tree module taints kernel.
May 10 11:55:07.424017 kernel: znvpair: module license 'CDDL' taints kernel.
May 10 11:55:07.424022 kernel: Disabling lock debugging due to kernel taint
May 10 11:55:07.602945 kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
May 10 11:55:07.603642 kernel: iwlwifi 0000:05:00.0: api flags index 2 larger than supported by driver
May 10 11:55:07.618292 kernel: iwlwifi 0000:05:00.0: reporting RF_KILL (radio disabled)
May 10 11:55:07.618399 kernel: thermal thermal_zone0: failed to read out thermal zone (-61)
May 10 11:55:07.626773 kernel: amdgpu 0000:07:00.0: amdgpu: PSP runtime database doesn't exist
May 10 11:55:08.498318 kernel: amdgpu: SRAT table not found
[root@galactica ~]# uname -a
Linux galactica 5.15.107-1-pve #1 SMP PVE 5.15.107-1 (2023-04-20T10:05Z) x86_64 GNU/Linux
[root@galactica ~]#
 
Last edited:
I've had issues installing Proxmox using the official ISO due to drivers for my iGPU not yet being present in the currently used kernel and X11 failing to start. (CPU is a Ryzen 7950X3D with integrated graphics)
Is there any way to get an installation ISO with this kernel version, or is there an ETA when it will be released?
 
nett_hier said:
I've had issues installing Proxmox using the official ISO due to drivers for my iGPU not yet being present in the currently used kernel and X11 failing to start. (CPU is a Ryzen 7950X3D with integrated graphics)
Is there any way to get an installation ISO with this kernel version, or is there an ETA when it will be released?
Click to expand...
Maybe you could install debian and then install proxmox on top of that? That might not work either tho. If it does there are instructions for that out there.
Good luck
 
That is exactly what I did for now, but I'd prefer to use the official ISO so I have a more standard installation.
 
Deafboy said:
This looks like a HW problem that has started to take effect since vanilla 5.19 - https://bugzilla.kernel.org/show_bug.cgi?id=216394
The same issue has been encountered and patched in unraid - https://forums.unraid.net/topic/137442-solvednew-nvme-not-visible-globally-duplicate-ids/

journal from 6.2 vs 5.15:

Code: 
[root@galactica ~]# journalctl -k -o short-precise --no-hostname -p warning..emerg -x
-- Journal begins at Tue 2021-09-28 23:07:12 CEST, ends at Wed 2023-05-10 11:38:25 CEST. --
May 10 11:37:33.405987 kernel:   #9 #10 #11 #12 #13 #14 #15
May 10 11:37:33.415154 kernel: tpm tpm0: AMD fTPM version 0x3003a00000005 causes system stutter; hwrng disabled
May 10 11:37:33.415344 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
May 10 11:37:33.415431 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
May 10 11:37:33.415468 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
May 10 11:37:33.415504 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
May 10 11:37:33.415544 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
May 10 11:37:33.415580 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
May 10 11:37:33.415618 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
May 10 11:37:33.415655 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
May 10 11:37:33.415692 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
May 10 11:37:33.415728 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
May 10 11:37:33.417190 kernel: nvme nvme1: failed to set APST feature (2)
May 10 11:37:33.417235 kernel: nvme nvme0: failed to set APST feature (2)
May 10 11:37:33.417459 kernel: nvme nvme0: globally duplicate IDs for nsid 1
May 10 11:37:33.417503 kernel: nvme nvme0: VID:DID 10ec:5765 model:ADATA SWORDFISH firmware:VC0S0285
May 10 11:37:33.418462 kernel: ata6: failed to resume link (SControl 0)
May 10 11:37:33.423205 kernel: spl: loading out-of-tree module taints kernel.
May 10 11:37:33.423209 kernel: znvpair: module license 'CDDL' taints kernel.
May 10 11:37:33.423214 kernel: Disabling lock debugging due to kernel taint
May 10 11:37:34.721012 kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
May 10 11:37:34.721813 kernel: iwlwifi 0000:05:00.0: api flags index 2 larger than supported by driver
May 10 11:37:34.722619 kernel: thermal thermal_zone0: failed to read out thermal zone (-61)
May 10 11:37:34.722682 kernel: iwlwifi 0000:05:00.0: reporting RF_KILL (radio disabled)
May 10 11:37:34.725357 kernel: amdgpu 0000:07:00.0: amdgpu: PSP runtime database doesn't exist
May 10 11:37:34.725424 kernel: amdgpu 0000:07:00.0: amdgpu: PSP runtime database doesn't exist
May 10 11:37:35.528234 kernel: amdgpu: SRAT table not found
[root@galactica ~]# uname -a
Linux galactica 6.2.11-1-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.11-1 (2023-04-20T09:59Z) x86_64 GNU/Linux
[root@galactica ~]#

Code: 
[root@galactica ~]# journalctl -k -o short-precise --no-hostname -p warning..emerg -x
-- Journal begins at Tue 2021-09-28 23:07:12 CEST, ends at Wed 2023-05-10 11:55:38 CEST. --
May 10 11:55:07.403715 kernel:   #9 #10 #11 #12 #13 #14 #15
May 10 11:55:07.413913 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
May 10 11:55:07.414040 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
May 10 11:55:07.414100 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
May 10 11:55:07.414153 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
May 10 11:55:07.414203 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
May 10 11:55:07.414261 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
May 10 11:55:07.414325 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
May 10 11:55:07.414372 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
May 10 11:55:07.414440 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
May 10 11:55:07.414512 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
May 10 11:55:07.420368 kernel: nvme nvme1: failed to set APST feature (2)
May 10 11:55:07.420424 kernel: nvme nvme0: failed to set APST feature (2)
May 10 11:55:07.420832 kernel: ata1.00: ATA Identify Device Log not supported
May 10 11:55:07.420843 kernel: ata1.00: ATA Identify Device Log not supported
May 10 11:55:07.422572 kernel: ata2.00: ATA Identify Device Log not supported
May 10 11:55:07.422581 kernel: ata2.00: ATA Identify Device Log not supported
May 10 11:55:07.423439 kernel: ata6: failed to resume link (SControl 0)
May 10 11:55:07.424013 kernel: spl: loading out-of-tree module taints kernel.
May 10 11:55:07.424017 kernel: znvpair: module license 'CDDL' taints kernel.
May 10 11:55:07.424022 kernel: Disabling lock debugging due to kernel taint
May 10 11:55:07.602945 kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
May 10 11:55:07.603642 kernel: iwlwifi 0000:05:00.0: api flags index 2 larger than supported by driver
May 10 11:55:07.618292 kernel: iwlwifi 0000:05:00.0: reporting RF_KILL (radio disabled)
May 10 11:55:07.618399 kernel: thermal thermal_zone0: failed to read out thermal zone (-61)
May 10 11:55:07.626773 kernel: amdgpu 0000:07:00.0: amdgpu: PSP runtime database doesn't exist
May 10 11:55:08.498318 kernel: amdgpu: SRAT table not found
[root@galactica ~]# uname -a
Linux galactica 5.15.107-1-pve #1 SMP PVE 5.15.107-1 (2023-04-20T10:05Z) x86_64 GNU/Linux
[root@galactica ~]#
Click to expand...
I'm running 'Linux 6.2.9-1-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.9-1 (2023-03-31T10:48Z)' and have been having issues with my HBA recognising sata ports five to ten. So started using 6.2 but still no luck thusfar. I read that my new ASM1062+JMB585 based BHA required kernel 6.x for the kernel driver.

Code: 
root@nas:~# journalctl -k -o short-precise --no-hostname -p warning..emerg -x
-- Journal begins at Wed 2023-05-03 17:47:58 BST, ends at Mon 2023-05-15 08:43:57 BST. --
May 13 16:24:19.012056 kernel:   #9 #10 #11 #12 #13 #14 #15
May 13 16:24:19.023403 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
May 13 16:24:19.023445 kernel: pci 0000:00:00.2: PCI INT A: not connected
May 13 16:24:19.024142 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
May 13 16:24:19.024229 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
May 13 16:24:19.024269 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
May 13 16:24:19.024306 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
May 13 16:24:19.024343 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
May 13 16:24:19.024379 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
May 13 16:24:19.024415 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
May 13 16:24:19.024452 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
May 13 16:24:19.024488 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
May 13 16:24:19.024526 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
May 13 16:24:19.024937 kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\GSA1.SMBI) (20221020/utaddress-204)
May 13 16:24:19.025163 kernel: ACPI Warning: SystemIO range 0x0000000000000B20-0x0000000000000B28 conflicts with OpRegion 0x0000000000000B20-0x0000000000000B3F (\GSA1.SMG0) (20221020/utaddress-204)
May 13 16:24:19.028722 kernel: ata7: failed to resume link (SControl 0)
May 13 16:24:19.136880 kernel: spl: loading out-of-tree module taints kernel.
May 13 16:24:19.136905 kernel: znvpair: module license 'CDDL' taints kernel.
May 13 16:24:19.137145 kernel: Disabling lock debugging due to kernel taint
May 13 16:24:19.138265 kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
May 13 16:24:19.505246 kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
May 13 16:24:20.262337 kernel: amdgpu 0000:07:00.0: amdgpu: PSP runtime database doesn't exist
May 13 16:24:20.262419 kernel: amdgpu 0000:07:00.0: amdgpu: PSP runtime database doesn't exist
May 13 16:24:21.101247 kernel: amdgpu: SRAT table not found
May 13 16:24:38.789514 kernel: kauditd_printk_skb: 9 callbacks suppressed
May 13 19:00:58.429205 kernel: smbd(6424): Attempt to set a LOCK_MAND lock via flock(2). This support has been removed and the request ignored.
 
I'm seeing some kernel crashes with igc (intel nic driver) on the current kernel. How often is a new kernel version released?

If this kernel is based off ubuntu; where can I check what version ubuntu is on?

my latest crash
Code: 
https://pastebin.com/X1X3gbwf
 
Deafboy said:
This looks like a HW problem that has started to take effect since vanilla 5.19 - https://bugzilla.kernel.org/show_bug.cgi?id=216394
The same issue has been encountered and patched in unraid - https://forums.unraid.net/topic/137442-solvednew-nvme-not-visible-globally-duplicate-ids/

journal from 6.2 vs 5.15:

Code: 
[root@galactica ~]# journalctl -k -o short-precise --no-hostname -p warning..emerg -x
-- Journal begins at Tue 2021-09-28 23:07:12 CEST, ends at Wed 2023-05-10 11:38:25 CEST. --
May 10 11:37:33.405987 kernel:   #9 #10 #11 #12 #13 #14 #15
May 10 11:37:33.415154 kernel: tpm tpm0: AMD fTPM version 0x3003a00000005 causes system stutter; hwrng disabled
May 10 11:37:33.415344 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
May 10 11:37:33.415431 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
May 10 11:37:33.415468 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
May 10 11:37:33.415504 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
May 10 11:37:33.415544 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
May 10 11:37:33.415580 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
May 10 11:37:33.415618 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
May 10 11:37:33.415655 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
May 10 11:37:33.415692 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
May 10 11:37:33.415728 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
May 10 11:37:33.417190 kernel: nvme nvme1: failed to set APST feature (2)
May 10 11:37:33.417235 kernel: nvme nvme0: failed to set APST feature (2)
May 10 11:37:33.417459 kernel: nvme nvme0: globally duplicate IDs for nsid 1
May 10 11:37:33.417503 kernel: nvme nvme0: VID:DID 10ec:5765 model:ADATA SWORDFISH firmware:VC0S0285
May 10 11:37:33.418462 kernel: ata6: failed to resume link (SControl 0)
May 10 11:37:33.423205 kernel: spl: loading out-of-tree module taints kernel.
May 10 11:37:33.423209 kernel: znvpair: module license 'CDDL' taints kernel.
May 10 11:37:33.423214 kernel: Disabling lock debugging due to kernel taint
May 10 11:37:34.721012 kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
May 10 11:37:34.721813 kernel: iwlwifi 0000:05:00.0: api flags index 2 larger than supported by driver
May 10 11:37:34.722619 kernel: thermal thermal_zone0: failed to read out thermal zone (-61)
May 10 11:37:34.722682 kernel: iwlwifi 0000:05:00.0: reporting RF_KILL (radio disabled)
May 10 11:37:34.725357 kernel: amdgpu 0000:07:00.0: amdgpu: PSP runtime database doesn't exist
May 10 11:37:34.725424 kernel: amdgpu 0000:07:00.0: amdgpu: PSP runtime database doesn't exist
May 10 11:37:35.528234 kernel: amdgpu: SRAT table not found
[root@galactica ~]# uname -a
Linux galactica 6.2.11-1-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.11-1 (2023-04-20T09:59Z) x86_64 GNU/Linux
[root@galactica ~]#

Code: 
[root@galactica ~]# journalctl -k -o short-precise --no-hostname -p warning..emerg -x
-- Journal begins at Tue 2021-09-28 23:07:12 CEST, ends at Wed 2023-05-10 11:55:38 CEST. --
May 10 11:55:07.403715 kernel:   #9 #10 #11 #12 #13 #14 #15
May 10 11:55:07.413913 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
May 10 11:55:07.414040 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
May 10 11:55:07.414100 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
May 10 11:55:07.414153 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
May 10 11:55:07.414203 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
May 10 11:55:07.414261 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
May 10 11:55:07.414325 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
May 10 11:55:07.414372 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
May 10 11:55:07.414440 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
May 10 11:55:07.414512 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
May 10 11:55:07.420368 kernel: nvme nvme1: failed to set APST feature (2)
May 10 11:55:07.420424 kernel: nvme nvme0: failed to set APST feature (2)
May 10 11:55:07.420832 kernel: ata1.00: ATA Identify Device Log not supported
May 10 11:55:07.420843 kernel: ata1.00: ATA Identify Device Log not supported
May 10 11:55:07.422572 kernel: ata2.00: ATA Identify Device Log not supported
May 10 11:55:07.422581 kernel: ata2.00: ATA Identify Device Log not supported
May 10 11:55:07.423439 kernel: ata6: failed to resume link (SControl 0)
May 10 11:55:07.424013 kernel: spl: loading out-of-tree module taints kernel.
May 10 11:55:07.424017 kernel: znvpair: module license 'CDDL' taints kernel.
May 10 11:55:07.424022 kernel: Disabling lock debugging due to kernel taint
May 10 11:55:07.602945 kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
May 10 11:55:07.603642 kernel: iwlwifi 0000:05:00.0: api flags index 2 larger than supported by driver
May 10 11:55:07.618292 kernel: iwlwifi 0000:05:00.0: reporting RF_KILL (radio disabled)
May 10 11:55:07.618399 kernel: thermal thermal_zone0: failed to read out thermal zone (-61)
May 10 11:55:07.626773 kernel: amdgpu 0000:07:00.0: amdgpu: PSP runtime database doesn't exist
May 10 11:55:08.498318 kernel: amdgpu: SRAT table not found
[root@galactica ~]# uname -a
Linux galactica 5.15.107-1-pve #1 SMP PVE 5.15.107-1 (2023-04-20T10:05Z) x86_64 GNU/Linux
[root@galactica ~]#
Click to expand...
I think I ran into a related issue with my two NVMe drives back with the 6.1 opt-in kernel, see my post here. You could try and compare the device links in /dev/disk/by-id/ (i.e. not only in /dev/ !) between 5.15 and 6.2, because at least for me they have changed since 5.19 (i.e. due to the bug you refer to?). If you can identify any changing identifiers, you may have to re-import the pool(s) with explicitly providing the changed device identifiers. For the root pool, this requires booting from a live system, unfortunately.

Regards
 
PCI passthrough of some USB controllers got broken after 6.2.6.

I'm passing through two of my motherboard's USB Extensible Host Controller (same IOMMU group) to a Win 11 VM and I noticed one of them failed to initialize on Windows after a kernel update.

I tried a fresh Win installation to rule out any Window config issue. Same problem.
I tried an Ubuntu VM where it also used to work. Same problem.

It's broken on 6.2.9-1, 6.2.11-1 and 6.2.11-2.
It works correctly on 6.2.6-1 and 5.19.17-2.

So this seems to be related to any change between kernel version > 6.2.6 <= 6.2.9
 
Hi guys,

Any improvement on power save about 12th Intel gen? I’m still on 6.1.0 (with PVE 7.4) and at idling I’ve 4 E-Core stuck at 3.7Ghz in my i5 12700k

Thanks
 
Partok said:
Is there an ISO available that includes the 6.2 kernel?

I've been trying to install Proxmox with ZFS using the qemu method on my new AX52 server from Hetzner, but although the installation process appears to work, I can't log in to my server.
At first, I thought I had a network configuration issue, but after ordering a KVM, I realized that I was experiencing a boot issue that redirected me to the BIOS.
The server's processor is an AMD Ryzen 7 7700, and I suspect that the 5.15 kernel is not supported and that I need a kernel version of 5.18 or higher.
Click to expand...

Happened to me also. I think problem is qemu installs proxmox in BIOS mode while new hetzner machines require UEFI.
I had to order KVM.
 
nett_hier said:
I've had issues installing Proxmox using the official ISO due to drivers for my iGPU not yet being present in the currently used kernel and X11 failing to start. (CPU is a Ryzen 7950X3D with integrated graphics)
Is there any way to get an installation ISO with this kernel version, or is there an ETA when it will be released?
Click to expand...

I ran in to this a while back.
Here was what I did to get around it:
https://forum.proxmox.com/threads/p...-install-on-amd-processor.116549/#post-514145

Pretty much muck around in the console after proxmox fails to start X and then add the bits and restart the process
 
Looks like the latest 6.2 kernel still has some major performance issues in our enviroment just like 6.1.

We are seeing a load increase of 30-50% on pretty much all VM's running on hosts with the 6.2.x kernel

If we go back to 5.15.x all is well.

Check out the screen shot, our load has essentially doubled on the 6.1 or 6.2 kernels.

1685714265315.png
 
Last edited:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom