Kernel update to 5.4.0-58 breaks system

Bug #1907992 reported by Lubensius
12
This bug affects 2 people
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-0ubuntu27.13
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: sven 1771 F.... pulseaudio
 /dev/snd/controlC0: sven 1771 F.... pulseaudio
CasperMD5CheckResult: skip
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
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-48-generic N/A
 linux-backports-modules-5.4.0-48-generic N/A
 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.asset.tag: ATN12345678901234567
dmi.board.name: TP500LN
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: TP
dmi.product.name: TP500LN
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
modified.conffile..etc.default.apport:
 # 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..etc.default.apport: 2020-01-29T20:18:17.309547

Revision history for this message
Norbert (nrbrtx) wrote :

please attach logs with `apport-collect 1907992`

tags: added: focal
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 1907992

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
Lubensius (lubensius) wrote :

UPDATE:

I updated my Dev VM with has similar configuration to 5.4.0-58 and this works without obvious problems.
While trying the reproduce the failure on the ASUS laptop I found that that there is no problem when network is disconnected. Problem appears, when network is connected in power-down.
Several stop jobs start bailing and the shut down takes several minutes.

No possibility to generate or view logs in this state.
Therefore apport-collect was done after reboot to 5.4.0-48 (four eight!)

tags: added: apport-collected
description: updated
Revision history for this message
Lubensius (lubensius) wrote : AlsaInfo.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : CRDA.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : IwConfig.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : Lspci.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : Lspci-vt.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : Lsusb.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : Lsusb-t.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : Lsusb-v.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : ProcEnviron.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : ProcModules.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : PulseList.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : UdevDb.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : WifiSyslog.txt

apport information

Revision history for this message
Lubensius (lubensius) wrote : acpidump.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in ubuntu-mate:
status: New → Confirmed
Norbert (nrbrtx)
Changed in ubuntu-mate:
status: Confirmed → Fix Released
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
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.