You are not logged in.
Hi everyone,
Long time Arch user, first time poster. Until now, I've never had an issue that I couldn't find the solution to on the wiki or somewhere else. I have a Dell Latitude 5580 with an Intel Core i3-7100u and no external GPU, and a 512 GB Intel 660P SSD. Until kernel 6.1, literally every hardware feature of this computer worked perfectly, including my LUKS full disk encryption. With kernel 6.1 and every version since it (we're up to 6.1.8 and the problem persists), however, waking up from sleep breaks the OS entirely. This manifests as a broken screen locker, and, if I can get into a second terminal, "Input/output error" as the output of every command. The only way to fix it is to force shut down the computer with the power button. I have tried adding `iommu=soft` to the kernel command line, a commonly recommended fix for this kind of issue, and it makes no difference. I can tell this is an NVMe issue because the journal---which doesn't save, unfortunately---contains errors from the NVMe driver, which result in ext4 errors. The main NVMe error I've seen is (or is very close to) "nvme: unable to change power state from d3cold to d0".
What could the issue be and how could I fix it? So far, as a patch, I've been running upgrades and then forcing the kernel back to version 6.0.9, which does not have this problem. A friend of mine with a Dell XPS 15 from a few years ago doesn't have this issue, could it be a hardware problem in my computer?
Offline
There seems to be one similar report with some attempts at narrowing down the problems in the kernel mailing lists:
https://lore.kernel.org/all/20230104150 … @bhelgaas/
https://bugzilla.kernel.org/show_bug.cgi?id=216877
Last edited by progandy (2023-01-28 22:02:10)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
What about linux-lts? Presumably that works?
Offline
Yes, linux-lts works. The issue is definitely traceable to 6.1, and that mailing list patch looks like the exact issue I'm having. I did some further research, and the error I was seeing comes from the PCIe subsystem, not the NVMe driver itself---it's an error message that gets passed upward to the relevant device driver.
Offline
This is just for reference and to help anybody else with this problem, but I captured the relevant kernel error messages that appear upon waking up while running the non-working kernel:
...
ACPI: PM: Waking up from system sleep state S3
ACPI: EC: interrupt unblocked
iwlwifi 0000:02:00.0: Unable to change power state from D3hot to D0, device inaccessible
nvme 0000:03:00.0: Unable to change power state from D3hot to D0, device inaccessible
ACPI: EC: event unblocked
...
nvme 0000:03:00.0: Unable to change power state from D3cold to D0, device inaccessible
nvme nvme0: Removing after probe failure status: -19
nvme0n1: detected capacity change from 1000215216 to 0
...
Offline
As of today, it looks like the change in question is going to be reverted.
Offline
Looks like it's been fixed (or something's been changed, because the issue is gone) in either 6.1.11 or 6.1.12, I'm not sure which.
Offline
Looks like it's been fixed (or something's been changed, because the issue is gone) in either 6.1.11 or 6.1.12, I'm not sure which.
Offline