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

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
5,550
1,817
174
South Tyrol/Italy
shop.proxmox.com
We recently uploaded a 6.1 kernel into our repositories. The 5.15 kernel will stay the default on the Proxmox VE 7.x series, 6.1 is an option that replaces the previous 5.19 based opt-in kernel.
The 6.1 based kernel may be useful for some (especially newer) setups, for example if there is improved hardware support that has not yet been backported to 5.15.

How to install:
  • apt update
  • apt install pve-kernel-6.1
  • reboot
Future updates to the 6.1 kernel will now get installed automatically.

Please note:
  • Systems using PBS to backup their VMs and booting from ZFS (i.e., having the /tmp directory backed by ZFS) should avoid the initial pve-kernel-6.1.0-1-pve package due to a missing compat w.r.t. to tmp-files. Note that the issue is non-descructive, iow. all backups that actually finished, made when booted the initial 6.1 kernel, are OK and can be restored if booting an older, e.g., 5.19 or 5.15 kernel.
  • It's not required to enable the pvetest repository, the opt-in kernel package is available also on the no-subscription repository.
    But, as a newer pve-firmware package is required to fully use the new opt-in kernel we didn't yet upload it to the enterprise repository; that will be done in the following days.
  • While we are trying to provide a stable experience with the opt-in 6.1 kernel, updates may appear less frequently than for the default 5.15 based kernel.
  • If unsure, we recommend continuing to use the 5.15 based kernel.
Feedback is welcome!
 
Last edited:

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
5,550
1,817
174
South Tyrol/Italy
shop.proxmox.com
  • Like
Reactions: SkyDiver79

janssensm

Well-Known Member
Dec 18, 2016
243
82
53
Thanks!
While installing v6.1 I noticed that v5.15 was removed. I already had v5.19 installed too at that moment. So I ended up with v5.19 and v6.1 installed.
As this was a vm (nested pve) I rolled back and before installing v6.1 again I removed v5.19. Now it ended with v5.15 and v6.1 installed.

To me it seems wise to at least keep v5.15 as current stable kernel for fallback, maybe an extra notice/warning for this behavior is necessary as this seems the first time that 2 opt-in kernels are available at the same time.
Otherwise, great effort and thanks, I will test first further in a vm and later on a physical server. So far running great.
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,659
972
173
While installing v6.1 I noticed that v5.15 was removed
That is not default. Please provide logs. 5.15 is default and never removed.
 

janssensm

Well-Known Member
Dec 18, 2016
243
82
53
@tom

pve-no-subscription repo.
root@pvetest01:~# cat /etc/apt/sources.list
deb http://ftp.nl.debian.org/debian bullseye main contrib

deb http://ftp.nl.debian.org/debian bullseye-updates main contrib

# security updates
deb http://security.debian.org bullseye-security main contrib

deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription


root@pvetest01:~# pveversion
pve-manager/7.3-3/c3928077 (running kernel: 5.19.17-1-pve)

root@pvetest01:~# proxmox-boot-tool kernel list
Manually selected kernels:
None.

Automatically selected kernels:
5.15.74-1-pve
5.19.17-1-pve

root@pvetest01:~# dpkg-query --list | grep pve-kernel
ii pve-firmware 3.6-1 all Binary firmware code for the pve-kernel
ii pve-kernel-5.15 7.2-14 all Latest Proxmox VE Kernel Image
ii pve-kernel-5.15.74-1-pve 5.15.74-1 amd64 Proxmox Kernel Image
ii pve-kernel-5.19 7.2-14 all Latest Proxmox VE Kernel Image
ii pve-kernel-5.19.17-1-pve 5.19.17-1 amd64 Proxmox Kernel Image
ii pve-kernel-helper 7.3-1 all Function for various kernel maintenance tasks.

root@pvetest01:~# apt install pve-kernel-6.1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
pve-kernel-6.1.0-1-pve
The following NEW packages will be installed:
pve-kernel-6.1 pve-kernel-6.1.0-1-pve
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 78.6 MB of archives.
After this operation, 422 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 pve-kernel-6.1.0-1-pve amd64 6.1.0-1 [78.6 MB]
Get:2 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 pve-kernel-6.1 all 7.3-1 [5,048 B]
Fetched 78.6 MB in 8s (10.0 MB/s)
Selecting previously unselected package pve-kernel-6.1.0-1-pve.
(Reading database ... 51251 files and directories currently installed.)
Preparing to unpack .../pve-kernel-6.1.0-1-pve_6.1.0-1_amd64.deb ...
Unpacking pve-kernel-6.1.0-1-pve (6.1.0-1) ...
Selecting previously unselected package pve-kernel-6.1.
Preparing to unpack .../pve-kernel-6.1_7.3-1_all.deb ...
Unpacking pve-kernel-6.1 (7.3-1) ...
Setting up pve-kernel-6.1.0-1-pve (6.1.0-1) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 6.1.0-1-pve /boot/vmlinuz-6.1.0-1-pve
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.1.0-1-pve /boot/vmlinuz-6.1.0-1-pve
update-initramfs: Generating /boot/initrd.img-6.1.0-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/728B-567B
Copying kernel 5.19.17-1-pve
Copying kernel 6.1.0-1-pve
Removing old version 5.15.74-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.0-1-pve
Found initrd image: /boot/initrd.img-6.1.0-1-pve
Found linux image: /boot/vmlinuz-5.19.17-1-pve
Found initrd image: /boot/initrd.img-5.19.17-1-pve
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
Copying and configuring kernels on /dev/disk/by-uuid/728C-9660
Copying kernel 5.19.17-1-pve
Copying kernel 6.1.0-1-pve
Removing old version 5.15.74-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.0-1-pve
Found initrd image: /boot/initrd.img-6.1.0-1-pve
Found linux image: /boot/vmlinuz-5.19.17-1-pve
Found initrd image: /boot/initrd.img-5.19.17-1-pve
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
run-parts: executing /etc/kernel/postinst.d/proxmox-auto-removal 6.1.0-1-pve /boot/vmlinuz-6.1.0-1-pve
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 6.1.0-1-pve /boot/vmlinuz-6.1.0-1-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/728B-567B
Copying kernel 5.19.17-1-pve
Copying kernel 6.1.0-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.0-1-pve
Found initrd image: /boot/initrd.img-6.1.0-1-pve
Found linux image: /boot/vmlinuz-5.19.17-1-pve
Found initrd image: /boot/initrd.img-5.19.17-1-pve
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
Copying and configuring kernels on /dev/disk/by-uuid/728C-9660
Copying kernel 5.19.17-1-pve
Copying kernel 6.1.0-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.0-1-pve
Found initrd image: /boot/initrd.img-6.1.0-1-pve
Found linux image: /boot/vmlinuz-5.19.17-1-pve
Found initrd image: /boot/initrd.img-5.19.17-1-pve
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 6.1.0-1-pve /boot/vmlinuz-6.1.0-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.0-1-pve
Found initrd image: /boot/initrd.img-6.1.0-1-pve
Found linux image: /boot/vmlinuz-5.19.17-1-pve
Found initrd image: /boot/initrd.img-5.19.17-1-pve
Found linux image: /boot/vmlinuz-5.15.74-1-pve
Found initrd image: /boot/initrd.img-5.15.74-1-pve
Found memtest86+ image: /ROOT/pve-1@/boot/memtest86+.bin
Found memtest86+ multiboot image: /ROOT/pve-1@/boot/memtest86+_multiboot.bin
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
Setting up pve-kernel-6.1 (7.3-1) ...

root@pvetest01:~# proxmox-boot-tool kernel list
Manually selected kernels:
None.

Automatically selected kernels:
5.19.17-1-pve
6.1.0-1-pve
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,659
972
173
strange. your pveversion -v?
 

janssensm

Well-Known Member
Dec 18, 2016
243
82
53
root@pvetest01:~# pveversion -v
proxmox-ve: 7.3-1 (running kernel: 6.1.0-1-pve)
pve-manager: 7.3-3 (running version: 7.3-3/c3928077)
pve-kernel-6.1: 7.3-1
pve-kernel-helper: 7.3-1
pve-kernel-5.15: 7.2-14
pve-kernel-5.19: 7.2-14
pve-kernel-6.1.0-1-pve: 6.1.0-1
pve-kernel-5.19.17-1-pve: 5.19.17-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.3
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-1
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.3-1
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.3.1-1
proxmox-backup-file-restore: 2.3.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-1
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.6-1
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-1
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1

This is a pretty fresh pve vm, installed from proxmox-ve_7.3-1.iso, without noteworthy customizations.
For the moment this will my last reply, if you need more info I can test further tomorrow.

Kind regards


Edit: now I just saw that in above info the 5.15 is listed, but I already did a reboot of the vm, and saw in the grub boot selection no option for 5.15.
Last message today ;-)
 
Last edited:

Neobin

Famous Member
Apr 29, 2021
1,106
391
83
That escalated arrived quickly; thank you very much. :)

My AMD 5700G was using the amd-pstate driver with 5.19; now with 6.1 it is back to: acpi-cpufreq. Is there a reason for this?

Unfortunately I can not yet check my AMD 5950X, which even with 5.19 still uses the acpi-cpufreq driver (why?), because of the currently most likely too old nvidia-driver from Debian... :(
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
5,550
1,817
174
South Tyrol/Italy
shop.proxmox.com
Any plans to enable MG-LRU in 6.1 builds?
It is already compiled in, as you can see in the Kconfig used for compilation, i.e., in /boot/config-6.1.0-1-pve.
It's just not enabled by default - as it's very new and can make things also worse in some situations.

You can just enable it yourself if you want to use it, from your linked docs:
echo y >/sys/kernel/mm/lru_gen/enabled
 

fiona

Proxmox Staff Member
Staff member
Aug 1, 2019
2,615
546
118
Hi,
Edit: now I just saw that in above info the 5.15 is listed, but I already did a reboot of the vm, and saw in the grub boot selection no option for 5.15.
Last message today ;-)
I guess proxmox-boot-tool only automatically select kernels from the latest two versions. You can add the 5.15 kernel with proxmox-boot-tool kernel add 5.15.74-1-pve and then proxmox-boot-tool refresh.
 
  • Like
Reactions: janssensm

UdoB

Renowned Member
Nov 1, 2016
435
128
68
Germany
The 5.15 kernel will stay the default on the Proxmox VE 7.x series, 6.1 is an option that replaces the previous 5.19 based opt-in kernel.
Great!
What is recommended for 5.19 users?

Currently I am in a stable situation, running 5.19 for some required improvements - in a production setting. Will 5.19 get security updates (for some time) or is it already recommended to switch to 6.1? (I have a scheduled maintenance for Xmas...)

Best regards
 

leesteken

Famous Member
May 31, 2020
2,630
569
118
PCIe passthrough appears to work fine. amdgpu hand-off of GPU to vfio-pci still works in 6.1 (like in 5.19 and unlike 5.15, 5.13), although it does give an ugly stack trace (which it did not do on 5.19):

Code:
dec 15 13:44:00 sentry kernel: Linux version 6.1.0-1-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT_DYNAMIC PVE 6.1.0-1 (Tue, 13 Dec 2022 15:08:53 +0
dec 15 13:44:00 sentry kernel: Command line: initrd=\EFI\proxmox\6.1.0-1-pve\initrd.img-6.1.0-1-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs consoleblank=0 iommu=pt acpi_enforce_resources=lax
dec 15 13:45:05 sentry kernel: Console: switching to colour dummy device 80x25
dec 15 13:45:06 sentry kernel: amdgpu 0000:0b:00.0: amdgpu: amdgpu: finishing device.
dec 15 13:45:07 sentry kernel: ------------[ cut here ]------------
dec 15 13:45:07 sentry kernel: WARNING: CPU: 23 PID: 86416 at drivers/gpu/drm/drm_mode_object.c:107 drm_mode_object_unregister+0x8c/0x90 [drm]
dec 15 13:45:07 sentry kernel: Modules linked in: binfmt_misc veth ebt_arp ebtable_filter ebtables ip6table_raw ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables iptable_raw xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_addrtype xt_multiport xt_conntrack xt_NFLOG xt_limit xt_comment xt_tcpudp xt_set xt_mark ip_set_hash_net ip_set lz4hc lz4hc_compress zram iptable_filter bpfilter 8021q garp mrp bonding tls nfnetlink_log nfnetlink vhost_net vhost vhost_iotlb tap si2157 si2168 i2c_mux em28xx_dvb rc_hauppauge dvb_core em28xx_rc radeon intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd input_leds kvm_amd usbkbd usbmouse amdgpu mt7921e kvm mt7921_common mt76_connac_lib iommu_v2 crct10dif_pclmul mt76 gpu_sched polyval_clmulni polyval_generic drm_buddy ghash_clmulni_intel video sha512_ssse3 drm_ttm_helper mac80211 ttm aesni_intel drm_display_helper crypto_simd cryptd cec rapl rc_core cfg80211 pcspkr efi_pstore drm_kms_helper gigabyte_wmi wmi_bmof k10temp ccp i2c_algo_bit fb_sys_fops syscopyarea
dec 15 13:45:07 sentry kernel:  sysfillrect sysimgblt libarc4 mac_hid em28xx tveeprom videodev mc ledtrig_heartbeat it87 hwmon_vid nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr drm sunrpc ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) btrfs blake2b_generic xor raid6_pq zstd_compress libcrc32c hid_generic usbhid hid simplefb xhci_pci vfio_pci vendor_reset(O) vfio_pci_core irqbypass vfio_virqfd crc32_pclmul vfio_iommu_type1 ahci nvme vfio xhci_pci_renesas i2c_piix4 libahci igc nvme_core xhci_hcd nvme_common wmi
dec 15 13:45:07 sentry kernel: CPU: 23 PID: 86416 Comm: task UPID:sentr Tainted: P           O       6.1.0-1-pve #1
dec 15 13:45:07 sentry kernel: Hardware name: Gigabyte Technology Co., Ltd. X570S AERO G/X570S AERO G, BIOS F4c 05/12/2022
dec 15 13:45:07 sentry kernel: RIP: 0010:drm_mode_object_unregister+0x8c/0x90 [drm]
dec 15 13:45:07 sentry kernel: Code: 06 ce 5b 41 5c 41 5d 5d c3 cc cc cc cc 44 0f b6 6f 50 41 80 fd 01 0f 87 ed 84 01 00 41 83 e5 01 74 9a 49 83 7c 24 18 00 75 92 <0f> 0b eb 8e 0f 1f 44 00 00 55 48 89 e5 81 ff cc cc cc cc 74 17 81
dec 15 13:45:07 sentry kernel: RSP: 0018:ffffbb98c5747b38 EFLAGS: 00010246
dec 15 13:45:07 sentry kernel: RAX: ffffffffc561c600 RBX: ffff9179f34a0010 RCX: 0000000000000000
dec 15 13:45:07 sentry kernel: RDX: ffff9179f34b6660 RSI: ffff9179f34b6620 RDI: ffff9179f34a0010
dec 15 13:45:07 sentry kernel: RBP: ffffbb98c5747b50 R08: 0000000000000001 R09: 0000000000b71b00
dec 15 13:45:07 sentry kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff9179f34b6620
dec 15 13:45:07 sentry kernel: R13: 0000000000000001 R14: ffff9179f34a0010 R15: 0000000000000001
dec 15 13:45:07 sentry kernel: FS:  00007f14cd838280(0000) GS:ffff9188cefc0000(0000) knlGS:0000000000000000
dec 15 13:45:07 sentry kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
dec 15 13:45:07 sentry kernel: CR2: 000056167fc1bfbc CR3: 00000005b8628000 CR4: 0000000000750ee0
dec 15 13:45:07 sentry kernel: PKRU: 55555554
dec 15 13:45:07 sentry kernel: Call Trace:
dec 15 13:45:07 sentry kernel:  <TASK>
dec 15 13:45:07 sentry kernel:  drm_encoder_cleanup+0x54/0xd0 [drm]
dec 15 13:45:07 sentry kernel:  amdgpu_dm_fini+0x61/0x240 [amdgpu]
dec 15 13:45:07 sentry kernel:  dm_hw_fini+0x23/0x30 [amdgpu]
dec 15 13:45:07 sentry kernel:  amdgpu_device_fini_hw+0x2e1/0x3c0 [amdgpu]
dec 15 13:45:07 sentry kernel:  amdgpu_driver_unload_kms+0x51/0x60 [amdgpu]
dec 15 13:45:07 sentry kernel:  amdgpu_pci_remove+0x52/0x140 [amdgpu]
dec 15 13:45:07 sentry kernel:  ? __pm_runtime_resume+0x60/0x90
dec 15 13:45:07 sentry kernel:  pci_device_remove+0x39/0xb0
dec 15 13:45:07 sentry kernel:  device_remove+0x46/0x70
dec 15 13:45:07 sentry kernel:  device_release_driver_internal+0x1fa/0x280
dec 15 13:45:07 sentry kernel:  device_driver_detach+0x14/0x20
dec 15 13:45:07 sentry kernel:  unbind_store+0x12a/0x140
dec 15 13:45:07 sentry kernel:  drv_attr_store+0x24/0x40
dec 15 13:45:07 sentry kernel:  sysfs_kf_write+0x3f/0x50
dec 15 13:45:07 sentry kernel:  kernfs_fop_write_iter+0x13f/0x1d0
dec 15 13:45:07 sentry kernel:  vfs_write+0x2a7/0x3b0
dec 15 13:45:07 sentry kernel:  ksys_write+0x67/0xf0
dec 15 13:45:07 sentry kernel:  __x64_sys_write+0x1a/0x20
dec 15 13:45:07 sentry kernel:  do_syscall_64+0x5c/0x90
dec 15 13:45:07 sentry kernel:  ? syscall_exit_to_user_mode+0x26/0x50
dec 15 13:45:07 sentry kernel:  ? __x64_sys_lseek+0x1a/0x20
dec 15 13:45:07 sentry kernel:  ? do_syscall_64+0x69/0x90
dec 15 13:45:07 sentry kernel:  ? do_syscall_64+0x69/0x90
dec 15 13:45:07 sentry kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
dec 15 13:45:07 sentry kernel:  ? irqentry_exit+0x3b/0x50
dec 15 13:45:07 sentry kernel:  ? exc_page_fault+0x87/0x180
dec 15 13:45:07 sentry kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
dec 15 13:45:07 sentry kernel: RIP: 0033:0x7f14cda5afb3
dec 15 13:45:07 sentry kernel: Code: 75 05 48 83 c4 58 c3 e8 cb 41 ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 64 8b 04 25 18 00 00 00 85 c0 75 14 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 55 c3 0f 1f 40 00 48 83 ec 28 48 89 54 24 18
dec 15 13:45:07 sentry kernel: RSP: 002b:00007fffe8190618 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
dec 15 13:45:07 sentry kernel: RAX: ffffffffffffffda RBX: 00005643e5c24e90 RCX: 00007f14cda5afb3
dec 15 13:45:07 sentry kernel: RDX: 000000000000000c RSI: 00005643e5c24e90 RDI: 0000000000000009
dec 15 13:45:07 sentry kernel: RBP: 000000000000000c R08: 0000000000000000 R09: 00005643df1733b0
dec 15 13:45:07 sentry kernel: R10: 00005643e5c03318 R11: 0000000000000246 R12: 00005643e5c23200
dec 15 13:45:07 sentry kernel: R13: 00005643e00c02a0 R14: 0000000000000009 R15: 00005643e5c23200
dec 15 13:45:07 sentry kernel:  </TASK>
dec 15 13:45:07 sentry kernel: ---[ end trace 0000000000000000 ]---
dec 15 13:45:07 sentry kernel: [drm] amdgpu: ttm finalized
dec 15 13:45:07 sentry kernel: vfio-pci 0000:0b:00.0: vgaarb: deactivate vga console
dec 15 13:45:07 sentry kernel: vfio-pci 0000:0b:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
dec 15 13:45:07 sentry kernel: vfio-pci 0000:0b:00.0: AMD_POLARIS10: version 1.1
dec 15 13:45:07 sentry kernel: vfio-pci 0000:0b:00.0: AMD_POLARIS10: performing pre-reset
dec 15 13:45:07 sentry kernel: vfio-pci 0000:0b:00.0: AMD_POLARIS10: performing reset
dec 15 13:45:07 sentry kernel: vfio-pci 0000:0b:00.0: AMD_POLARIS10: CLOCK_CNTL: 0x0, PC: 0x205c4
dec 15 13:45:07 sentry kernel: vfio-pci 0000:0b:00.0: AMD_POLARIS10: Performing BACO reset
dec 15 13:45:07 sentry kernel: vfio-pci 0000:0b:00.0: AMD_POLARIS10: performing post-reset
dec 15 13:45:07 sentry kernel: vfio-pci 0000:0b:00.0: AMD_POLARIS10: reset result = 0
 

jasonsansone

Active Member
May 17, 2021
127
29
28
Oklahoma City, OK
www.sansonehowell.com
It is already compiled in, as you can see in the Kconfig used in /boot/config-6.1.0-1-pve, just not enabled by default - as it's very new and can make things also worse in some situations.

You can just enable it yourself if you want to use it, from your linked docs:
echo y >/sys/kernel/mm/lru_gen/enabled

Testing on three nodes. Nothing has blown up (yet).
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
5,550
1,817
174
South Tyrol/Italy
shop.proxmox.com
Will 5.19 get security updates (for some time) or is it already recommended to switch to 6.1?
Nothing 100% definite yet, but we'll probably do a final update for 5.19 over the next weeks and then might even switch the pve-kernel-5.19 meta package over to depend on (or at least recommend) pve-kernel-6.1 to avoid that users that did not notice the new opt-in kernel to be stuck on an outdated kernel; but I'd think that we'd only do so in a few weeks after the final update.

If you need to run a newer kernel than the 5.15 one, e.g. due to HW needs or the like, I'd recommend to first test and then switch over to the new 6.1 based opt-in kernel rather sooner (say next few weeks) than later.
 
  • Like
Reactions: flames and UdoB

xi784

Member
Feb 14, 2019
16
4
8
38
That escalated arrived quickly; thank you very much. :)

My AMD 5700G was using the amd-pstate driver with 5.19; now with 6.1 it is back to: acpi-cpufreq. Is there a reason for this?

Unfortunately I can not yet check my AMD 5950X, which even with 5.19 still uses the acpi-cpufreq driver (why?), because of the currently most likely too old nvidia-driver from Debian... :(
you need:
amd_pstate=passive

sometimes
amd_pstate.shared_mem=1 amd_pstate=passive

in grub line
greetz
 

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!

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 your own in 60 seconds.

Buy now!