Opt-in Linux 6.11 Kernel for Proxmox VE 8 available on test & no-subscription

Had this crash recently using 6.11 kernel

Code: 
Feb 28 18:12:37.535630 homelab1 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000008
Feb 28 18:12:37.535795 homelab1 kernel: #PF: supervisor read access in kernel mode
Feb 28 18:12:37.537603 homelab1 kernel: #PF: error_code(0x0000) - not-present page
Feb 28 18:12:37.538671 homelab1 kernel: PGD 0 P4D 0
Feb 28 18:12:37.539739 homelab1 kernel: Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
Feb 28 18:12:37.539757 homelab1 kernel: CPU: 5 UID: 0 PID: 1850 Comm: pve-firewall Tainted: P           O       6.11.11-1-pve #1
Feb 28 18:12:37.539774 homelab1 kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
Feb 28 18:12:37.539786 homelab1 kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450M Pro4, BIOS P10.31 08/22/2024
Feb 28 18:12:37.539798 homelab1 kernel: RIP: 0010:__rb_insert_augmented+0x28/0x1e0
Feb 28 18:12:37.539810 homelab1 kernel: Code: 90 90 48 89 f8 48 8b 3f 48 85 ff 0f 84 af 01 00 00 55 48 89 e5 41 56 49 89 f6 41 55 49 89 d5 41 54 53 48 8b 1f f6 c3 01 75 68 <48> 8b 53 08 48 39 fa 74 76 48 85 d2 74 09 f6 02 01 0f 84 ae 00 00
Feb 28 18:12:37.539822 homelab1 kernel: RSP: 0018:ffff98f581787968 EFLAGS: 00010246
Feb 28 18:12:37.539834 homelab1 kernel: RAX: ffff88f2671ed1a8 RBX: 0000000000000000 RCX: ffff88f2671ed170
Feb 28 18:12:37.539848 homelab1 kernel: RDX: ffffffff8d9e8d70 RSI: ffff88f208233e98 RDI: ffff88f22b00f488
Feb 28 18:12:37.539863 homelab1 kernel: RBP: ffff98f581787988 R08: ffff88f22b00f498 R09: 0000000000000000
Feb 28 18:12:37.539872 homelab1 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff88f208233e50
Feb 28 18:12:37.539884 homelab1 kernel: R13: ffffffff8d9e8d70 R14: ffff88f208233e98 R15: ffff88f29cec5200
Feb 28 18:12:37.539896 homelab1 kernel: FS:  00007bba165bdb80(0000) GS:ffff8900de880000(0000) knlGS:0000000000000000
Feb 28 18:12:37.539913 homelab1 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 28 18:12:37.539925 homelab1 kernel: CR2: 0000000000000008 CR3: 00000001be9f8000 CR4: 0000000000350ef0
Feb 28 18:12:37.539937 homelab1 kernel: Call Trace:
Feb 28 18:12:37.539949 homelab1 kernel:  <TASK>
Feb 28 18:12:37.539962 homelab1 kernel:  ? show_regs+0x6c/0x80
Feb 28 18:12:37.539976 homelab1 kernel:  ? __die+0x24/0x80
Feb 28 18:12:37.539988 homelab1 kernel:  ? page_fault_oops+0x175/0x5e0
Feb 28 18:12:37.540000 homelab1 kernel:  ? __pte_offset_map+0x1c/0x1b0
Feb 28 18:12:37.540012 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540023 homelab1 kernel:  ? set_ptes.constprop.0+0x48/0xb0
Feb 28 18:12:37.540035 homelab1 kernel:  ? do_user_addr_fault+0x4a5/0x830
Feb 28 18:12:37.540046 homelab1 kernel:  ? exc_page_fault+0x85/0x1e0
Feb 28 18:12:37.540058 homelab1 kernel:  ? asm_exc_page_fault+0x27/0x30
Feb 28 18:12:37.540079 homelab1 kernel:  ? __pfx_vma_interval_tree_augment_rotate+0x10/0x10
Feb 28 18:12:37.540093 homelab1 kernel:  ? __pfx_vma_interval_tree_augment_rotate+0x10/0x10
Feb 28 18:12:37.540103 homelab1 kernel:  ? __rb_insert_augmented+0x28/0x1e0
Feb 28 18:12:37.540115 homelab1 kernel:  vma_interval_tree_insert_after+0x94/0xc0
Feb 28 18:12:37.540127 homelab1 kernel:  copy_process+0x2040/0x27f0
Feb 28 18:12:37.540138 homelab1 kernel:  kernel_clone+0xbc/0x430
Feb 28 18:12:37.540148 homelab1 kernel:  __do_sys_clone+0x66/0xa0
Feb 28 18:12:37.540160 homelab1 kernel:  __x64_sys_clone+0x25/0x40
Feb 28 18:12:37.540171 homelab1 kernel:  x64_sys_call+0x1d45/0x24e0
Feb 28 18:12:37.540183 homelab1 kernel:  do_syscall_64+0x7e/0x170
Feb 28 18:12:37.540197 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540208 homelab1 kernel:  ? syscall_exit_to_user_mode+0x4e/0x250
Feb 28 18:12:37.540220 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540232 homelab1 kernel:  ? do_syscall_64+0x8a/0x170
Feb 28 18:12:37.540244 homelab1 kernel:  ? do_pipe2+0xcb/0x110
Feb 28 18:12:37.540253 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540263 homelab1 kernel:  ? syscall_exit_to_user_mode+0x4e/0x250
Feb 28 18:12:37.540272 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540282 homelab1 kernel:  ? do_syscall_64+0x8a/0x170
Feb 28 18:12:37.540291 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540301 homelab1 kernel:  ? ptep_set_access_flags+0x4a/0x70
Feb 28 18:12:37.540313 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540322 homelab1 kernel:  ? wp_page_reuse+0x97/0xc0
Feb 28 18:12:37.540334 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540343 homelab1 kernel:  ? do_wp_page+0x8b8/0xc90
Feb 28 18:12:37.540355 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540364 homelab1 kernel:  ? __set_task_blocked+0x29/0x80
Feb 28 18:12:37.540376 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540388 homelab1 kernel:  ? sigprocmask+0xa3/0xd0
Feb 28 18:12:37.540400 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540409 homelab1 kernel:  ? _copy_to_user+0x41/0x60
Feb 28 18:12:37.540420 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540430 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540439 homelab1 kernel:  ? syscall_exit_to_user_mode+0x4e/0x250
Feb 28 18:12:37.540448 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540458 homelab1 kernel:  ? do_syscall_64+0x8a/0x170
Feb 28 18:12:37.540467 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540477 homelab1 kernel:  ? __count_memcg_events+0x7d/0x130
Feb 28 18:12:37.540486 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540496 homelab1 kernel:  ? count_memcg_events.constprop.0+0x2a/0x50
Feb 28 18:12:37.540505 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540515 homelab1 kernel:  ? handle_mm_fault+0xae/0x360
Feb 28 18:12:37.540526 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540536 homelab1 kernel:  ? do_user_addr_fault+0x5ec/0x830
Feb 28 18:12:37.540548 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540557 homelab1 kernel:  ? irqentry_exit_to_user_mode+0x43/0x250
Feb 28 18:12:37.540569 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540578 homelab1 kernel:  ? irqentry_exit+0x43/0x50
Feb 28 18:12:37.540590 homelab1 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 28 18:12:37.540599 homelab1 kernel:  ? exc_page_fault+0x96/0x1e0
Feb 28 18:12:37.540609 homelab1 kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Feb 28 18:12:37.540620 homelab1 kernel: RIP: 0033:0x7bba166cf313
Feb 28 18:12:37.540632 homelab1 kernel: Code: 00 00 00 00 00 66 90 64 48 8b 04 25 10 00 00 00 45 31 c0 31 d2 31 f6 bf 11 00 20 01 4c 8d 90 d0 02 00 00 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 89 c2 85 c0 75 2c 64 48 8b 04 25 10 00 00
Feb 28 18:12:37.540644 homelab1 kernel: RSP: 002b:00007ffeaa353f98 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
Feb 28 18:12:37.540656 homelab1 kernel: RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007bba166cf313
Feb 28 18:12:37.540668 homelab1 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
Feb 28 18:12:37.540682 homelab1 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
Feb 28 18:12:37.540694 homelab1 kernel: R10: 00007bba165bde50 R11: 0000000000000246 R12: 0000000000000001
Feb 28 18:12:37.540706 homelab1 kernel: R13: 00007ffeaa3540b0 R14: 00007ffeaa354130 R15: 00007bba16900020
Feb 28 18:12:37.540719 homelab1 kernel:  </TASK>
Feb 28 18:12:37.540731 homelab1 kernel: Modules linked in: cfg80211 nfsd auth_rpcgss nfs_acl lockd grace veth xt_MASQUERADE xt_tcpudp xt_mark ebtable_filter ebtables ip_set ip6table_raw iptable_raw scsi_transport_iscsi nvme_fabrics nvme_keyring nf_tables ip6table_nat ip6table_filter ip6_tables iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bonding tls qrtr sunrpc binfmt_misc nfnetlink_log nfnetlink tcp_bbr sch_fq input_leds joydev amd_atl intel_rapl_msr intel_rapl_common edac_mce_amd kvm_amd ccp kvm crct10dif_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd jc42 cryptd rapl wmi_bmof pcspkr ee1004 k10temp mac_hid zfs(PO) spl(O) vhost_net vhost vhost_iotlb tap nct6775 nct6775_core hwmon_vid wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel vfio_pci vfio_pci_core vfio_iommu_type1 vfio iommufd efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq
Feb 28 18:12:37.540778 homelab1 kernel:  dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c hid_generic usbkbd usbmouse usbhid uas hid usb_storage nvme nvme_core xhci_pci i2c_piix4 xhci_pci_renesas crc32_pclmul atlantic i2c_smbus r8169 ahci xhci_hcd macsec realtek nvme_auth libahci video wmi gpio_amdpt
Feb 28 18:12:37.540792 homelab1 kernel: CR2: 0000000000000008
Feb 28 18:12:37.540803 homelab1 kernel: ---[ end trace 0000000000000000 ]---
Feb 28 18:12:37.540813 homelab1 kernel: RIP: 0010:__rb_insert_augmented+0x28/0x1e0
Feb 28 18:12:37.540823 homelab1 kernel: Code: 90 90 48 89 f8 48 8b 3f 48 85 ff 0f 84 af 01 00 00 55 48 89 e5 41 56 49 89 f6 41 55 49 89 d5 41 54 53 48 8b 1f f6 c3 01 75 68 <48> 8b 53 08 48 39 fa 74 76 48 85 d2 74 09 f6 02 01 0f 84 ae 00 00
Feb 28 18:12:37.540836 homelab1 kernel: RSP: 0018:ffff98f581787968 EFLAGS: 00010246
Feb 28 18:12:37.540845 homelab1 kernel: RAX: ffff88f2671ed1a8 RBX: 0000000000000000 RCX: ffff88f2671ed170
Feb 28 18:12:37.540855 homelab1 kernel: RDX: ffffffff8d9e8d70 RSI: ffff88f208233e98 RDI: ffff88f22b00f488
Feb 28 18:12:37.540865 homelab1 kernel: RBP: ffff98f581787988 R08: ffff88f22b00f498 R09: 0000000000000000
Feb 28 18:12:37.540874 homelab1 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff88f208233e50
Feb 28 18:12:37.540884 homelab1 kernel: R13: ffffffff8d9e8d70 R14: ffff88f208233e98 R15: ffff88f29cec5200
Feb 28 18:12:37.540893 homelab1 kernel: FS:  00007bba165bdb80(0000) GS:ffff8900de880000(0000) knlGS:0000000000000000
Feb 28 18:12:37.540903 homelab1 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 28 18:12:37.540912 homelab1 kernel: CR2: 0000000000000008 CR3: 00000001be9f8000 CR4: 0000000000350ef0
Feb 28 18:12:37.540922 homelab1 kernel: note: pve-firewall[1850] exited with irqs disabled
Feb 28 18:17:08.494087 homelab1 kernel: smbd(7620): Attempt to set a LOCK_MAND lock via flock(2). This support has been removed and the request ignored.
-- Boot 56ce11783b194414a76113376a2b1944 --
Feb 28 18:46:42.926166 homelab1 kernel: Linux version 6.11.11-1-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.11.11-1 (2025-01-17T15:44Z) ()
Feb 28 18:46:42.926192 homelab1 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.11.11-1-pve root=/dev/mapper/pve-root ro quiet nofb nomodeset video=vesafb:off,efifb:off pcie_acs_override=downstream,multifunction fsck.mode=force fsck.repair=yes
Feb 28 18:46:42.926207 homelab1 kernel: KERNEL supported cpus:
 
xmesaj2 said:
Had this crash recently using 6.11 kernel

Code: 
Feb 28 18:12:37.535630 homelab1 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000008
Feb 28 18:12:37.535795 homelab1 kernel: #PF: supervisor read access in kernel mode
<snip>
Click to expand...
Chat GPT says:
It’s essentially a null-pointer dereference in the kernel’s memory-management code (you can see it die at __rb_insert_augmented while handling a process clone). The “Tainted: P O” means out-of-tree/proprietary modules are loaded (e.g., ZFS, wireguard, etc.). Most likely, an out-of-tree module or the Proxmox firewall code triggered a bug in the kernel’s red-black tree handling. In other words, something in the kernel or a third-party module passed an invalid pointer during process creation (the “pve-firewall” process in this case), causing the kernel to Oops.
 
d0glesby said:
I tried that, but nothing seems to override the graphics mode that the console ends up going into once the Linux kernel has loaded.
Click to expand...
You did
Code: 
update-grub
after you added that option?
Check it with
Code: 
cat /proc/cmdline
 
Yeah, I've run update-grub every time I make a change. Thanks for all the suggestions! I'll keep poking at this and see if I can get it working.
 
If I understand correctly, the problem is that at boot time the OS changes the resolution to one that the IPMI console does not support.
In my experience, if I forget a monitor is connected to VGA and it's at high resolution, IPMI doesn't load for me or loads part of the image full screen.
On older kernels there was an option with
vga=791, this may also help: GRU_TERMINAL=console.
Any of these primers might also be useful :
nofb nomodeset video=vesafb:off i915.modeset=0
Good luck with solving the problem :)
 
I've done just about all of those. I think UEFI boot is what is throwing something off during the boot process. Thankfully I have a handful of these systems that I can reboot at will. If I get some more free time I'll throw everything at it and see what sticks to make this work properly.
 
try doing the modification in /etc/kernel/cmdline instead of /default/grub and proxmox-kernel-tool refresh
d0glesby said:
I've done just about all of those. I think UEFI boot is what is throwing something off during the boot process. Thankfully I have a handful of these systems that I can reboot at will. If I get some more free time I'll throw everything at it and see what sticks to make this work properly.
Click to expand...
 
d0glesby said:
I tried that, but nothing seems to override the graphics mode that the console ends up going into once the Linux kernel has loaded.
Click to expand...
W

Thread 'FIX for iDrac issue on 6.11 Kernel'

THESE ARE THE STEPS TO FIX THE REMOTE CONTROL ISSUE ON THE DELL IDRAC WHEN YOU USE LINUX/PROXMOX KERNEL 6.11, THIS HAS BEEN TESTED AND WORKS CORRECTLY ON A DELL POWEREDGE R420 SERVER WITH IDRAC 7.



Login in your sever command line via SSH or PROXMOX GUI.


Run this command:
Bash: 
nano /etc/default/grub

Find this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"

Edit that line to this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset video=1024x768"

PRESS "CTRL + X" KEY COMBO AND SAVE THE CHANGES.

Then run this command:
Bash: 
update-grub


***NOW, THIS IS IMPORTANT:

POWER OFF THE SYSTEM VIA...
  • Like
 
wolframio said:
W

Thread 'FIX for iDrac issue on 6.11 Kernel'

THESE ARE THE STEPS TO FIX THE REMOTE CONTROL ISSUE ON THE DELL IDRAC WHEN YOU USE LINUX/PROXMOX KERNEL 6.11, THIS HAS BEEN TESTED AND WORKS CORRECTLY ON A DELL POWEREDGE R420 SERVER WITH IDRAC 7.



Login in your sever command line via SSH or PROXMOX GUI.


Run this command:
Bash: 
nano /etc/default/grub

Find this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"

Edit that line to this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset video=1024x768"

PRESS "CTRL + X" KEY COMBO AND SAVE THE CHANGES.

Then run this command:
Bash: 
update-grub


***NOW, THIS IS IMPORTANT:

POWER OFF THE SYSTEM VIA...
  • Like
Click to expand...
I just tried this on a Dell R740, and it did not fix the issue. The iDRAC virtual console shows text until the kernel boots up to a certain point, then displays the "NO SIGNAL" message. System operates fine otherwise.
 
d0glesby said:
I just tried this on a Dell R740, and it did not fix the issue. The iDRAC virtual console shows text until the kernel boots up to a certain point, then displays the "NO SIGNAL" message. System operates fine otherwise.
Click to expand...
did you follow every step??? even power off and unplug the system from the power after changes?
 
No, it seems to be defaulting to a very high resolution. If we boot up a system without a monitor attached it is much higher than 1920x1080.
 
You must log in or register to reply here.
Top Bottom