Opt-in Linux 6.17 Kernel for Proxmox VE 9 available on test & no-subscription

ExplodingLemur said:
Oh! OH!!!! Okay, I found something! Adding this kernel command line boot parameter FIXES IT:
Code: 
xe.vram_bar_size=-1
Click to expand...
To tidy up your Kernel command line, you can tweak / create /etc/modprobe.d/xe.conf by adding:
Code: 
options xe vram_bar_size=-1
After that, run update-initramfs -uk all to ensure your initramfs are fresh. Once that’s done, you can remove it from your kernel command.
Now you’re all set!
 
Hi all,

yesterday i migrated my proxmox environment to a new server

HP Elite Mini 600 G9 with 32GB DDR5, 2x 1TB NVMe drives and I5 13500 CPU.

Installed the 9.1 from usb stick, without any problems. Migrated all my VMs to the new server without any problems.

After some hours where i saw, that everything works fine i decided to purchase the subscription.

And well, after updating with the new updates from official repository and updating it to 9.1.5 and 6.17.4-2 kernel my new server hung up. Hardlocks from CPU messages, not booting to gui.

I hat to pin the 6.17.2-1 kernel which works nice. So this kernel made for me everything worse.
 
indigosi said:
Hi all,

yesterday i migrated my proxmox environment to a new server

HP Elite Mini 600 G9 with 32GB DDR5, 2x 1TB NVMe drives and I5 13500 CPU.

Installed the 9.1 from usb stick, without any problems. Migrated all my VMs to the new server without any problems.

After some hours where i saw, that everything works fine i decided to purchase the subscription.

And well, after updating with the new updates from official repository and updating it to 9.1.5 and 6.17.4-2 kernel my new server hung up. Hardlocks from CPU messages, not booting to gui.

I hat to pin the 6.17.2-1 kernel which works nice. So this kernel made for me everything worse.
Click to expand...
please try newer 6.17 kernels!
 
I still have issues with SATA Links since the upgrade do 6.17.
I already replaced SATA cables and tried different disks. Same issue.
Could this be a kernel issue?
https://bugzilla.kernel.org/show_bug.cgi?id=220693


Code: 
[ 4744.506222] ata1.00: exception Emask 0x0 SAct 0x50800000 SErr 0x50000 action 0x6 frozen
[ 4744.506228] ata1: SError: { PHYRdyChg CommWake }
[ 4744.506231] ata1.00: failed command: WRITE FPDMA QUEUED
[ 4744.506231] ata1.00: cmd 61/08:b8:10:a8:3a/00:00:5a:03:00/40 tag 23 ncq dma 4096 out
                        res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 4744.506234] ata1.00: status: { DRDY }
[ 4744.506235] ata1.00: failed command: READ FPDMA QUEUED
[ 4744.506236] ata1.00: cmd 60/08:e0:b0:a0:eb/00:00:48:03:00/40 tag 28 ncq dma 4096 in
                        res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 4744.506238] ata1.00: status: { DRDY }
[ 4744.506238] ata1.00: failed command: WRITE FPDMA QUEUED
[ 4744.506239] ata1.00: cmd 61/08:f0:00:a8:3a/00:00:5a:03:00/40 tag 30 ncq dma 4096 out
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 4744.506240] ata1.00: status: { DRDY }
[ 4744.506242] ata1: hard resetting link
[ 4744.968220] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 4745.104031] ata1.00: configured for UDMA/133
[ 4745.104179] sd 0:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=37s
[ 4745.104182] sd 0:0:0:0: [sda] tag#23 Sense Key : Aborted Command [current]
[ 4745.104183] sd 0:0:0:0: [sda] tag#23 Add. Sense: No additional sense information
[ 4745.104185] sd 0:0:0:0: [sda] tag#23 CDB: Write(16) 8a 00 00 00 00 03 5a 3a a8 10 00 00 00 08 00 00
[ 4745.104186] I/O error, dev sda, sector 14398695440 op 0x1:(WRITE) flags 0x100 phys_seg 1 prio class 2
[ 4745.104188] zio pool=local-zfs-hdd vdev=/dev/disk/by-id/ata-WDC_WD100EFGX-68CPLN0_WD-BC0DDUJJ-part1 error=5 type=2 offset=7372131016704 size=4096 flags=3162240
[ 4745.104206] sd 0:0:0:0: [sda] tag#28 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=30s
[ 4745.104206] sd 0:0:0:0: [sda] tag#28 Sense Key : Aborted Command [current]
[ 4745.104207] sd 0:0:0:0: [sda] tag#28 Add. Sense: No additional sense information
[ 4745.104208] sd 0:0:0:0: [sda] tag#28 CDB: Read(16) 88 00 00 00 00 03 48 eb a0 b0 00 00 00 08 00 00
[ 4745.104208] I/O error, dev sda, sector 14108303536 op 0x0:(READ) flags 0x100 phys_seg 1 prio class 2
[ 4745.104210] zio pool=local-zfs-hdd vdev=/dev/disk/by-id/ata-WDC_WD100EFGX-68CPLN0_WD-BC0DDUJJ-part1 error=5 type=1 offset=7223450361856 size=4096 flags=3145856
[ 4745.104214] sd 0:0:0:0: [sda] tag#30 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=37s
[ 4745.104214] sd 0:0:0:0: [sda] tag#30 Sense Key : Aborted Command [current]
[ 4745.104215] sd 0:0:0:0: [sda] tag#30 Add. Sense: No additional sense information
[ 4745.104216] sd 0:0:0:0: [sda] tag#30 CDB: Write(16) 8a 00 00 00 00 03 5a 3a a8 00 00 00 00 08 00 00
[ 4745.104216] I/O error, dev sda, sector 14398695424 op 0x1:(WRITE) flags 0x100 phys_seg 1 prio class 2
[ 4745.104217] zio pool=local-zfs-hdd vdev=/dev/disk/by-id/ata-WDC_WD100EFGX-68CPLN0_WD-BC0DDUJJ-part1 error=5 type=2 offset=7372131008512 size=4096 flags=3162240
[ 4745.104220] ata1: EH complete
[ 6849.280152] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 6849.414758] ata1.00: configured for UDMA/133
 
6.17 kernel breaks USB 2 ports on Intel S1200BTL motherboard.

6.17
[ 0.000000] DMI: Intel Corporation S1200BTL/S1200BTL, BIOS S1200BT.86B.02.01.0044.072520181346 07/25/2018
[ 1.359727] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 1.360032] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 1.361121] ehci-pci 0000:00:1a.0: debug port 2
[ 1.365372] ehci-pci 0000:00:1a.0: irq 22, io mem 0xc2460000
[ 1.372587] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 1.375542] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 1.375853] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 1.376218] ehci-pci 0000:00:1d.0: debug port 2
[ 1.393868] ehci-pci 0000:00:1d.0: can't setup: -110
[ 1.394202] ehci-pci 0000:00:1d.0: USB bus 2 deregistered
[ 1.394672] ehci-pci 0000:00:1d.0: init 0000:00:1d.0 fail, -110
[ 1.394983] ehci-pci 0000:00:1d.0: probe with driver ehci-pci failed with error -110
[ 1.615623] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 2.024600] usb 1-1.1: new full-speed USB device number 3 using ehci-pci

6.14
[ 1.345590] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 1.345866] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 1
[ 1.346133] ehci-pci 0000:00:1d.0: debug port 2
[ 1.351053] ehci-pci 0000:00:1d.0: irq 20, io mem 0xc2450000
[ 1.358655] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 1.365318] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 1.366025] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 2
[ 1.366487] ehci-pci 0000:00:1a.0: debug port 2
[ 1.370988] ehci-pci 0000:00:1a.0: irq 22, io mem 0xc2460000
[ 1.376629] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 1.603619] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 1.618645] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 2.108721] usb 2-1.1: new full-speed USB device number 3 using ehci-pci
[ 2.108938] usb 1-1.2: new full-speed USB device number 3 using ehci-pci
[ 2.345723] usb 1-1.3: new full-speed USB device number 4 using ehci-pci
[ 2.728641] usb 1-1.3.3: new full-speed USB device number 5 using ehci-pci
 
  • Like
Reactions: Fantomas
For anyone who had issues with your dell boss card once proxmox went to 6.17 kernels, I have something for you to try. Found this bugzilla for the kernel where they were talking about issues with the boss card (posted above by beposec)
.

https://bugzilla.kernel.org/show_bug.cgi?id=220693

After some trial and error, I was able to get my system booting fine with a udev rule.

# cat /etc/udev/rules.d/99-dellboss-max-sectors.rules
# Generic fix for Kernel 6.17+ lockups on Dell BOSS cards (Marvell 88SE9230)
# Matches any model starting with "DELLBOSS" to handle spaces or underscores
ACTION=="add|change", SUBSYSTEM=="block", ENV{ID_MODEL}=="DELLBOSS*", ATTR{queue/max_sectors_kb}="1024"



after making the udev rule, then regenerating the initramfs

update-initramfs -u -k 6.17.13-2-pve

The system can boot into the 6.17 kernel fine. It should continue to work with new kernel releases too since the rule is already in place at kernel package install time when it initially generates the initram.
 
Last edited:
  • Like
Reactions: ghandalf
t.lamprecht said:
Yeah, NIVIDIA did not yet manage to release a driver that's compatible with newer kernel yet.

For now, I added a known issue entry in the initial post here:
Click to expand...

The patch here published: https://www.reddit.com/r/Proxmox/s/cYmX4PKxgX (The patch code is duplicated, take only the first half)
makes version R535 v16.12 compatible with kernel 6.17 (I personally tested it and it works).

Then versions 16.13 and 16.14 were also released (16.14 a few weeks ago). I don't know if these versions are already compatible without a patch or if they also need to be patched.
EDIT: I was able to personally test version 6.14 and can say that it compiles and runs under the 6.17 kernel without needing the patch.
I haven't tried version 6.13, but since 6.14 is available, why use it?

And as for the more recent versions I know that for the R580 (v19.x) there is compatibility with the 6.17 kernel, at least in the more recent versions (as some comments in this thread have confirmed)
 
Last edited:
  • Like
Reactions: matt69
whataboutpereira said:
6.17 kernel breaks USB 2 ports on Intel S1200BTL motherboard.

6.17
[ 0.000000] DMI: Intel Corporation S1200BTL/S1200BTL, BIOS S1200BT.86B.02.01.0044.072520181346 07/25/2018
[ 1.359727] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 1.360032] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 1.361121] ehci-pci 0000:00:1a.0: debug port 2
[ 1.365372] ehci-pci 0000:00:1a.0: irq 22, io mem 0xc2460000
[ 1.372587] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 1.375542] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 1.375853] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 1.376218] ehci-pci 0000:00:1d.0: debug port 2
[ 1.393868] ehci-pci 0000:00:1d.0: can't setup: -110
[ 1.394202] ehci-pci 0000:00:1d.0: USB bus 2 deregistered
[ 1.394672] ehci-pci 0000:00:1d.0: init 0000:00:1d.0 fail, -110
[ 1.394983] ehci-pci 0000:00:1d.0: probe with driver ehci-pci failed with error -110
[ 1.615623] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 2.024600] usb 1-1.1: new full-speed USB device number 3 using ehci-pci

6.14
[ 1.345590] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 1.345866] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 1
[ 1.346133] ehci-pci 0000:00:1d.0: debug port 2
[ 1.351053] ehci-pci 0000:00:1d.0: irq 20, io mem 0xc2450000
[ 1.358655] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 1.365318] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 1.366025] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 2
[ 1.366487] ehci-pci 0000:00:1a.0: debug port 2
[ 1.370988] ehci-pci 0000:00:1a.0: irq 22, io mem 0xc2460000
[ 1.376629] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 1.603619] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 1.618645] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 2.108721] usb 2-1.1: new full-speed USB device number 3 using ehci-pci
[ 2.108938] usb 1-1.2: new full-speed USB device number 3 using ehci-pci
[ 2.345723] usb 1-1.3: new full-speed USB device number 4 using ehci-pci
[ 2.728641] usb 1-1.3.3: new full-speed USB device number 5 using ehci-pci
Click to expand...
This has persisted into 7.0 so I guess this motherboard is out of luck with future updates. :/
 
You must log in or register to reply here.
Top Bottom
Back