Ubuntu 20.04 crashed with ext4 error after waking laptop from sleep

[grofaty]

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-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
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=/boot/vmlinuz-5.4.0-58-generic root=UUID=5ae35a7d-8195-4867-8bb5-49ab3106da83 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-58-generic N/A
 linux-backports-modules-5.4.0-58-generic N/A
 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.asset.tag: Not Available
dmi.board.name: 20N4S06V00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN2IET92W(1.70):bd09/21/2020:svnLENOVO:pn20N4S06V00:pvrThinkPadT590:rvnLENOVO:rn20N4S06V00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T590
dmi.product.name: 20N4S06V00
dmi.product.sku: LENOVO_MT_20N4_BU_Think_FM_ThinkPad T590
dmi.product.version: ThinkPad T590
dmi.sys.vendor: LENOVO
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-04-29T17:08:03.553351

[grofaty (grofaty)]

I checked freshprevboot.txt and I see logs from yesterday evening that I haven't stopped any problem.

Now I executed command:
journalctl -b > journalctl_today.txt

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1909736/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[grofaty (grofaty)]

I collected more logs.

/var/log/dmesg

[grofaty (grofaty)]

/var/log/kern.log

[grofaty (grofaty)]

/var/log/syslog

[lotuspsychje (lotuspsychje)]

You have secureboot enabled, this could possibly influence your hardware

Please try booting ubuntu with secureboot Off and see if you can reproduce this bug

if you do, please change the packagename to 'linux' and run apport-collect 1909736
from a terminal to complete relevant info about your system into your bug.

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

apport information

[grofaty (grofaty)]

This problem has never appeared before and I am using Ubuntu 20.04 for months on this laptop. I don't know how to reproduce this problem. I try to close laptop lid and opened it for several time and everything works like it has thousand times in last few months.

I changed package name to Linux. I have also executed:
apport-collect 1909736
from terminal

[lotuspsychje (lotuspsychje)]

Thank you for changing the right package name and doing apport-collect

can you try booting without secureboot also as a test? if you can reproduce
this with secureboot OFF you could also try booting a previous kernel as a test

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.