Ubuntu 20.04 crashed with ext4 error after waking laptop from sleep
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I wake-up my laptop from sleep (opened laptop lid) and I noticed my WiFi connection was not working and also Bluetooth mouse was not working (in settings it looked Bluetooth was of).
I tried to turn on Bluetooth but nothing happened. Then suddenly black screen appeared with some ext4 messages all over the screen. Then I have hard reset laptop and now it booted normally and works normally.
Now I have executed bellow commands that I have found to collect after similar "crash" appears:
journalctl -b-1 > freshprevboot.txt
lspci -kv > lspci.txt
---
ProblemType: Bug
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-10-23 (435 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: LENOVO 20N4S06V00
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.187.6
Tags: focal
Uname: Linux 5.4.0-58-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-08-14 (138 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 09/21/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2IET92W (1.70 )
dmi.board.
dmi.board.name: 20N4S06V00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad T590
dmi.product.name: 20N4S06V00
dmi.product.sku: LENOVO_
dmi.product.
dmi.sys.vendor: LENOVO
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.
I checked freshprevboot.txt and I see logs from yesterday evening that I haven't stopped any problem.
Now I executed command: today.txt
journalctl -b > journalctl_