Upgrade to kernel 6.8.4-2 failed

s4nguine

New Member
Apr 26, 2024
2
0
1
Hello,

This is the first time I ran into problem during Proxmox upgrade.
I made a maintenance day to update my home hardware. For Proxmox it included kernel update from 6.5.13-5-pve to 6.8.4-2-pve.
At first I didn't notice any errors in the output and rebooted the server without thinking but I ended up stuck on
"Loading linux 6.8.4-2-pve" during boot.

I switched back to the older kernel, system luckily is up so I tried to run "apt install pve-kernel-6.8.4-2-pve" again to see what went wrong.
Here's the output:
Code:
root@pve01:~# apt install pve-kernel-6.8.4-2-pve
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'proxmox-kernel-6.8.4-2-pve' instead of 'pve-kernel-6.8.4-2-pve'
proxmox-kernel-6.8.4-2-pve is already the newest version (6.8.4-2).
The following packages were automatically installed and are no longer required:
  dctrl-tools g++-10 libstdc++-10-dev libtiff5 libwebp6 proxmox-headers-6.5.11-7-pve proxmox-headers-6.5.11-8-pve proxmox-headers-6.5.13-1-pve proxmox-kernel-6.5.11-7-pve-signed proxmox-kernel-6.5.11-8-pve-signed pve-headers
  pve-headers-5.15.102-1-pve pve-headers-5.15.104-1-pve pve-headers-5.15.107-1-pve pve-headers-5.15.107-2-pve pve-headers-5.15.108-1-pve pve-headers-5.15.111-1-pve pve-headers-5.15.116-1-pve pve-headers-5.15.126-1-pve
  pve-headers-5.15.131-1-pve pve-kernel-5.15.102-1-pve pve-kernel-5.15.104-1-pve pve-kernel-5.15.107-1-pve pve-kernel-5.15.107-2-pve pve-kernel-5.15.108-1-pve pve-kernel-5.15.111-1-pve pve-kernel-5.15.116-1-pve
  pve-kernel-5.15.126-1-pve pve-kernel-5.15.131-1-pve telnet
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up proxmox-kernel-6.8.4-2-pve (6.8.4-2) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.8.4-2-pve /boot/vmlinuz-6.8.4-2-pve
dkms: running auto installation service for kernel 6.8.4-2-pve.
Sign command: /lib/modules/6.8.4-2-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub


Building module:
Cleaning build area...
make -j12 KERNELRELEASE=6.8.4-2-pve KDIR=/lib/modules/6.8.4-2-pve/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.8.4-2-pve (x86_64)
Consult /var/lib/dkms/vendor-reset/0.1.1/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.8.4-2-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.8.4-2-pve.postinst line 20.
dpkg: error processing package proxmox-kernel-6.8.4-2-pve (--configure):
 installed proxmox-kernel-6.8.4-2-pve package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.8:
 proxmox-kernel-6.8 depends on proxmox-kernel-6.8.4-2-pve-signed | proxmox-kernel-6.8.4-2-pve; however:
  Package proxmox-kernel-6.8.4-2-pve-signed is not installed.
  Package proxmox-kernel-6.8.4-2-pve is not configured yet.
  Package proxmox-kernel-6.8.4-2-pve-signed which provides proxmox-kernel-6.8.4-2-pve is not installed.


dpkg: error processing package proxmox-kernel-6.8 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-6.8; however:
  Package proxmox-kernel-6.8 is not configured yet.


dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on proxmox-default-kernel; however:
  Package proxmox-default-kernel is not configured yet.


dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-6.8.4-2-pve
 proxmox-kernel-6.8
 proxmox-default-kernel
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

Content of var/lib/dkms/vendor-reset/0.1.1/build/make.log

Code:
DKMS make.log for vendor-reset-0.1.1 for kernel 6.8.4-2-pve (x86_64)
Fri Apr 26 07:21:46 PM CEST 2024
make -C /lib/modules/6.8.4-2-pve/build M=/var/lib/dkms/vendor-reset/0.1.1/build modules
make[1]: Entering directory '/usr/src/linux-headers-6.8.4-2-pve'
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/module.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/vendor-reset-dev.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/ioctl.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/ftrace.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/hook.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/common.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/compat.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/firmware.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/navi10.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/polaris10.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/vega10.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/vega20.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_device.o
/var/lib/dkms/vendor-reset/0.1.1/build/src/ioctl.c:91:5: warning: no previous prototype for ‘vendor_reset_ioctl_init’ [-Wmissing-prototypes]
   91 | int vendor_reset_ioctl_init(void)
      |     ^~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/ioctl.c:96:6: warning: no previous prototype for ‘vendor_reset_ioctl_exit’ [-Wmissing-prototypes]
   96 | void vendor_reset_ioctl_exit(void)
      |      ^~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/ftrace.c:66:5: warning: no previous prototype for ‘fh_install_hook’ [-Wmissing-prototypes]
   66 | int fh_install_hook(struct ftrace_hook *hook)
      |     ^~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/ftrace.c:96:6: warning: no previous prototype for ‘fh_remove_hook’ [-Wmissing-prototypes]
   96 | void fh_remove_hook(struct ftrace_hook *hook)
      |      ^~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/firmware.c:40:5: warning: no previous prototype for ‘amdgpu_io_rreg’ [-Wmissing-prototypes]
   40 | u32 amdgpu_io_rreg(struct amd_fake_dev *adev, u32 reg)
      |     ^~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/firmware.c:60:6: warning: no previous prototype for ‘amdgpu_io_wreg’ [-Wmissing-prototypes]
   60 | void amdgpu_io_wreg(struct amd_fake_dev *adev, u32 reg, u32 v)
      |      ^~~~~~~~~~~~~~
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_discovery.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_bios.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_atomfirmware.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/atom.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/common_baco.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/navi10_reg_init.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/navi12_reg_init.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/navi14_reg_init.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/polaris_baco.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/smu7_baco.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/vega10_reg_init.o
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/vega10.c:96:5: warning: no previous prototype for ‘vega10_baco_set_state’ [-Wmissing-prototypes]
   96 | int vega10_baco_set_state(struct amd_fake_dev *adev, enum BACO_STATE state)
      |     ^~~~~~~~~~~~~~~~~~~~~
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/vega20_reg_init.o
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_device.c:47:6: warning: no previous prototype for ‘amdgpu_device_vram_access’ [-Wmissing-prototypes]
   47 | void amdgpu_device_vram_access(struct amd_fake_dev *adev, loff_t pos,
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_bios.c:91:6: warning: no previous prototype for ‘amdgpu_read_bios’ [-Wmissing-prototypes]
   91 | bool amdgpu_read_bios(struct amd_fake_dev *adev)
      |      ^~~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_bios.c:156:6: warning: no previous prototype for ‘amdgpu_get_bios’ [-Wmissing-prototypes]
  156 | bool amdgpu_get_bios(struct amd_fake_dev *adev)
      |      ^~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/atom.c: In function ‘amdgpu_atom_parse’:
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/atom.c:1427:17: error: implicit declaration of function ‘strlcpy’; did you mean ‘strscpy’? [-Werror=implicit-function-declaration]
 1427 |                 strlcpy(ctx->vbios_version, str, sizeof(ctx->vbios_version));
      |                 ^~~~~~~
      |                 strscpy
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/vega20_reg_init.c:29:5: warning: no previous prototype for ‘vega20_reg_base_init’ [-Wmissing-prototypes]
   29 | int vega20_reg_base_init(struct amd_fake_dev *adev)
      |     ^~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/vega10_reg_init.c:29:5: warning: no previous prototype for ‘vega10_reg_base_init’ [-Wmissing-prototypes]
   29 | int vega10_reg_base_init(struct amd_fake_dev *adev)
      |     ^~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:243: /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/atom.o] Error 1
make[2]: *** [/usr/src/linux-headers-6.8.4-2-pve/Makefile:1926: /var/lib/dkms/vendor-reset/0.1.1/build] Error 2
make[1]: *** [Makefile:240: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.8.4-2-pve'
make: *** [Makefile:8: build] Error 2

Can you please help me make sense out of it?
Since there's a reference to the AMD iGPU it might be important - I'm running AMD Ryzen 5 5600G (version with iGPU)
Thank you in advance.
 
Consult /var/lib/dkms/vendor-reset/0.1.1/build/make.log for more information.
You need to update (git pull or download the latest) vendor-reset source, otherwise it is not compatible with Linux kernel 6.8. You might have to remove the currently installed module (with dkms remove vendor-reset/0.1.1 --all) before you dkms install . it again.
 
Last edited:
You need to update (git pull or download the latest) vendor-reset source, otherwise it is not compatible with Linux kernel 6.8. You might have to remove the currently installed module (with dkms remove vendor-reset/0.1.1 --all) before you dkms install . it again.

Solved my issue in under 60 seconds, thanks for including the commands. I made an account here just to say thanks, really appreciate it.
 
You need to update (git pull or download the latest) vendor-reset source, otherwise it is not compatible with Linux kernel 6.8. You might have to remove the currently installed module (with dkms remove vendor-reset/0.1.1 --all) before you dkms install . it again.
It has worked for me as well. Much appreciated. Cheers!
 
before the problem occurred, updated via GUI
I updated via gui and am also running vendor-reset and still experienced the issue. I looked in /boot/grub/grub.cfg and noticed no initramfs ref in the advanced section submenu nor the initrd.img-4.8.4-42 file in /boot for the default entry so I select previous working 4.5.13-5-pve. Spent too much time playing to get vendor-reset and iommu to work that all the intracacies have fallen out of my head to remember.
 

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 yours easily in our online shop.

Buy now!