kernel panic after restart kb not responding after dropping to CLI

Bug #1903013 reported by pleabargain
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

kernel panic after restart kb not responding after dropping to CLI

$ sudo lspci -vnvn > lspci-vnvn.log
pcilib: sysfs_read_vpd: read failed: Input/output error

$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04

please see video
https://youtu.be/NMxEDLhdeKI

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-52-generic 5.4.0-52.57
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC3: dgd 5920 F.... pulseaudio
 /dev/snd/controlC2: dgd 5920 F.... pulseaudio
 /dev/snd/controlC1: dgd 5920 F.... pulseaudio
 /dev/snd/controlC0: dgd 5920 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 5 10:28:58 2020
HibernationDevice: RESUME=UUID=69f2e3e2-4aa9-4ccb-a32e-0339d1e1a049
InstallationDate: Installed on 2015-08-23 (1900 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-52-generic N/A
 linux-backports-modules-5.4.0-52-generic N/A
 linux-firmware 1.187.3
RfKill:

SourcePackage: linux
StagingDrivers: ashmem_linux
UpgradeStatus: Upgraded to focal on 2020-06-06 (151 days ago)
dmi.bios.date: 07/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V LX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
pleabargain (dennisgdaniels) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you please attach `journalctl -b -1 -k` which may contain the panic log?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Hello

this command:
$ sudo lspci -vnvn > lspci-vnvn.log

should be the following instead, it will put the output into a lspci-vnvn.log file for you to upload:
sudo lspci -vnvn > lspci-vnvn.log

The video does not include the complete error message, can you check if you can found the string "panic" in your /var/log/syslog
If yes, can you attach the file here?

Thanks

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.