Kernel update to 5.4.0-58 breaks system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu MATE |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login.
If you are able to request a shutdown, you get the message that caja is not responding.
Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN).
Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem.
Reproducible.
---
ProblemType: Bug
ApportVersion: 2.20.11-
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CasperMD5CheckR
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-01-25 (324 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: ASUSTeK COMPUTER INC. TP500LN
NonfreeKernelMo
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.187.6
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: focal
Uname: Linux 5.4.0-48-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark
_MarkForUpload: True
dmi.bios.date: 06/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: TP500LN.203
dmi.board.
dmi.board.name: TP500LN
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: TP
dmi.product.name: TP500LN
dmi.product.sku: ASUS-NotebookSKU
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
modified.
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile.
Changed in ubuntu-mate: | |
status: | Confirmed → Fix Released |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Released |
please attach logs with `apport-collect 1907992`