Public bug reported:
Some time after updating to Ubuntu 22.04 and Kernel 5.15, Intel Tiger
Lake laptop started getting black screen and EXT4-fs errors 10-20
seconds after resume from sleep. This is reproducible approximately
every other time, i.e. sometimes the resume works normally.
Usually, after resume I can enter GDM password, unlock the desktop and
see running apps, but soon when they start writing to the disk (NVME),
the screen goes blank with a bunch of errors regarding read-only
filesystem, unable to unmount partitions, etc.
Upgrading to Ubuntu 22.10 / Kernel 5.19 does not fix the issue. The same
laptop worked flawlessly before Ubuntu 22.04.
After hard reset and boot, the system works normally.
The logs are not written anywhere besides the screen.
OCR from an photo using Google Lens:
[19449.602615) systemd[9792) home.mount: Failed at step EXEC spawning
/bin/umount: Input/output error
[19449.609995) systemd[1]: Failed unmounting /home.
[19449.932421] systemd[9794): docker.service: Failed at step EXEC spawning
/usr/bin/dockerd: Input/output error
[19449.959791) systemd[1]: Failed to start Docker Application Container Engine.
[19452.164163) systemd[9795): docker.service: Failed at step EXEC spawning
/usr/bin/dockerd: Input/output error
[19452.165445] systemd[1]: Failed to start Docker Application Container Engine.
[19454.397310] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode
#655370: comm systemd: reading directory Iblock o
[19454.397999) EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode
#2: comm systemd: reading directory 1block o
[19454.997891] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode
#655370: comm systemd: reading directory 1block 0
[19454.397949] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode
#2: comm systemd: reading directory Iblock o
[19454.420294] systemd[9797]: docker.service: Failed at step EXEC spawning
/usr/bin/dockerd: Input/output error
119454.421508] systemd[1]: Failed to start Docker Application Container Engine.
[19456.207832 EXT4-fs error (device nvmeon1p5): __ext4_find_entry: 1658: inode
#922214: comm gmain: reading directory Iblock 0
[19456.264664 EXT4-fs error (device nvme0n1p5): ext4_find_entry: 1658: inode
#1187760: comm gmain: reading directory Iblock o
[13456.264765] EXT4-fs error (device Avme0n1p5): ext4_find_entry: 1658: inode
#1187760: comm gmain: reading directory Iblock o
[19456.264816] EXT4-fs error (device nvme0n1p5): ext4_find_entry: 1658: inode
#1187760: comm gmain: reading directory Iblock 0
[13456.467816] EXT4-fs error (device nvme0n1p5): ext4_find_entry: 1658: inode
#1179649: comm thermald: reading directory Iblock 0
[13456.468150] EXT4-fs error (device nvmeon1p5): __ext4_find_entry: 1658: inode
#1179649: comm thermald: reading directory lblock 0
113456.648475] systemd[1]: Failed to start Docker Application Container Engine.
113459.330449] EXT4-fs error (device nvme0n1p6): ext4_find_entry: 1658: inode
#48896417: comm Daemon periodic: reading directory Iblock
[13459.330594] EXT4-fs error (device nvme0n1p6): ext4_find_entry: 1658: inode
#48896417: comm Daemon periodic: reading directory Iblock
[13459.330680] EXT4-fs error (device nvmeon1p6): ext4_find_entry: 1658: inode
#48896417: comm Daemon periodic: reading directory lblock
113459.420371] systemd [9799]: gpu-manager.service: Failed at step EXEC
spawning /usr/bin/gpu-manager: Input/output error
113459.421974] systemd[1]: Failed to start Detect the available GPUS and deal
with any system changes
113459.424728] systemd [9800]: gdm.service: Failed at step EXEC spawning
/usr/share/gdm/generate-config: Input/output error
[13459.426019] systemd[1]: Failed to start GNOME Display Manager.
113459.647301] EXT4-fs error (device nvme0n1p5): ext4_find_entry: 1658: inode
#1315384: comm systemd-logind: reading directory Iblock 0
113459.649171] EXT4-fs error (device nvme0n1p6): ext4_find_entry: 1658: inode
#45744136: comm systemd: reading directory lblock 0
113459.649295] EXT4-fs error (device nvme0n1p6): ext4_find_entry: 1658: inode
#45744134: comm systemd: reading directory lblock 0
113459.649318] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode
#1315384: comm systemd-logind: reading directory lblock 0
113459.649359] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode
#922214: comm systemd: reading directory lblock 0
113459.649472] EXT4-fs error (device nymeon1p5): ext4_find_entry:1658: inode
#655370: comm systemd: reading directory Iblock 0
(13459.649594] EXT4-fs error (device nvmeon1p6): ext4_find_entry: 1658: inode
#45744136: comm systemd: reading directory Iblack 0
[13459.649673] EXT4-fs error (device nymeon1p6): ext4_find_entry: 1658: inode
#45744134: comm systemd: reading directory 1block 0
(13459.6497291 EXT4-fs error (device nymeon1p5); ext4_find_entry: 1658: inode
#922214: comm systemd: reading directory lblock o
[18459.649787] EXT4-fs error (device nymeon1p5); ext4_find_entry:1658: inode
#655370: comm systemd: reading directory lblock 0
[18459.649924] EXT4-fs error (device nymeon1p5):ext4_find_entry: 1658: Inode
#655370: comm NetworkManager: reading directory lblock 0
(13459,650080) EXT4-fs error (device nymeonips); ext4 find_entry:1658: inode
#655365: comm NetworkManager: reading directory lblock 0
(13459.650194] EXT4-fs error (device nymeonips): ext4_find_entry:1658: inode
#2: comm NetworkManager: reading directory lblock 0
[18459.650626] EXT4-fs error (device nymeon1p5); ext4_find_entry:1658: inode
#1315384: comm systemd-logind: reading directory lblock 0
[13460.664307] systemd [9801]: gpu-manager, service: Failed at step EXEC
spawning /usr/bin/gpu-manager: Input/output error
[13460.665714] systemd[1]: Failed to start Detect the available GPUs and deal
with any system changes.
[13460.668564] systemd [9802] gdm, service: Failed at step EXEC spawning
/usr/share/gdm/generate-config: Input/output error
[13460.669827] systemd[1]: Failed to start GNOME Display Manager,
[13461.9285141 systemd [9803) gpu-manager, service: Failed at step EXEC
spawning /usr/bin/gpu-manager: Input/output error
[13461.9300611 systemd[1]: Failed to start Detect the available GPUS and deal
with any system changes.
[13461.932897] systemd [9804]: gdm.service: Failed at step EXEC spawning
/usr/share/gdm/generate-config: Input/output error
ailed to start GNOME Display Manager.
r/bin/gpu-manager: Input/output error
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-21-generic 5.19.0-21.21
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: anton 2702 F.... pipewire
anton 2705 F.... wireplumber
/dev/snd/seq: anton 2702 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 17 22:21:29 2022
InstallationDate: Installed on 2021-04-03 (562 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
MachineType: ASUSTeK COMPUTER INC. ZenBook UX393EA_UX393EA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic
root=UUID=026d3f6d-d78e-4225-b283-76118fb789a8 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.19.0-21-generic N/A
linux-backports-modules-5.19.0-21-generic N/A
linux-firmware 20220923.gitf09bebf3-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to kinetic on 2022-10-16 (1 days ago)
dmi.bios.date: 04/22/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX393EA.312
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX393EA
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:bvnAmericanMegatrendsInternational,LLC.:bvrUX393EA.312:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX393EA_UX393EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX393EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX393EA_UX393EA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993205
Title:
EXT4-fs errors on black screen after resume from sleep
Status in linux package in Ubuntu:
New
Bug description:
Some time after updating to Ubuntu 22.04 and Kernel 5.15, Intel Tiger
Lake laptop started getting black screen and EXT4-fs errors 10-20
seconds after resume from sleep. This is reproducible approximately
every other time, i.e. sometimes the resume works normally.
Usually, after resume I can enter GDM password, unlock the desktop and
see running apps, but soon when they start writing to the disk (NVME),
the screen goes blank with a bunch of errors regarding read-only
filesystem, unable to unmount partitions, etc.
Upgrading to Ubuntu 22.10 / Kernel 5.19 does not fix the issue. The
same laptop worked flawlessly before Ubuntu 22.04.
After hard reset and boot, the system works normally.
The logs are not written anywhere besides the screen.
OCR from an photo using Google Lens:
[19449.602615) systemd[9792) home.mount: Failed at step EXEC spawning
/bin/umount: Input/output error
[19449.609995) systemd[1]: Failed unmounting /home.
[19449.932421] systemd[9794): docker.service: Failed at step EXEC spawning
/usr/bin/dockerd: Input/output error
[19449.959791) systemd[1]: Failed to start Docker Application Container
Engine.
[19452.164163) systemd[9795): docker.service: Failed at step EXEC spawning
/usr/bin/dockerd: Input/output error
[19452.165445] systemd[1]: Failed to start Docker Application Container
Engine.
[19454.397310] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode
#655370: comm systemd: reading directory Iblock o
[19454.397999) EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode
#2: comm systemd: reading directory 1block o
[19454.997891] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode
#655370: comm systemd: reading directory 1block 0
[19454.397949] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode
#2: comm systemd: reading directory Iblock o
[19454.420294] systemd[9797]: docker.service: Failed at step EXEC spawning
/usr/bin/dockerd: Input/output error
119454.421508] systemd[1]: Failed to start Docker Application Container
Engine.
[19456.207832 EXT4-fs error (device nvmeon1p5): __ext4_find_entry: 1658:
inode #922214: comm gmain: reading directory Iblock 0
[19456.264664 EXT4-fs error (device nvme0n1p5): ext4_find_entry: 1658: inode
#1187760: comm gmain: reading directory Iblock o
[13456.264765] EXT4-fs error (device Avme0n1p5): ext4_find_entry: 1658: inode
#1187760: comm gmain: reading directory Iblock o
[19456.264816] EXT4-fs error (device nvme0n1p5): ext4_find_entry: 1658: inode
#1187760: comm gmain: reading directory Iblock 0
[13456.467816] EXT4-fs error (device nvme0n1p5): ext4_find_entry: 1658: inode
#1179649: comm thermald: reading directory Iblock 0
[13456.468150] EXT4-fs error (device nvmeon1p5): __ext4_find_entry: 1658:
inode #1179649: comm thermald: reading directory lblock 0
113456.648475] systemd[1]: Failed to start Docker Application Container
Engine.
113459.330449] EXT4-fs error (device nvme0n1p6): ext4_find_entry: 1658: inode
#48896417: comm Daemon periodic: reading directory Iblock
[13459.330594] EXT4-fs error (device nvme0n1p6): ext4_find_entry: 1658: inode
#48896417: comm Daemon periodic: reading directory Iblock
[13459.330680] EXT4-fs error (device nvmeon1p6): ext4_find_entry: 1658: inode
#48896417: comm Daemon periodic: reading directory lblock
113459.420371] systemd [9799]: gpu-manager.service: Failed at step EXEC
spawning /usr/bin/gpu-manager: Input/output error
113459.421974] systemd[1]: Failed to start Detect the available GPUS and deal
with any system changes
113459.424728] systemd [9800]: gdm.service: Failed at step EXEC spawning
/usr/share/gdm/generate-config: Input/output error
[13459.426019] systemd[1]: Failed to start GNOME Display Manager.
113459.647301] EXT4-fs error (device nvme0n1p5): ext4_find_entry: 1658: inode
#1315384: comm systemd-logind: reading directory Iblock 0
113459.649171] EXT4-fs error (device nvme0n1p6): ext4_find_entry: 1658: inode
#45744136: comm systemd: reading directory lblock 0
113459.649295] EXT4-fs error (device nvme0n1p6): ext4_find_entry: 1658: inode
#45744134: comm systemd: reading directory lblock 0
113459.649318] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode
#1315384: comm systemd-logind: reading directory lblock 0
113459.649359] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode
#922214: comm systemd: reading directory lblock 0
113459.649472] EXT4-fs error (device nymeon1p5): ext4_find_entry:1658: inode
#655370: comm systemd: reading directory Iblock 0
(13459.649594] EXT4-fs error (device nvmeon1p6): ext4_find_entry: 1658: inode
#45744136: comm systemd: reading directory Iblack 0
[13459.649673] EXT4-fs error (device nymeon1p6): ext4_find_entry: 1658: inode
#45744134: comm systemd: reading directory 1block 0
(13459.6497291 EXT4-fs error (device nymeon1p5); ext4_find_entry: 1658: inode
#922214: comm systemd: reading directory lblock o
[18459.649787] EXT4-fs error (device nymeon1p5); ext4_find_entry:1658: inode
#655370: comm systemd: reading directory lblock 0
[18459.649924] EXT4-fs error (device nymeon1p5):ext4_find_entry: 1658: Inode
#655370: comm NetworkManager: reading directory lblock 0
(13459,650080) EXT4-fs error (device nymeonips); ext4 find_entry:1658: inode
#655365: comm NetworkManager: reading directory lblock 0
(13459.650194] EXT4-fs error (device nymeonips): ext4_find_entry:1658: inode
#2: comm NetworkManager: reading directory lblock 0
[18459.650626] EXT4-fs error (device nymeon1p5); ext4_find_entry:1658: inode
#1315384: comm systemd-logind: reading directory lblock 0
[13460.664307] systemd [9801]: gpu-manager, service: Failed at step EXEC
spawning /usr/bin/gpu-manager: Input/output error
[13460.665714] systemd[1]: Failed to start Detect the available GPUs and deal
with any system changes.
[13460.668564] systemd [9802] gdm, service: Failed at step EXEC spawning
/usr/share/gdm/generate-config: Input/output error
[13460.669827] systemd[1]: Failed to start GNOME Display Manager,
[13461.9285141 systemd [9803) gpu-manager, service: Failed at step EXEC
spawning /usr/bin/gpu-manager: Input/output error
[13461.9300611 systemd[1]: Failed to start Detect the available GPUS and deal
with any system changes.
[13461.932897] systemd [9804]: gdm.service: Failed at step EXEC spawning
/usr/share/gdm/generate-config: Input/output error
ailed to start GNOME Display Manager.
r/bin/gpu-manager: Input/output error
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-21-generic 5.19.0-21.21
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: anton 2702 F.... pipewire
anton 2705 F.... wireplumber
/dev/snd/seq: anton 2702 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 17 22:21:29 2022
InstallationDate: Installed on 2021-04-03 (562 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
MachineType: ASUSTeK COMPUTER INC. ZenBook UX393EA_UX393EA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic
root=UUID=026d3f6d-d78e-4225-b283-76118fb789a8 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.19.0-21-generic N/A
linux-backports-modules-5.19.0-21-generic N/A
linux-firmware 20220923.gitf09bebf3-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to kinetic on 2022-10-16 (1 days ago)
dmi.bios.date: 04/22/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX393EA.312
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX393EA
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:bvnAmericanMegatrendsInternational,LLC.:bvrUX393EA.312:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX393EA_UX393EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX393EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX393EA_UX393EA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993205/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
