I have an Asus ExpertBook P5.
I've had Fedora installed on my laptop for the past couple of days. I've found that when the system is suspended, while I can log in after it wakes up, I am unable to open any programs that aren't already running or interact with the file system. Any attempt to do so results in "Input/output error" or "Read-only file system."
A bit of backstory: I installed Ubuntu on it last week, and when I resumed from sleep I would immediately be presented with this screen stating "Authentication Error" before I'd even interacted with it in any way. Clicking kind of just refreshed this state, and sometimes it would lock up altogether. Ctrl+Alt+F3 did absolutely nothing at all.
I ultimately gave up with Ubuntu, which is why I'm currently using Fedora. I've managed to reproduce the issue using the Fedora live image by mounting my actual drive and trying to read/write from it after suspending and resuming.
This is the output from journalctl -x
for the time period in question:
Sep 23 16:45:20 localhost-live systemd[1]: Reached target sleep.target - Sleep.
░░ Subject: A start job for unit sleep.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit sleep.target has finished successfully.
░░
░░ The job identifier is 2906.
Sep 23 16:45:20 localhost-live systemd[1]: Starting systemd-suspend.service - System Suspend...
░░ Subject: A start job for unit systemd-suspend.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-suspend.service has begun execution.
░░
░░ The job identifier is 2905.
Sep 23 16:45:20 localhost-live systemd-sleep[4448]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Sep 23 16:45:20 localhost-live systemd-sleep[4448]: This is not recommended, and might result in unexpected behavior, particularly
Sep 23 16:45:20 localhost-live systemd-sleep[4448]: in suspend-then-hibernate operations or setups with encrypted home directories.
Sep 23 16:45:20 localhost-live systemd-sleep[4448]: Performing sleep operation 'suspend'...
░░ Subject: System sleep state suspend entered
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The system has now entered the suspend sleep state.
Sep 23 16:45:20 localhost-live kernel: PM: suspend entry (s2idle)
Sep 23 16:45:20 localhost-live kernel: Filesystems sync: 0.000 seconds
Sep 23 16:45:22 localhost-live kernel: Freezing user space processes
Sep 23 16:45:22 localhost-live kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Sep 23 16:45:22 localhost-live kernel: OOM killer disabled.
Sep 23 16:45:22 localhost-live kernel: Freezing remaining freezable tasks
Sep 23 16:45:22 localhost-live kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Sep 23 16:45:22 localhost-live kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.0: Asserting Reset
Sep 23 16:45:22 localhost-live kernel: intel-hid INTC107B:00: failed to get button capability
Sep 23 16:45:22 localhost-live kernel: PM: suspend devices took 0.606 seconds
Sep 23 16:45:22 localhost-live kernel: ACPI: EC: interrupt blocked
Sep 23 16:45:22 localhost-live kernel: ACPI: EC: interrupt unblocked
Sep 23 16:45:22 localhost-live kernel: nvme 0000:56:00.0: Unable to change power state from D3cold to D0, device inaccessible
Sep 23 16:45:22 localhost-live kernel: nvme nvme1: Disabling device after reset failure: -19
Sep 23 16:45:22 localhost-live kernel: intel-hid INTC107B:00: failed to get button capability
Sep 23 16:45:22 localhost-live kernel: nvme nvme0: 8/0/0 default/read/poll queues
Sep 23 16:45:22 localhost-live kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.0: DSP1: cirrus/cs35l41-dsp1-spk-prot-10431f63.wmfw: format 3 timestamp 0x64269d09
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.0: DSP1: cirrus/cs35l41-dsp1-spk-prot-10431f63.wmfw: Fri 31 Mar 2023 10:42:49 W. Europe Daylight Time
Sep 23 16:45:22 localhost-live kernel: PM: resume devices took 0.197 seconds
Sep 23 16:45:22 localhost-live kernel: mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops xe_gsc_proxy_component_ops [xe])
Sep 23 16:45:22 localhost-live kernel: OOM killer enabled.
Sep 23 16:45:22 localhost-live systemd-resolved[1315]: Clock change detected. Flushing caches.
Sep 23 16:45:22 localhost-live kernel: Restarting tasks ...
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2 v0.65.0, 2 algorithms
Sep 23 16:45:22 localhost-live kernel: done.
Sep 23 16:45:22 localhost-live kernel: random: crng reseeded on system resumption
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.0: DSP1: cirrus/cs35l41-dsp1-spk-prot-10431f63-l0.bin: v0.65.0
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: C:\ProductSetting\ASUS\Comercial\P5405\Tuning\06032024\P5405_Lchannel_Tuning_Retune_ID.bin
Sep 23 16:45:22 localhost-live udisksd[1421]: Cleaning up mount point /run/media/liveuser/fedora (device 259:8 no longer exists)
Sep 23 16:45:22 localhost-live udisksd[1421]: Error inhibiting: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running (g-io-error-quark, 36)
Sep 23 16:45:22 localhost-live systemd-sleep[4448]: System returned from sleep operation 'suspend'.
░░ Subject: System sleep state suspend left
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The system has now left the suspend sleep state.
Sep 23 16:45:22 localhost-live kernel: PM: suspend exit
Sep 23 16:45:22 localhost-live systemd[1]: systemd-suspend.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit systemd-suspend.service has successfully entered the 'dead' state.
Sep 23 16:45:22 localhost-live systemd[1]: Finished systemd-suspend.service - System Suspend.
░░ Subject: A start job for unit systemd-suspend.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-suspend.service has finished successfully.
░░
░░ The job identifier is 2905.
Sep 23 16:45:22 localhost-live audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 23 16:45:22 localhost-live audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 23 16:45:22 localhost-live systemd[1]: Stopped target sleep.target - Sleep.
░░ Subject: A stop job for unit sleep.target has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit sleep.target has finished.
░░
░░ The job identifier is 2909 and the job result is done.
Sep 23 16:45:22 localhost-live systemd[1]: Reached target suspend.target - Suspend.
░░ Subject: A start job for unit suspend.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit suspend.target has finished successfully.
░░
░░ The job identifier is 2904.
Sep 23 16:45:22 localhost-live systemd-logind[1412]: Operation 'suspend' finished.
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.0: Calibration applied: R0=9836
Sep 23 16:45:22 localhost-live systemd-resolved[1315]: Closing all remaining TCP connections.
Sep 23 16:45:22 localhost-live ModemManager[1528]: <msg> [sleep-monitor-systemd] system is resuming
Sep 23 16:45:22 localhost-live systemd-resolved[1315]: Resetting learnt feature levels on all servers.
Sep 23 16:45:22 localhost-live systemd[1]: run-media-liveuser-fedora.mount: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit run-media-liveuser-fedora.mount has successfully entered the 'dead' state.
Sep 23 16:45:22 localhost-live NetworkManager[1603]: <info> [1758645922.6534] manager: sleep: wake requested (sleeping: yes enabled: yes)
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.1: DSP1: cirrus/cs35l41-dsp1-spk-prot-10431f63.wmfw: format 3 timestamp 0x64269d09
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.1: DSP1: cirrus/cs35l41-dsp1-spk-prot-10431f63.wmfw: Fri 31 Mar 2023 10:42:49 W. Europe Daylight Time
Sep 23 16:45:22 localhost-live NetworkManager[1603]: <info> [1758645922.6546] device (wlo1): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Sep 23 16:45:22 localhost-live systemd[1]: Stopped target suspend.target - Suspend.
░░ Subject: A stop job for unit suspend.target has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit suspend.target has finished.
░░
░░ The job identifier is 2912 and the job result is done.
Sep 23 16:45:22 localhost-live udisksd[1421]: Error probing device: NVMe Identify Namespace command error: Input/output error (g-bd-nvme-error-quark, 1)
Sep 23 16:45:22 localhost-live kernel: nvme nvme1: Identify namespace failed (-5)
Sep 23 16:45:22 localhost-live udisksd[1421]: Partitions found on device '/dev/nvme1n1' but couldn't read partition table signature: Failed to assign the new context to disk '/dev/nvme1n1': Invalid argument
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.1: DSP1: Firmware: 400a4 vendor: 0x2 v0.65.0, 2 algorithms
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.1: DSP1: cirrus/cs35l41-dsp1-spk-prot-10431f63-r0.bin: v0.65.0
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.1: DSP1: spk-prot: C:\ProductSetting\ASUS\Comercial\P5405\Tuning\05312024\P5405_Rchannel_Tuning_ID_0531.bin
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.1: Calibration applied: R0=10157
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.0: Firmware Loaded - Type: spk-prot, Gain: 17
Sep 23 16:45:22 localhost-live kernel: cs35l41-hda spi0-CSC3551:00-cs35l41-hda.1: Firmware Loaded - Type: spk-prot, Gain: 17
Sep 23 16:45:22 localhost-live NetworkManager[1603]: <info> [1758645922.8721] device (wlo1): set-hw-addr: set MAC address to C6:67:1A:F5:91:3C (scanning)
Sep 23 16:45:23 localhost-live kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
Sep 23 16:45:23 localhost-live NetworkManager[1603]: <info> [1758645923.2019] device (p2p-dev-wlo1): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Sep 23 16:45:23 localhost-live NetworkManager[1603]: <info> [1758645923.2024] manager: NetworkManager state is now DISCONNECTED
Sep 23 16:45:23 localhost-live NetworkManager[1603]: <info> [1758645923.2026] agent-manager: agent[38690a1924993416,:1.49/org.gnome.Shell.NetworkAgent/1000]: agent registered
Sep 23 16:45:23 localhost-live NetworkManager[1603]: <info> [1758645923.2412] device (wlo1): supplicant interface state: internal-starting -> disconnected
Sep 23 16:45:23 localhost-live NetworkManager[1603]: <info> [1758645923.2413] device (p2p-dev-wlo1): state change: unavailable -> unmanaged (reason 'unmanaged-link-not-init', managed-type: 'removed')
Sep 23 16:45:23 localhost-live NetworkManager[1603]: <info> [1758645923.2419] Wi-Fi P2P device controlled by interface wlo1 created
Sep 23 16:45:23 localhost-live NetworkManager[1603]: <info> [1758645923.2422] manager: (p2p-dev-wlo1): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Sep 23 16:45:23 localhost-live NetworkManager[1603]: <info> [1758645923.2425] device (p2p-dev-wlo1): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Sep 23 16:45:23 localhost-live NetworkManager[1603]: <info> [1758645923.2430] device (wlo1): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
Sep 23 16:45:23 localhost-live NetworkManager[1603]: <info> [1758645923.2439] device (p2p-dev-wlo1): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
Sep 23 16:45:23 localhost-live gsd-media-keys[2443]: Unable to get default sink
Sep 23 16:45:23 localhost-live gsd-media-keys[2443]: Unable to get default source
Sep 23 16:45:26 localhost-live ModemManager[1528]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin
Sep 23 16:45:27 localhost-live wpa_supplicant[1739]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=JP
Sep 23 16:45:27 localhost-live wpa_supplicant[1739]: p2p-dev-wlo1: Channel list changed: 6 GHz was enabled
Sep 23 16:45:27 localhost-live wpa_supplicant[1739]: wlo1: Channel list changed: 6 GHz was enabled
Sep 23 16:45:27 localhost-live wpa_supplicant[1739]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=JP
Sep 23 16:45:29 localhost-live kernel: BTRFS error (device nvme1n1p3): bdev /dev/nvme1n1p3 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
Sep 23 16:45:29 localhost-live kernel: BTRFS error (device nvme1n1p3): bdev /dev/nvme1n1p3 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0
Sep 23 16:45:29 localhost-live kernel: BTRFS error (device nvme1n1p3): bdev /dev/nvme1n1p3 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0
Sep 23 16:45:29 localhost-live kernel: BTRFS error (device nvme1n1p3): bdev /dev/nvme1n1p3 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0
Sep 23 16:45:29 localhost-live kernel: BTRFS error (device nvme1n1p3): bdev /dev/nvme1n1p3 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0
Sep 23 16:45:29 localhost-live kernel: BTRFS error (device nvme1n1p3): bdev /dev/nvme1n1p3 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0
Sep 23 16:45:29 localhost-live kernel: BTRFS error (device nvme1n1p3): bdev /dev/nvme1n1p3 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0
Sep 23 16:45:29 localhost-live kernel: BTRFS error (device nvme1n1p3): bdev /dev/nvme1n1p3 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0
Sep 23 16:45:29 localhost-live kernel: BTRFS error (device nvme1n1p3): bdev /dev/nvme1n1p3 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0
Sep 23 16:45:29 localhost-live kernel: BTRFS error (device nvme1n1p3): bdev /dev/nvme1n1p3 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0
Sep 23 16:45:29 localhost-live kernel: BTRFS: error (device nvme1n1p3) in btrfs_commit_transaction:2522: errno=-5 IO failure (Error while writing out transaction)
Sep 23 16:45:29 localhost-live kernel: BTRFS info (device nvme1n1p3 state E): forced readonly
Sep 23 16:45:29 localhost-live kernel: BTRFS warning (device nvme1n1p3 state E): Skipping commit of aborted transaction.
Sep 23 16:45:29 localhost-live kernel: BTRFS error (device nvme1n1p3 state EA): Transaction aborted (error -5)
Sep 23 16:45:29 localhost-live kernel: BTRFS: error (device nvme1n1p3 state EA) in cleanup_transaction:2016: errno=-5 IO failure
Sep 23 16:45:38 localhost-live irqbalance[1379]: Cannot change IRQ 172 affinity: Permission denied
Sep 23 16:45:38 localhost-live irqbalance[1379]: IRQ 172 affinity is now unmanaged
Sep 23 16:45:38 localhost-live irqbalance[1379]: Cannot change IRQ 170 affinity: Permission denied
Sep 23 16:45:38 localhost-live irqbalance[1379]: IRQ 170 affinity is now unmanaged
Sep 23 16:45:38 localhost-live irqbalance[1379]: Cannot change IRQ 169 affinity: Permission denied
Sep 23 16:45:38 localhost-live irqbalance[1379]: IRQ 169 affinity is now unmanaged
Sep 23 16:45:38 localhost-live irqbalance[1379]: Cannot change IRQ 167 affinity: Permission denied
Sep 23 16:45:38 localhost-live irqbalance[1379]: IRQ 167 affinity is now unmanaged
Sep 23 16:45:38 localhost-live irqbalance[1379]: Cannot change IRQ 171 affinity: Permission denied
Sep 23 16:45:38 localhost-live irqbalance[1379]: IRQ 171 affinity is now unmanaged
Sep 23 16:45:38 localhost-live irqbalance[1379]: Cannot change IRQ 168 affinity: Permission denied
Sep 23 16:45:38 localhost-live irqbalance[1379]: IRQ 168 affinity is now unmanaged
Sep 23 16:45:38 localhost-live irqbalance[1379]: Cannot change IRQ 166 affinity: Permission denied
Sep 23 16:45:38 localhost-live irqbalance[1379]: IRQ 166 affinity is now unmanaged
The following rows seem like they might be relevant
kernel: nvme 0000:56:00.0: Unable to change power state from D3cold to D0, device inaccessible
kernel: nvme nvme1: Disabling device after reset failure: -19
udisksd[1421]: Error probing device: NVMe Identify Namespace command error: Input/output error (g-bd-nvme-error-quark, 1)
kernel: nvme nvme1: Identify namespace failed (-5)
udisksd[1421]: Partitions found on device '/dev/nvme1n1' but couldn't read partition table signature: Failed to assign the new context to disk '/dev/nvme1n1': Invalid argument
I'm not sure how to fix this, so I've tried some advice I've found online for similar-sounding issues, namely by adding different values to GRUB_CMDLINE_LINUX_DEFAULT
:
nvme_core.default_ps_max_latency_us=5500
pcie_aspm=off
mem_sleep_default=deep
- I confirmed that the mem sleep setting had changed after rebooting, and it had.
I've also downloaded the latest UEFI BIOS firmware from the manufacturer and updated to it.
None of these changes helped (yes, I did actually run the command to regenerate the grub config from my changes /etc/default/grub).
Here is a video of the events that produced the above log from the live environment: https://www.youtube.com/watch?v=vDr4c_nIGBE
How can I resolve this?
Update after resolving the issue:
I was using a Patriot brand Viper VP4000 Mini 2TB M.2 NVMe drive. Thanks to the answer from Marcus, I purchased a WD M.2 NVMe drive instead, and can confirm that simply swapping them and cloning the existing drive's data to the new one solved the issue.