linux kerkel 6.2.0.20-generic failed to install

Bug #2018420 reported by Michael Harden
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-20-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
   ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
 installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-generic:
 linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
  Package linux-headers-6.2.0-20-generic is not configured yet.

dpkg: error processing package linux-headers-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
  Package linux-headers-generic is not configured yet.

dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.37-0ubuntu2) ...
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                      Processing triggers for man-db (2.11.2-1) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-20-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash'
Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
   ...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
 installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1
No apport report written because MaxReports is reached already
                                                              Errors were encountered while processing:
 linux-headers-6.2.0-20-generic
 linux-headers-generic
 linux-generic
 linux-image-6.2.0-20-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
---
ProblemType: Bug
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michael 1934 F.... wireplumber
 /dev/snd/seq: michael 1932 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DistroRelease: Ubuntu 23.04
InstallationDate: Installed on 2019-01-13 (1572 days ago)
InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
IwConfig:
 lo no wireless extensions.

 eno1 no wireless extensions.

 virbr0 no wireless extensions.
MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=fb795829-c3ca-41fc-8f58-5448a75c1398 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-40-generic N/A
 linux-backports-modules-5.19.0-40-generic N/A
 linux-firmware 20230323.gitbcdcfbcf-0ubuntu1
RfKill:

Tags: lunar
Uname: Linux 5.19.0-40-generic x86_64
UpgradeStatus: Upgraded to lunar on 2023-04-23 (11 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/16/2013
dmi.bios.release: 2.90
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v02.90
dmi.board.asset.tag: AUD4100JVJ
dmi.board.name: 3397
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: AUD4100JVJ
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:skuC4K06PA#ABG:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Elite 8300 SFF
dmi.product.sku: C4K06PA#ABG
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Michael Harden (michaelharden1a) wrote :

DKMS make.log for vhba-20200106 for kernel 6.2.0-20-generic (x86_64)
Wed May 3 01:11:40 PM EDT 2023
make -C /lib/modules/6.2.0-20-generic/build M=/var/lib/dkms/vhba/20200106/build modules
make[1]: Entering directory '/usr/src/linux-headers-6.2.0-20-generic'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0
  You are using: gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0
  CC [M] /var/lib/dkms/vhba/20200106/build/vhba.o
/var/lib/dkms/vhba/20200106/build/vhba.c: In function ‘vhba_queuecommand_lck’:
/var/lib/dkms/vhba/20200106/build/vhba.c:474:8: error: ‘struct scsi_cmnd’ has no member named ‘scsi_done’
  474 | cmd->scsi_done = done;
      | ^~
In file included from /var/lib/dkms/vhba/20200106/build/vhba.c:42:
/var/lib/dkms/vhba/20200106/build/vhba.c: In function ‘vhba_queuecommand’:
/var/lib/dkms/vhba/20200106/build/vhba.c:483:15: error: too few arguments to function ‘vhba_queuecommand_lck’
  483 | DEF_SCSI_QCMD(vhba_queuecommand)
      | ^~~~~~~~~~~~~~~~~
./include/scsi/scsi_host.h:511:22: note: in definition of macro ‘DEF_SCSI_QCMD’
  511 | rc = func_name##_lck(cmd); \
      | ^~~~~~~~~
/var/lib/dkms/vhba/20200106/build/vhba.c:457:12: note: declared here
  457 | static int vhba_queuecommand_lck (struct scsi_cmnd *cmd, void (*done)(struct scsi_cmnd *))
      | ^~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vhba/20200106/build/vhba.c: In function ‘vhba_ctl_write’:
/var/lib/dkms/vhba/20200106/build/vhba.c:807:18: error: ‘struct scsi_cmnd’ has no member named ‘scsi_done’
  807 | vcmd->cmd->scsi_done(vcmd->cmd);
      | ^~
/var/lib/dkms/vhba/20200106/build/vhba.c: In function ‘vhba_ctl_release’:
/var/lib/dkms/vhba/20200106/build/vhba.c:942:18: error: ‘struct scsi_cmnd’ has no member named ‘scsi_done’
  942 | vcmd->cmd->scsi_done(vcmd->cmd);
      | ^~
make[2]: *** [scripts/Makefile.build:260: /var/lib/dkms/vhba/20200106/build/vhba.o] Error 1
make[1]: *** [Makefile:2026: /var/lib/dkms/vhba/20200106/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.2.0-20-generic'
make: *** [Makefile:14: modules] Error 2

this is from the change log that was asked to be referenced, I am running linux kernel 5.19.0.40 currently to get system to work, when booting off entry 6.2.0.20 gets kernel panic

did autoremove and that did not resolve this issue, also did what was suggested by someone else, but I did not have that package so that was not the issue for this one. if there is a work around, or a way to take care of the dependency let me know what im missing and ill install the packages that are needed

Colin Watson (cjwatson)
affects: launchpad → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 2018420

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Michael Harden (michaelharden1a) wrote :

Launchpad.net

    Launchpad Home Code Bugs Blueprints Translations Answers

Authorize application to access Launchpad on your behalf
Confirm Computer Access

The Ubuntu computer called michael-HP-Compaq-Elite-8300-SFF wants access to your Launchpad account. If you allow this, every application running on michael-HP-Compaq-Elite-8300-SFF will have read-write access to your Launchpad account, including to your private data.

If you're using a public computer, if michael-HP-Compaq-Elite-8300-SFF is not the computer you're using right now, or if something just doesn't feel right about this situation, you should choose "Do Not Allow 'michael-HP-Compaq-Elite-8300-SFF' to Access my Launchpad Account", or close this window now. You can always try again later.

Even if you decide to give michael-HP-Compaq-Elite-8300-SFF access to your Launchpad account, you can change your mind later.

Allow michael-HP-Compaq-Elite-8300-SFF to access my Launchpad account:

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: apport-collected lunar
description: updated
Revision history for this message
Michael Harden (michaelharden1a) wrote : AlsaInfo.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : CRDA.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : Lspci.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : Lspci-vt.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : Lsusb.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : Lsusb-t.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : Lsusb-v.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : PaInfo.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : ProcEnviron.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : ProcModules.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : UdevDb.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : WifiSyslog.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote : acpidump.txt

apport information

Revision history for this message
Michael Harden (michaelharden1a) wrote :

It generated the logs and I clicked on send, it did not report any errors so I assume it sent everything.

Revision history for this message
Juerg Haefliger (juergh) wrote :

You have an unsupported DKMS module (vhba) installed which doesn't compile for the 6.2 kernel and prevents the kernel upgrade. Please remove it and retry the upgrade.

Revision history for this message
Juerg Haefliger (juergh) wrote :

What's the output of:
$ dkms status

You can probably remove it with:
# dkms uninstall vhba

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Michael Harden (michaelharden1a) wrote (last edit ):

michael@michael-HP-Compaq-Elite-8300-SFF:~$ dkms status
vhba/20200106, 5.11.0-16-generic, x86_64: installed
vhba/20200106, 5.11.0-17-generic, x86_64: installed
vhba/20200106, 5.11.0-18-generic, x86_64: installed
vhba/20200106, 5.11.0-22-generic, x86_64: installed
vhba/20200106, 5.11.0-31-generic, x86_64: installed
vhba/20200106, 5.4.0-52-generic, x86_64: installed
vhba/20200106, 5.8.0-26-generic, x86_64: installed
vhba/20200106, 5.8.0-29-generic, x86_64: installed
vhba/20200106, 5.8.0-31-generic, x86_64: installed
vhba/20200106, 5.8.0-40-generic, x86_64: installed
virtualbox/7.0.6, 5.19.0-40-generic, x86_64: installed
virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed

I tried to uninstall but it needs to know the module and the version, should I just remove all of these?
I attempted to remove virtualbox since I already have boxes installed, and it does not seem to remove it, because its trying to install 6.0.2-20, appears it removed all but one package.

Revision history for this message
Juerg Haefliger (juergh) wrote :

That version refers to the dkms module version, not the kernel versions.

You have 2 dkms modules installed: vhba/20200106 and virtualbox/7.0.6.

You can keep virtualbox since it compiled successfully for 6.2:
  virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed

But you need to remove vhba/20200106. If you don't need it in the older kernels, the easiest is:
$ dkms remove vhba/20200106 --all

'dkms status' should then no longer list it. The dkms files are still there, the module is just removed from the dkms tree. If you want to (re-)add it again later:
$ dkms install vhba/20200106 --all

I think.

Revision history for this message
Juerg Haefliger (juergh) wrote :

Are these dkms'es Debian packages? What is the output of:
$ dpkg -l | grep dkms

If so, you could also purge them for good by removing the package:
$ apt purge vhba-dkms (or whatever the package name is)

Revision history for this message
Michael Harden (michaelharden1a) wrote :

Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-20-generic
   ...done.
Setting up linux-headers-generic (6.2.0.20.20) ...
Setting up linux-generic (6.2.0.20.20) ...
Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-20-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.2.0-20-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.2.0-20-generic
Found initrd image: /boot/initrd.img-6.2.0-20-generic
Found linux image: /boot/vmlinuz-5.19.0-40-generic
Found initrd image: /boot/initrd.img-5.19.0-40-generic
Found linux image: /boot/vmlinuz-5.11.0-31-generic
Found initrd image: /boot/initrd.img-5.11.0-31-generic
Found linux image: /boot/vmlinuz-5.11.0-22-generic
Found initrd image: /boot/initrd.img-5.11.0-22-generic
Found linux image: /boot/vmlinuz-5.11.0-18-generic
Found initrd image: /boot/initrd.img-5.11.0-18-generic
Found linux image: /boot/vmlinuz-5.11.0-17-generic
Found initrd image: /boot/initrd.img-5.11.0-17-generic
Found linux image: /boot/vmlinuz-5.11.0-16-generic
Found initrd image: /boot/initrd.img-5.11.0-16-generic
Found linux image: /boot/vmlinuz-5.8.0-40-generic
Found initrd image: /boot/initrd.img-5.8.0-40-generic
Found linux image: /boot/vmlinuz-5.8.0-31-generic
Found initrd image: /boot/initrd.img-5.8.0-31-generic
Found linux image: /boot/vmlinuz-5.8.0-29-generic
Found initrd image: /boot/initrd.img-5.8.0-29-generic
Found linux image: /boot/vmlinuz-5.8.0-26-generic
Found initrd image: /boot/initrd.img-5.8.0-26-generic
Found linux image: /boot/vmlinuz-5.4.0-52-generic
Found initrd image: /boot/initrd.img-5.4.0-52-generic
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
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.
Adding boot menu entry for UEFI Firmware Settings ...
done
Processing triggers for libc-bin (2.37-0ubuntu2) ...

I get this after I ran the command to remove VHBA/20200106, it seems that it sucessfully compiled and installed the new kernel, will reboot the computer and change the ticket if it works properly

Revision history for this message
Michael Harden (michaelharden1a) wrote :

UPdate, compiled, and rebooted, confirmed it is running 6.2.0-20 generic, getting error message at boot, but may not be anything at all, I will therefore put this ticket as complete.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
description: updated
Revision history for this message
Michael Harden (michaelharden1a) wrote :

issue resolved, please complete this

Juerg Haefliger (juergh)
Changed in linux (Ubuntu):
status: Fix Released → Invalid
Juerg Haefliger (juergh)
tags: added: lunar-upgrade-dkms-failure
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.