linux-image-6.2.0-20-generic install failed

Bug #2017586 reported by greg gaustad
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dkms (Ubuntu)
New
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

during upgrade from 22.10 to 23.04
installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1
---
ProblemType: Bug
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: gregg 3609 F.... pipewire
                      gregg 3613 F.... wireplumber
 /dev/snd/controlC0: gregg 3613 F.... wireplumber
 /dev/snd/seq: gregg 3609 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroRelease: Ubuntu 23.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=2bcaea5c-fe56-452a-97ac-2315908d2c0a
InstallationDate: Installed on 2017-10-27 (2005 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
MachineType: Dell Inc. Latitude 7480
Package: linux (not installed)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=0e02fc8e-5e0e-4df8-91b3-72ab7fc37d78 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.
RebootRequiredPkgs: Error: path contained symlinks.
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
Tags: lunar
Uname: Linux 5.19.0-40-generic x86_64
UpgradeStatus: Upgraded to lunar on 2023-04-24 (0 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare scanner sudo wireshark
_MarkForUpload: True
dmi.bios.date: 06/05/2020
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 00F6D3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd06/05/2020:br1.18:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:sku07A0:
dmi.product.family: Latitude
dmi.product.name: Latitude 7480
dmi.product.sku: 07A0
dmi.sys.vendor: Dell Inc.

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 2017586

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
greg gaustad (ggaustad) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected lunar
description: updated
Revision history for this message
greg gaustad (ggaustad) wrote : CRDA.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : CurrentDmesg.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : IwConfig.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : Lspci.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : Lspci-vt.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : Lsusb.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : Lsusb-t.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : Lsusb-v.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : PaInfo.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : ProcInterrupts.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : ProcModules.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : RfKill.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : UdevDb.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : WifiSyslog.txt

apport information

Revision history for this message
greg gaustad (ggaustad) wrote : acpidump.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Juerg Haefliger (juergh) wrote :

Not sure if this is related but dmesg shows a lot of PCIe errors like:

[342155.015795] pcieport 0000:00:1c.2: AER: Corrected error received: 0000:00:1c.2
[342155.015824] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[342155.015833] pcieport 0000:00:1c.2: device [8086:9d12] error status/mask=00001000/00002000
[342155.015842] pcieport 0000:00:1c.2: [12] Timeout
[342273.645526] pcieport 0000:00:1c.2: AER: Corrected error received: 0000:00:1c.2
[342273.645547] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[342273.645554] pcieport 0000:00:1c.2: device [8086:9d12] error status/mask=00001000/00002000
[342273.645562] pcieport 0000:00:1c.2: [12] Timeout

Wifi is connected to that PCIe port. Are you trying to upgrade over wifi?

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

I'm also seeing this with the 5.19 kernel so apparently not a new issue. But it's still unclear if that is the reason for the failed upgrade.

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

I need some logs from when you performed the upgrade. Specifically:
/var/log/apt/*
/var/log/dpkg*

Can you look through the above and see if you can find a sensible error message? Specifically in /var/log/apt/term.log* from when you did the upgrade?

Also, do you have any wonky DKMS modules installed? What's the output of:
$ dkms status

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
greg gaustad (ggaustad) wrote : Re: [Bug 2017586] Re: linux-image-6.2.0-20-generic install failed
Download full text (3.6 KiB)

Jeurg:

FYI- My responses are delayed due to remodeling of my house.

Yes, upgrade was done over wifi

/var/log/apt/term.log relevant lines from the period encompassing the
time of upgrade

snapd.failure.service is a disabled or a static unit not running, not
starting it.
snapd.snap-repair.service is a disabled or a static unit not running,
not starting it.
Failed to restart snapd.mounts-pre.target: Operation refused, unit
snapd.mounts-pre.target may be requested by dependency only (it is
configured to refuse manual start/stop).
See system logs and 'systemctl status snapd.mounts-pre.target' for details.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.

update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults

update-notifier-download.service is a disabled or a static unit not
running, not starting it.
update-notifier-motd.service is a disabled or a static unit not running,
not starting it.

Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing
complain mode
Warning from /etc/apparmor.d/usr.sbin.sssd
(/etc/apparmor.d/usr.sbin.sssd line 60): Caching disabled for:
'usr.sbin.sssd' due to force complain
sssd-autofs.service is a disabled or a static unit not running, not
starting it.
sssd-nss.service is a disabled or a static unit not running, not
starting it.
sssd-pam.service is a disabled or a static unit not running, not
starting it.
sssd-ssh.service is a disabled or a static unit not running, not
starting it.
sssd-sudo.service is a disabled or a static unit not running, not
starting it.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.

sssd-pac.service is a disabled or a static unit not running, not
starting it.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.

Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
------------------------------------------------
/var/log/dpkg.<time-of upgrade> found nothing error like
/var/log/apt/history.log.<time-of upgrade> found nothing error like
------------------------------------------------

dkms status
Deprecated feature: REMAKE_INITRD
(/var/lib/dkms/intel-hid/3.1/source/dkms.conf)
Deprecated feature: REMAKE_INITRD
(/var/lib/dkms/intel-hid/3.1/source/dkms.conf)
Deprecated feature: REMAKE_INITRD
(/var/lib/dkms/oem-ethernet-e1000e-for-i219/4/source/dkms.conf)
Deprecated feature: REMAKE_INITRD
(/var/lib/dkms/oem-ethernet-e1000e-for-i219/4/source/dkms.conf)
hid-alps/0.0.20160824, 4.4.0-174-generic, x86_64: installed
hid-alps/0.0.20160824, 4.4.0-176-generic, x86_64: installed
intel-hid/3.1, 4.4.0-174-generic, x86_64: installed
intel-hid/3.1, 4.4.0-176-generic, x86_64: installed
oem-audio-hda-daily/0.201708030416~ubuntu16.04.1, 4.4.0-174-generic,
x86_64: installed
oem-audio-hda-daily/0.201708030416~ubuntu16.04.1, 4.4.0-176-generic,
x86_64: installed
oem-ethernet-e1000e-for-i219/4, 4.4.0-174-generic, x86_64: installed
oem-ethernet-e1000e-for-i219/4, 4.4.0-176-generic, x86_64: installed

On 5/8/23 1:43 AM, Ju...

Read more...

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

Hm. Not sure if these snap errors are relevant. I suggest to disable the DKMS modules and retry the kernel upgrade. There is a dkms regression that results in a kernel installation failure.

Also, your DKMS modules seem to be really old. Do you still need them? And you might want to purge old kernels...

To remove the DKMS modules:
$ dkms remove hid-alps/0.0.20160824 --all
$ dkms remove intel-hid/3.1 --all
$ dkms remove oem-ethernet-e1000e-for-i219/4 --all

Revision history for this message
Pete Cowley (prcowley) wrote :

I accidentally discovered a fix for this issue whilst searching the web.

I saw something that mentioned Linus-headers-6.2.0-20 ... I didn't have it.
I downloaded it and it immediately recompiled the modules (and I was missing bluetooth) and created a new linus-image-6.2.0.20 files. Rebooted and now bluetooth works and no errors in updating software.

Hopefully this might help someone in need.

Cheers
Pete Cowley, New Zealand

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

Hm. This should not really result in a kernel upgrade failure. Reassigning to 'dkms' package.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Juerg Haefliger (juergh) wrote :
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.