Skip to content
Snippets Groups Projects

NVME fails to reset after resume from sleep on "Lenovo Thinkpad P14s Gen 2 AMD" when IOMMU is enabled

    • Closed Issue created by Christos Papadopoulos @Bodanor

    Hi,

    I'm kind of new to the Linux world and I don't know what's going on here. So I've heard that there where patches for Linux when using the s0ix sleep mode (s2idle) but unfortunately, those patches doesn't work on any of the distros I've tested. All of them have failed to resume from sleep (fans starts to spin really fast and black screen with complete freeze) except for one which is OpenSUSE . Now, they are no kernel parameter for it and I don't understand how Opensuse doesn't fail to resume from sleep, like did OpenSUSE applied some patches ? Also, adding amd_iommu=off when booting with all the distros that failed, resolved the issue without problem. (Don't know if it's relevant :smile: )

    As this article says, my computer is affected by this issue and fortunately @superm1 has finally tracked down the issue, but I would like to have an answer to when will I expect to have my computer to not crash when waking up from sleep. By this I mean, which linux kernel version should fix this issue in order for me to avoid tweaking my BIOS and change the sleep mode to S3 ?

    Thank you

    Edited

    Designs

      Child items ...

      2. Activity

      • Christos Papadopoulos changed the description

        changed the description

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Your host distro doesn't really matter. You just need to get latest 5.15.y. If you're having problems with that please share all the stuff in the bug template.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Well, I'm on 5.16-9, so I guess it doesn't work.. So you are telling me that the patches mentioned in the article are already on the kernel 5.15 ?

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Yeah everything is in 5.16.y as well.

          Please share a kernel dmesg and explain more about the circumstances of your failure, certain wake sources, power consumption issues, etc.

          Please make sure you also set your BIOS to "Windows" sleep mode if you didn't already.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Just to be sure as I’m not an advanced Linux user, by kernel 5.15.y you mean I have to compile this particular branch or does that mean that whatever distro that uses the same or later kernel version should include those fixes ?

          I’m truly determined to help the situation as I want this to end and finally fix the only issue I have with Linux and AMD

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Let's please start with what distro you're running then and the kernel they have for it.

          If you're comfortable using Ubuntu I can help you the easiest there, including some binary packages.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Yeah sure let’s do it on Ubuntu for simplicity ! I’ll give you all the infos when I get back home !

          I’ll start by doing a fresh install and disable full disk encryption as I had issue with this when I compiled the kernel 5.15.y, hopefully I can give you all the I fois needed to fix it..

          Edited by Christos Papadopoulos
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Okay so just install Ubuntu 20.04 and then install kernel linux-image-oem-20.04d

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          I’m gonna go with 21.10 because of 20.04 not including the drivers for my wifi card :) hope it’s not over complicating things

          So I install Ubuntu 21.10 and then kernel linux-image-oem-20.04d right ?

          Edited by Christos Papadopoulos
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          20.04d is only in 20.04. it's a special kernel normally for OEM preload use that has tons of backports. It most likely has your WiFi support already bsckported.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Oh okay didn’t know about this package that’s why I was asking

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          https://launchpad.net/ubuntu/+source/linux-meta-oem-5.14 is the metapackage I suggested, and https://launchpad.net/ubuntu/+source/linux-oem-5.14 is the binary packages it will pull in.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Okay, So I've installed Ubuntu 20.04 unecrypted then installed linux-image-oem-20.04d package, performed a reboot and checked to running kernel which is : 5.14.0-1022-oem. Tried to closed the lid and reopened it from sleep but this time I get another issue. When reopen it, I was able to enter my password from the lock screen and get to the desktop, but I noticed that the wifi icon was missing and when clicking on it the system sort of frozed but, after like 5-10 seconds all the icons on the screen where missing so I tried to switch to tty and there was kind of an infinite loop showing this error : systemd-journald[342] : Failed to write entry (22 items, 761 bytes), ignoring : Read-only file system and this error too EXT4-fs error (device nvme0n1p2) : __ext4_find_entry:1611: inode *17695017: comm gmain: reading directory Iblock 0

          IMG_0077.HEIC

          After pressing ctrl + alt + F1. As you can see icons are missing and clicking on the menu on the top right of the screen just shows the errors related to the read-only filesystem on tty. IMG_0080.HEIC IMG_0081.HEIC

          Edit : I also tried the latest one which is 5.14.0.1024.22 but this time I only got as an error : nvme nvme0: Device not ready : aborting reset, CSIS=0x1, which anyway is related to the previous errors

          Edited by Christos Papadopoulos
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Can you please try iommu=pt on the kernel command line?

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          And also please share the dmesg from a test run with this kernel.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          iommu=pt --> Successful resume from sleep without any problems !

          Now, for the dmesg, do you want to just send the whole output of the dmesg command ? And you want a test run with the kernel parameter iommu=pt ?

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Full dmesg, one for each case if you can.

          Edited by Mario Limonciello
        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Well, I want to post the results but the output of dmesg differs from /var/log/dmesg... It seams like dmesg stops writing to /var/log/dmesgafter 5 seconds so I can't recover the dmesg after my system crashes

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Can I instead post the full journalctl when the system crashes ?

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Yeah that would work too.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author
          1. I'll start with the run without the kernel parameter iommu=pt. As the system crashes (and apparently the nvme is not ready based on previous errors I have shown) after opening the lid from sleep, logs can't be written so we don't know what's going on after waking up the computer from sleep but here is the output of journalctl command:

          journcatl_crash

          As we can see, the system detects that we have entered sleep : Feb 19 20:52:07 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Reached target Sleep.

          but then at the end we only see --reboot-- and after that are just logs from a normal kernel startup...

          1. As for the run with the kernel parameter iommu=pt goes, I have successfully saved the dmesg output as well as the journalctl.

          Dmesg :
          dmesg_no_crash

          Entering sleep :
          [ 79.047264] PM: suspend entry (s2idle)

          And for journalctl :
          journactl_no_crash

          Relevant snippets from the journal (do whatever with these as this might be unaccurate. Anyway everything is in the journalctl and dmesg dump) :
          startup and entering sleep :

          Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Stopping User Manager for UID 125...
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped target Main User Target.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a tracker-miner-fs[881]: Received signal:15->'Terminated'
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a tracker-miner-f[881]: Error while sending AddMatch() message: The connection is closed
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a tracker-miner-f[881]: Error while sending AddMatch() message: The connection is closed
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a tracker-miner-f[881]: Error while sending AddMatch() message: The connection is closed
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopping D-Bus User Message Bus...
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopping Virtual filesystem service - Apple File Conduit monitor...
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopping Virtual filesystem service...
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopping Virtual filesystem service - digital camera monitor...
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopping Virtual filesystem service - disk device monitor...
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopping Tracker file system data miner...
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: dbus.service: Killing process 981 (dconf worker) with signal SIGKILL.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: gvfs-udisks2-volume-monitor.service: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped Virtual filesystem service - disk device monitor.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: gvfs-goa-volume-monitor.service: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: gvfs-gphoto2-volume-monitor.service: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped Virtual filesystem service - digital camera monitor.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a tracker-miner-fs[881]: OK
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: run-user-125-gvfs.mount: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[1436]: run-user-125-gvfs.mount: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: run-user-125-gvfs.mount: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: gvfs-mtp-volume-monitor.service: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: gvfs-afc-volume-monitor.service: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped Virtual filesystem service - Apple File Conduit monitor.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: gvfs-daemon.service: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped Virtual filesystem service.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: dbus.service: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped D-Bus User Message Bus.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: tracker-miner-fs.service: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped Tracker file system data miner.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped target Basic System.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped target Paths.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: ubuntu-report.path: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped Pending report trigger for Ubuntu Report.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped target Sockets.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Stopped target Timers.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: dbus.socket: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Closed D-Bus User Message Bus Socket.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: dirmngr.socket: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Closed GnuPG network certificate management daemon.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: gpg-agent-browser.socket: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: gpg-agent-extra.socket: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: gpg-agent-ssh.socket: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: gpg-agent.socket: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Closed GnuPG cryptographic agent and passphrase cache.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: pk-debconf-helper.socket: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Closed debconf communication socket.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: pulseaudio.socket: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Closed Sound System.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: snapd.session-agent.socket: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Closed REST API socket for snapd user session agent.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Reached target Shutdown.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: systemd-exit.service: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Finished Exit the Session.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[871]: Reached target Exit the Session.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: user@125.service: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Stopped User Manager for UID 125.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Stopping User Runtime Directory /run/user/125...
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[1436]: run-user-125.mount: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: run-user-125.mount: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: user-runtime-dir@125.service: Succeeded.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Stopped User Runtime Directory /run/user/125.
Feb 19 20:59:26 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Removed slice User Slice of UID 125.
Feb 19 20:59:41 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: fprintd.service: Succeeded.
Feb 19 20:59:44 liwinux-ThinkPad-P14s-Gen-2a tracker-store[1526]: OK
Feb 19 20:59:44 liwinux-ThinkPad-P14s-Gen-2a systemd[1436]: tracker-store.service: Succeeded.
Feb 19 20:59:44 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: systemd-hostnamed.service: Succeeded.
Feb 19 20:59:44 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: systemd-localed.service: Succeeded.
Feb 19 20:59:53 liwinux-ThinkPad-P14s-Gen-2a geoclue[1155]: Service not used for 60 seconds. Shutting down..
Feb 19 20:59:53 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: geoclue.service: Succeeded.
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a systemd-logind[679]: Lid closed.
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a systemd-logind[679]: Suspending...
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300802.7061] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300802.7063] device (enp2s0f0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300802.7152] device (enp5s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300802.7258] device (wlp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300802.7685] manager: NetworkManager state is now ASLEEP
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a wpa_supplicant[683]: nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: Error adding children to desktop: desktopGrid is undefined
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: Error adding children to desktop: desktopGrid is undefined
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: Error adding children to desktop: desktopGrid is undefined
Feb 19 21:00:02 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: Error adding children to desktop: desktopGrid is undefined
Feb 19 21:00:07 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Reached target Sleep.
Feb 19 21:00:07 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Starting Record successful boot for GRUB...
Feb 19 21:00:07 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Starting Suspend...
Feb 19 21:00:07 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: grub-common.service: Succeeded.
Feb 19 21:00:07 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Finished Record successful boot for GRUB.
Feb 19 21:00:07 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Starting GRUB failed boot detection...
Feb 19 21:00:07 liwinux-ThinkPad-P14s-Gen-2a systemd-sleep[2071]: Suspending system...

          When opening the lid or just waking up the computer :

          Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: PM: suspend entry (s2idle)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: Filesystems sync: 0.002 seconds
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: OOM killer disabled.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: ACPI: EC: interrupt blocked
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: hrtimer: interrupt took 10013982 ns
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0.HKEY.MSCB], AE_NOT_FOUND (20210604/psargs-330)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: 
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: No Local Variables are initialized for Method [_DSM]
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: 
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: Initialized Arguments for Method [_DSM]:  (4 arguments defined for method invocation)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg0:   000000005ff6d52e <Obj>           Buffer(16) 56 0D E0 11 64 CE CE 47
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg1:   00000000ee318337 <Obj>           Integer 0000000000000000
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg2:   000000006e619692 <Obj>           Integer 0000000000000003
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg3:   00000000aca801ed <Obj>           Package 00000000aca801ed
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: 
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: ACPI Error: Aborting method \_SB.PEP._DSM due to previous error (AE_NOT_FOUND) (20210604/psparse-529)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0.HKEY.MSCB], AE_NOT_FOUND (20210604/psargs-330)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: 
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: No Local Variables are initialized for Method [_DSM]
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: 
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: Initialized Arguments for Method [_DSM]:  (4 arguments defined for method invocation)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg0:   000000005ff6d52e <Obj>           Buffer(16) 56 0D E0 11 64 CE CE 47
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg1:   00000000ee318337 <Obj>           Integer 0000000000000000
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg2:   000000006e619692 <Obj>           Integer 0000000000000007
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg3:   00000000aca801ed <Obj>           Package 00000000aca801ed
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: 
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: ACPI Error: Aborting method \_SB.PEP._DSM due to previous error (AE_NOT_FOUND) (20210604/psparse-529)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0.HKEY.MSCB], AE_NOT_FOUND (20210604/psargs-330)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: 
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: No Local Variables are initialized for Method [_DSM]
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: 
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: Initialized Arguments for Method [_DSM]:  (4 arguments defined for method invocation)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg0:   0000000053b3bab2 <Obj>           Buffer(16) 56 0D E0 11 64 CE CE 47
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg1:   0000000074440bd8 <Obj>           Integer 0000000000000000
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg2:   00000000d0f0967a <Obj>           Integer 0000000000000008
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg3:   00000000e1b32950 <Obj>           Package 00000000e1b32950
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: 
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: ACPI Error: Aborting method \_SB.PEP._DSM due to previous error (AE_NOT_FOUND) (20210604/psparse-529)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0.HKEY.MSCB], AE_NOT_FOUND (20210604/psargs-330)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: 
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: No Local Variables are initialized for Method [_DSM]
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: 
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: Initialized Arguments for Method [_DSM]:  (4 arguments defined for method invocation)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg0:   0000000053b3bab2 <Obj>           Buffer(16) 56 0D E0 11 64 CE CE 47
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg1:   0000000074440bd8 <Obj>           Integer 0000000000000000
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg2:   00000000d0f0967a <Obj>           Integer 0000000000000004
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel:   Arg3:   00000000e1b32950 <Obj>           Package 00000000e1b32950
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: 
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: ACPI Error: Aborting method \_SB.PEP._DSM due to previous error (AE_NOT_FOUND) (20210604/psparse-529)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: ACPI: EC: interrupt unblocked
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: pci 0000:00:00.2: PCI INT A: no GSI
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: usb usb1: root hub lost power or was reset
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: usb usb2: root hub lost power or was reset
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: xhci_hcd 0000:06:00.0: Zeroing 64bit base registers, expecting fault
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: [drm] PCIE GART of 1024M enabled.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: [drm] PTB located at 0x000000F400900000
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resuming...
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: dpm has been disabled
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resumed successfully!
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: nvme nvme0: 16/0/0 default/read/poll queues
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: [drm] JPEG decode initialized successfully.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: amdgpu 0000:07:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: usb 1-2: reset high-speed USB device number 2 using xhci_hcd
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: OOM killer enabled.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a systemd-logind[679]: Lid opened.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: grub-initrd-fallback.service: Succeeded.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Finished GRUB failed boot detection.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a systemd-sleep[2071]: System resumed.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: Restarting tasks ... done.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: PM: suspend exit
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a /usr/lib/gdm3/gdm-x-session[1535]: (II) AMDGPU(0): EDID vendor "AUO", prod id 16525
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a /usr/lib/gdm3/gdm-x-session[1535]: (II) AMDGPU(0): Printing DDC gathered Modelines:
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a /usr/lib/gdm3/gdm-x-session[1535]: (II) AMDGPU(0): Modeline "1920x1080"x0.0  141.00  1920 1936 1952 2104  1080 1083 1097 1116 -hsync -vsync (67.0 kHz eP)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: systemd-suspend.service: Succeeded.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Finished Suspend.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Stopped target Sleep.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Reached target Suspend.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Stopped target Suspend.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a systemd-logind[679]: Operation 'sleep' finished.
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300819.6738] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300819.6742] device (enp2s0f0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: psmouse serio1: synaptics: queried max coordinates: x [..5678], y [..4694]
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300819.8330] device (enp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: r8169 0000:02:00.0 enp2s0f0: Link is Down
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1162..]
Feb 19 21:00:19 liwinux-ThinkPad-P14s-Gen-2a kernel: Generic FE-GE Realtek PHY r8169-0-500:00: attached PHY driver (mii_bus:phy_addr=r8169-0-500:00, irq=MAC)
Feb 19 21:00:20 liwinux-ThinkPad-P14s-Gen-2a kernel: r8169 0000:05:00.0 enp5s0: Link is Down
Feb 19 21:00:20 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300820.0493] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Feb 19 21:00:20 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300820.1117] manager: NetworkManager state is now DISCONNECTED
Feb 19 21:00:20 liwinux-ThinkPad-P14s-Gen-2a wpa_supplicant[683]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice dbus_property=P2PDeviceConfig getter failed
Feb 19 21:00:20 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300820.1837] sup-iface[0x55a4163e7210,wlp3s0]: supports 4 scan SSIDs
Feb 19 21:00:20 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300820.1843] device (wlp3s0): supplicant interface state: starting -> ready
Feb 19 21:00:20 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300820.1844] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Feb 19 21:00:21 liwinux-ThinkPad-P14s-Gen-2a dbus-daemon[659]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.93' (uid=1000 pid=1719 comm="/usr/bin/gnome-shell " label="unconfined")
Feb 19 21:00:21 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Starting Fingerprint Authentication Daemon...
Feb 19 21:00:21 liwinux-ThinkPad-P14s-Gen-2a kernel: usb 5-3: reset full-speed USB device number 2 using xhci_hcd
Feb 19 21:00:21 liwinux-ThinkPad-P14s-Gen-2a upowerd[1117]: treating change event as add on /sys/devices/pci0000:00/0000:00:08.1/0000:07:00.4/usb5/5-3
Feb 19 21:00:21 liwinux-ThinkPad-P14s-Gen-2a dbus-daemon[659]: [system] Successfully activated service 'net.reactivated.Fprint'
Feb 19 21:00:21 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Started Fingerprint Authentication Daemon.
Feb 19 21:00:21 liwinux-ThinkPad-P14s-Gen-2a upowerd[1117]: treating change event as add on /sys/devices/pci0000:00/0000:00:08.1/0000:07:00.4/usb5/5-3
Feb 19 21:00:21 liwinux-ThinkPad-P14s-Gen-2a gdm-password][2177]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: No such file or directory
Feb 19 21:00:21 liwinux-ThinkPad-P14s-Gen-2a gdm-fingerprint][2178]: gkr-pam: no password is available for user
Feb 19 21:00:21 liwinux-ThinkPad-P14s-Gen-2a gdm-password][2177]: pam_unix(gdm-password:auth): conversation failed
Feb 19 21:00:21 liwinux-ThinkPad-P14s-Gen-2a gdm-password][2177]: pam_unix(gdm-password:auth): auth could not identify password for [liwinux]
Feb 19 21:00:22 liwinux-ThinkPad-P14s-Gen-2a gdm-password][2191]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: No such file or directory
Feb 19 21:00:22 liwinux-ThinkPad-P14s-Gen-2a gdm-fingerprint][2192]: gkr-pam: no password is available for user
Feb 19 21:00:22 liwinux-ThinkPad-P14s-Gen-2a ModemManager[728]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.2/0000:02:00.0': not supported by any plugin
Feb 19 21:00:22 liwinux-ThinkPad-P14s-Gen-2a ModemManager[728]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.3/0000:03:00.0': not supported by any plugin
Feb 19 21:00:22 liwinux-ThinkPad-P14s-Gen-2a ModemManager[728]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.6/0000:05:00.0': not supported by any plugin
Feb 19 21:00:24 liwinux-ThinkPad-P14s-Gen-2a dbus-daemon[1448]: [session uid=1000 pid=1448] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.43' (uid=1000 pid=1719 comm="/usr/bin/gnome-shell " label="unconfined")
Feb 19 21:00:24 liwinux-ThinkPad-P14s-Gen-2a systemd[1436]: Starting Virtual filesystem metadata service...
Feb 19 21:00:24 liwinux-ThinkPad-P14s-Gen-2a dbus-daemon[1448]: [session uid=1000 pid=1448] Successfully activated service 'org.gtk.vfs.Metadata'
Feb 19 21:00:24 liwinux-ThinkPad-P14s-Gen-2a systemd[1436]: Started Virtual filesystem metadata service.
Feb 19 21:00:24 liwinux-ThinkPad-P14s-Gen-2a gdm-password][2191]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: No such file or directory
Feb 19 21:00:24 liwinux-ThinkPad-P14s-Gen-2a gdm-password][2191]: gkr-pam: unlocked login keyring
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a wpa_supplicant[683]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300825.0488] agent-manager: agent[c8058fc5defc6da5,:1.93/org.gnome.Shell.NetworkAgent/1000]: agent registered
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a dbus-daemon[1448]: [session uid=1000 pid=1448] Activating service name='org.freedesktop.FileManager1' requested by ':1.43' (uid=1000 pid=1719 comm="/usr/bin/gnome-shell " label="unconfined")
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a dbus-daemon[1448]: [session uid=1000 pid=1448] Activating service name='org.gnome.Nautilus' requested by ':1.43' (uid=1000 pid=1719 comm="/usr/bin/gnome-shell " label="unconfined")
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a dbus-daemon[1448]: [session uid=1000 pid=1448] Successfully activated service 'org.gnome.Nautilus'
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a org.gnome.Nautilus[2219]: Failed to register: Unable to acquire bus name 'org.gnome.Nautilus'
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a dbus-daemon[1448]: [session uid=1000 pid=1448] Successfully activated service 'org.freedesktop.FileManager1'
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Feb 19 21:00:25 liwinux-ThinkPad-P14s-Gen-2a gnome-shell[1719]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.2986] policy: auto-activating connection 'PapaKoro-5GHz' (ab82f5af-9abd-4a6a-9247-f95adf4f85fa)
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.2992] device (wlp3s0): Activation: starting connection 'PapaKoro-5GHz' (ab82f5af-9abd-4a6a-9247-f95adf4f85fa)
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.2993] device (wlp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.2994] manager: NetworkManager state is now CONNECTING
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.2996] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.2999] device (wlp3s0): Activation: (wifi) access point 'PapaKoro-5GHz' has security, but secrets are required.
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.2999] device (wlp3s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.3001] sup-iface[0x55a4163e7210,wlp3s0]: wps: type pbc start...
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.3013] device (wlp3s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.3015] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.3018] device (wlp3s0): Activation: (wifi) connection 'PapaKoro-5GHz' has security, and secrets exist.  No new secrets needed.
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.3019] Config: added 'ssid' value 'PapaKoro-5GHz'
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.3019] Config: added 'scan_ssid' value '1'
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.3019] Config: added 'bgscan' value 'simple:30:-70:86400'
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.3019] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.3020] Config: added 'auth_alg' value 'OPEN'
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.3020] Config: added 'psk' value '<hidden>'
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a wpa_supplicant[683]: wlp3s0: SME: Trying to authenticate with 80:78:71:96:70:70 (SSID='PapaKoro-5GHz' freq=5220 MHz)
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a kernel: wlp3s0: authenticate with 80:78:71:96:70:70
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.4822] device (wlp3s0): supplicant interface state: ready -> authenticating
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a kernel: wlp3s0: send auth to 80:78:71:96:70:70 (try 1/3)
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a wpa_supplicant[683]: wlp3s0: Trying to associate with 80:78:71:96:70:70 (SSID='PapaKoro-5GHz' freq=5220 MHz)
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.4841] device (wlp3s0): supplicant interface state: authenticating -> associating
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a kernel: wlp3s0: authenticated
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a kernel: wlp3s0: associate with 80:78:71:96:70:70 (try 1/3)
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a kernel: wlp3s0: RX AssocResp from 80:78:71:96:70:70 (capab=0x1011 status=0 aid=8)
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a kernel: wlp3s0: associated
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a wpa_supplicant[683]: wlp3s0: Associated with 80:78:71:96:70:70
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a wpa_supplicant[683]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a wpa_supplicant[683]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.5183] device (wlp3s0): supplicant interface state: associating -> 4-way handshake
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a kernel: wlp3s0: Limiting TX power to 23 (23 - 0) dBm as advertised by 80:78:71:96:70:70
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a wpa_supplicant[683]: wlp3s0: WPA: Key negotiation completed with 80:78:71:96:70:70 [PTK=CCMP GTK=CCMP]
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a wpa_supplicant[683]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to 80:78:71:96:70:70 completed [id=0 id_str=]
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a wpa_supplicant[683]: bgscan simple: Failed to enable signal strength monitoring
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.7433] device (wlp3s0): supplicant interface state: 4-way handshake -> completed
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.7434] device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "PapaKoro-5GHz"
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.7437] device (wlp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300826.7441] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a avahi-daemon[652]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::dff6:9e8c:f8b:bcc.
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a avahi-daemon[652]: New relevant interface wlp3s0.IPv6 for mDNS.
Feb 19 21:00:26 liwinux-ThinkPad-P14s-Gen-2a avahi-daemon[652]: Registering new address record for fe80::dff6:9e8c:f8b:bcc on wlp3s0.*.
Feb 19 21:00:28 liwinux-ThinkPad-P14s-Gen-2a pkexec[2358]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
Feb 19 21:00:28 liwinux-ThinkPad-P14s-Gen-2a pkexec[2358]: liwinux: Executing command [USER=root] [TTY=unknown] [CWD=/home/liwinux] [COMMAND=/usr/lib/update-notifier/package-system-locked]
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7935] dhcp4 (wlp3s0): option dhcp_lease_time      => '86400'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7936] dhcp4 (wlp3s0): option domain_name_servers  => '212.224.129.90 212.224.129.94'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7936] dhcp4 (wlp3s0): option expiry               => '1645387228'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7936] dhcp4 (wlp3s0): option ip_address           => '192.168.0.19'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7936] dhcp4 (wlp3s0): option next_server          => '192.168.0.1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7936] dhcp4 (wlp3s0): option requested_broadcast_address => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7936] dhcp4 (wlp3s0): option requested_domain_name => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7936] dhcp4 (wlp3s0): option requested_domain_name_servers => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7936] dhcp4 (wlp3s0): option requested_domain_search => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a avahi-daemon[652]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.0.19.
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7937] dhcp4 (wlp3s0): option requested_host_name  => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7937] dhcp4 (wlp3s0): option requested_interface_mtu => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7937] dhcp4 (wlp3s0): option requested_ms_classless_static_routes => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7937] dhcp4 (wlp3s0): option requested_nis_domain => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7937] dhcp4 (wlp3s0): option requested_nis_servers => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7937] dhcp4 (wlp3s0): option requested_ntp_servers => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7937] dhcp4 (wlp3s0): option requested_rfc3442_classless_static_routes => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7937] dhcp4 (wlp3s0): option requested_root_path  => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7937] dhcp4 (wlp3s0): option requested_routers    => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7938] dhcp4 (wlp3s0): option requested_static_routes => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7938] dhcp4 (wlp3s0): option requested_subnet_mask => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7938] dhcp4 (wlp3s0): option requested_time_offset => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7938] dhcp4 (wlp3s0): option requested_wpad       => '1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7938] dhcp4 (wlp3s0): option routers              => '192.168.0.1'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7938] dhcp4 (wlp3s0): option subnet_mask          => '255.255.255.0'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7938] dhcp4 (wlp3s0): state changed unknown -> bound
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a avahi-daemon[652]: New relevant interface wlp3s0.IPv4 for mDNS.
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a avahi-daemon[652]: Registering new address record for 192.168.0.19 on wlp3s0.IPv4.
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.7988] device (wlp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a dbus-daemon[659]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.17' (uid=0 pid=661 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a whoopsie[1408]: [21:00:29] Cannot reach: https://daisy.ubuntu.com
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a dbus-daemon[659]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.8076] device (wlp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.8079] device (wlp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.8083] manager: NetworkManager state is now CONNECTED_LOCAL
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.8094] manager: NetworkManager state is now CONNECTED_SITE
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.8095] policy: set 'PapaKoro-5GHz' (wlp3s0) as default for IPv4 routing and DNS
Feb 19 21:00:29 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300829.8098] device (wlp3s0): Activation: successful, device activated.
Feb 19 21:00:30 liwinux-ThinkPad-P14s-Gen-2a NetworkManager[661]: <info>  [1645300830.0877] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 19 21:00:30 liwinux-ThinkPad-P14s-Gen-2a whoopsie[1408]: [21:00:30] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1
Feb 19 21:00:30 liwinux-ThinkPad-P14s-Gen-2a whoopsie[1408]: [21:00:30] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1
Feb 19 21:00:30 liwinux-ThinkPad-P14s-Gen-2a whoopsie[1408]: [21:00:30] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1
Feb 19 21:00:31 liwinux-ThinkPad-P14s-Gen-2a whoopsie[1408]: [21:00:31] online
Feb 19 21:00:40 liwinux-ThinkPad-P14s-Gen-2a systemd[1]: NetworkManager-dispatcher.service: Succeeded.
        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Just to add up, I've installed the kernel version 5.17-rc-4 and 5.16-10 from canonical just to test but same results, I end up with the same error saying that nvme is not ready

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Thanks for checking those preemptively.

          5.17-rc4 confirms testing all the latest iommu patches.

          For now I suggest since you have a W/A of iommu=pt to use that until we have a solution for this.

          Unfortunately this problem can be any of iommu driver, nvme driver, nvme firmware or even platform firmware so isolating it will be challenging since you can't get logs after resume with the crash.

          Can you please share the nvme drive info? From the nvme command.

          I've got one more idea though. Can you try to boot Ubuntu 22.04 daily build live media from a USB key and issue a suspend from that? If that works then we should be able to get a dmesg or journal log with the traceback from this failure.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          For the moment, I cannot install Ubuntu 22.04 daily build as I am not at home. But I'll do it ASAP !

          As for the nvme command, I'm not sure which sub-command you want from it but here is the output of sudo nvme id-ctrl :

          NVME Identify Controller:
vid       : 0x1344
ssvid     : 0x1344
sn        : 21242FB98ECE        
mn        : Micron MTFDHBA512TDV                    
fr        : 3009P4LN
rab       : 0
ieee      : 00a075
cmic      : 0
mdts      : 9
cntlid    : 0
ver       : 0x10300
rtd3r     : 0x7a120
rtd3e     : 0x1e8480
oaes      : 0
ctratt    : 0x2
rrls      : 0
crdt1     : 0
crdt2     : 0
crdt3     : 0
oacs      : 0x17
acl       : 3
aerl      : 7
frmw      : 0x14
lpa       : 0xb
elpe      : 255
npss      : 4
avscc     : 0x1
apsta     : 0x1
wctemp    : 351
cctemp    : 354
mtfa      : 50
hmpre     : 0
hmmin     : 0
tnvmcap   : 0
unvmcap   : 0
rpmbs     : 0
edstt     : 15
dsto      : 1
fwug      : 0
kas       : 0
hctma     : 0x1
mntmt     : 273
mxtmt     : 353
sanicap   : 0x3
hmminds   : 0
hmmaxd    : 0
nsetidmax : 0
anatt     : 0
anacap    : 0
anagrpmax : 0
nanagrpid : 0
sqes      : 0x66
cqes      : 0x44
maxcmd    : 0
nn        : 1
oncs      : 0x57
fuses     : 0
fna       : 0x4
vwc       : 0x1
awun      : 7
awupf     : 0
nvscc     : 1
nwpc      : 0
acwu      : 0
sgls      : 0
mnan      : 0
subnqn    : nqn.2014-08.org.nvmexpress:1344134421242FB98ECE        Micron MTFDHBA512TDV                    
ioccsz    : 0
iorcsz    : 0
icdoff    : 0
ctrattr   : 0
msdbd     : 0
ps    0 : mp:8.25W operational enlat:0 exlat:0 rrt:0 rrl:0
          rwt:0 rwl:0 idle_power:- active_power:-
ps    1 : mp:3.00W operational enlat:0 exlat:0 rrt:1 rrl:1
          rwt:1 rwl:1 idle_power:- active_power:-
ps    2 : mp:1.90W operational enlat:0 exlat:0 rrt:2 rrl:2
          rwt:2 rwl:2 idle_power:- active_power:-
ps    3 : mp:0.0800W non-operational enlat:10000 exlat:2500 rrt:3 rrl:3
          rwt:3 rwl:3 idle_power:- active_power:-
ps    4 : mp:0.0050W non-operational enlat:12000 exlat:35000 rrt:4 rrl:4
          rwt:4 rwl:4 idle_power:- active_power:-

          Let me now if you need additional infos as I'm able to give them to you for the moment except for the usb key

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          I have some great news ! I can say that your idea was genius as I think we are on a new trail !

          So, I've booted my laptop on a usb running Ubuntu 22.04 with the latest 5.15 kernel, entered sleep mode and surprisingly, it waked up without any issues ! One thing I've noticed and I thing is worth saying before giving you the journalctl dump is that, when i woke up the computer from sleep, I heard a sound similar to when a peripheral is disconnected. So I went I checked out if my nvme drive was still connected and noticed that is wasn't !!

          Before issuing a suspend (my nvme was shown into the file explorer) : Screenshot_from_2022-02-21_16-50-43

          After waking up from suspend (my nvme drive was missing with the peripheral sound I heard) : Screenshot_from_2022-02-21_16-52-43

          One thing to consider too, is that when I've performed the first sleep, the computer took like 5-10 seconds to wake up (I guess because there is an issue with the nvme driver or something that slowed it down). And after sleeping it again (without rebooting), the computer woke up really fast like 1-2 seconds !

          Now, Here is the interesting part. First I'll post the full journalctl and dmesg output, wich is quite big. And after I'll just show you the journalctl and dmesg that are stripped down when I performed the second sleep.

          Full journalctl that issues the first sleep : journalctl_full

          Dmesg that issues the first sleep : dmesg_full

          Here is the stripped down dump, where I issue another sleep (I did that to have a shorter log file and get only where it crashes):

          Journalctl second sleep : journalctl_sleep

          dmesg second sleep : dmesg_sleep

          Let me know if you need further tests, I'll be happy to help !

          Again, greate job on having this idea !

          Edited by Christos Papadopoulos
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          OK, great. So we're on the right track and you have a workaround until we can figure out what's going on.

          One thing to consider too, is that when I've performed the first sleep, the computer took like 5-10 seconds to wake up (I guess because there is an issue with the nvme driver or something that slowed it down). And after sleeping it again (without rebooting), the computer woke up really fast like 1-2 seconds !

          The reason for this is because the nvme driver is essentially removed from the bus. Look closer at the error in your log:

          [  230.704098] nvme nvme0: Device not ready; aborting reset, CSTS=0x1
[  230.704115] nvme nvme0: Removing after probe failure status: -19
[  246.248012] nvme nvme0: Device not ready; aborting reset, CSTS=0x1
[  246.248309] nvme0n1: detected capacity change from 1000215216 to 0

          You're basically hitting this codepath in the kernel that there is a timeout hit while resetting the disk. https://github.com/torvalds/linux/blob/master/drivers/nvme/host/core.c#L2143 fails and then you see this message: https://github.com/torvalds/linux/blob/master/drivers/nvme/host/pci.c#L2929

          I guess next step would be to check whether Lenovo has any updates for this SSD or for your platform firmware (if you haven't already). Having posted the details above should be helpful in case anyone else hits this same issue to find some patterns.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Okay i get it and it’s some progress ! I’ve also fetched for new firmware update on the Lenovo website but nothing seams the need an update right now…

          So now what ? What you should I do and how could it get fix?

          Edited by Christos Papadopoulos
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          So now what ? What you should I do and how could it get fix?

          If there isn't already a firmware update available for your laptop or SSD it will require discussion between Lenovo and AMD firmware teams about this situation to figure out where exactly the problem is. So please don't expect a quick fix.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          I see, well I guess they might not be informed so I should better start talking to them then. Do you now the best way to get in touch with them about it ? And eventually link this tread ?

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          One last thing I just thought of and I can't explain. Do you remember that I said that using openSUSE worked like a charm ? Well, if we assume that it's a firmware issue, how is OpenSUSE able to keep up ? It's just a thought I had :)

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          I see, well I guess they might not be informed so I should better start talking to them then. Do you now the best way to get in touch with them about it ? And eventually link this tread ?

          You can start with their forums I guess.

          One last thing I just thought of and I can't explain. Do you remember that I said that using openSUSE worked like a charm ? Well, if we assume that it's a firmware issue, how is OpenSUSE able to keep up ? It's just a thought I had :smile:

          My knee jerk guess is that you weren't getting into the deepest sleep state. There are a lot of patches that landed in 5.14 and later that enabled s0ix on AMD. What is the kernel version in OpenSUSE?

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          You can start with their forums I guess.

          I sure will do and link this thread so that they already have some infos.

          My knee jerk guess is that you weren't getting into the deepest sleep state. There are a lot of patches that landed in 5.14 and later that enabled s0ix on AMD. What is the kernel version in OpenSUSE?

          That makes sense. I'll probably do a clean install of openSUSE and see the journalctl output and look for something like : kernel: PM: suspend entry (s2idle) (if it's the case then I entered at the same sleep state as ubuntu right ? )

          What is the kernel version in OpenSUSE?

          Kernel Version was 5.16.10 if I remember correctly

          Edited by Christos Papadopoulos
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          That makes sense. I'll probably do a clean install of openSUSE and see the journalctl output and look for something like : kernel: PM: suspend entry (s2idle) (if it's the case then I entered at the same sleep state as ubuntu right ? )

          Maybe do a dual boot? It's nice to go back and forth if we get somewhere rather than re-installing.

          Kernel Version was 5.16.10 if I remember correctly

          That should have the backports from 5.17-rc4 for IOMMU fixes that you checked in the OEM kernel already. Maybe they don't enable the IOMMU by default?

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Maybe do a dual boot? It's nice to go back and forth if we get somewhere rather than re-installing.

          That's what I'm already doing with Windows and Ubuntu (for school purposes) but yeah, I'll maybe have a triple boot with OpenSUSE that's easier

          Maybe they don't enable the IOMMU by default?

          Do you know how I could check that ?

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Do you know how I could check that ?

          Look at the kernel config for:

          CONFIG_AMD_IOMMU
CONFIG_AMD_IOMMU_V2
        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          You were right ! Just installed a VM for Opensuse :

          For amd they both have :

          CONFIG_AMD_IOMMU=y
CONFIG_AMD_IOMMU_V2=m

          BUT they differ when looking for CONFIG_IOMMU :

          OpenSUSE :

          CONFIG_IOMMU_IOVA=y
CONFIG_IOMMU_API=y
CONFIG_IOMMU_SUPPORT=y
CONFIG_IOMMU_IO_PGTABLE=y
# CONFIG_IOMMU_DEBUGFS is not set
# CONFIG_IOMMU_DEFAULT_DMA_STRICT is not set
# CONFIG_IOMMU_DEFAULT_DMA_LAZY is not set
CONFIG_IOMMU_DEFAULT_PASSTHROUGH=y
CONFIG_IOMMU_DMA=y
CONFIG_IOMMU_SVA_LIB=y
CONFIG_IOMMU_HELPER=y
# CONFIG_IOMMU_DEBUG is not set

          Ubuntu :

          CONFIG_IOMMU_IOVA=y
CONFIG_IOMMU_API=y
CONFIG_IOMMU_SUPPORT=y
CONFIG_IOMMU_IO_PGTABLE=y
# CONFIG_IOMMU_DEBUGFS is not set
# CONFIG_IOMMU_DEFAULT_PASSTHROUGH=y
CONFIG_IOMMU_DMA=y
CONFIG_IOMMU_SVA_LIB=y
CONFIG_IOMMU_HELPER=y
# CONFIG_IOMMU_DEBUG is not set
```
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          CONFIG_IOMMU_DEFAULT_PASSTHROUGH=y that explains it. It's the same thing as running iommu=pt on kernel command line.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          I'm kind of relieved now that I know what's going on. I've asked the lenovo forum if it's possible to get in touch with some lenovo firmware developpers. Now we move on to the next chapter I guess. Anyway, many thanks for taking time to try and help me, I learned so much and at least we didn't to this for nothing as we are now on a new trail !

          Edited by Christos Papadopoulos
        • Please register or sign in to reply
      • Mario Limonciello added s0ix label

        added s0ix label

      • Mario Limonciello changed title from Fail to resume from sleep AMD Ryzen 5 PRO 5650U Thinkpad P14s Gen 2 amd to NVME fails to reset after resume from sleep on "Lenovo Thinkpad P14s Gen 2 AMD" when IOMMU is enabled

        changed title from Fail to resume from sleep AMD Ryzen 5 PRO 5650U Thinkpad P14s Gen 2 amd to NVME fails to reset after resume from sleep on "Lenovo Thinkpad P14s Gen 2 AMD" when IOMMU is enabled

      • Christos Papadopoulos
        Christos Papadopoulos @Bodanor ·
        Author

        I'm reopening this thread again since I've spoken to Lenovo about this issue. They told me that even tough I report the issue, they wouldn't do anything about it since firmware software is done in China, So I told them that it was a shame since they chipped this computer with this Nvme drive and even tough I could change manually the drive and replace it with another, that's means I would have to buy a new one and basically throw away a drive that I paid for that is still functional..

        I also saw in the release notes of Linux Kernel 5.17, that there was an issue addressed to the s2idle sleep mode for AMD Ryzen. Even though my issue seams to be a nvme driver failing, do you think that this patch could also help the situation ? Like is it related ?

      • Mario Limonciello
        Mario Limonciello @superm1 ·
        Developer

        they wouldn't do anything about it

        I don't think it's likely to help anything but you can try this patch: https://lore.kernel.org/linux-nvme/20220315072233.GA2288@lst.de/T/#mb9b5782220a32e2c69fe37cf04ae1501b0f48221 If that does actually manage to help we might be able to quirk this in the kernel.

        I also saw in the release notes of Linux Kernel 5.17, that there was an issue addressed to the s2idle sleep mode for AMD Ryzen. Even though my issue seams to be a nvme driver failing, do you think that this patch could also help the situation ? Like is it related ?

        I don't know anything specific to your issue landed, but there is no harm in trying.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Hi get this following error : Applying: nvme-pci: Disable LTR for simple suspend error: drivers/nvme/host/pci.c: does not exist in index

          Maybe I am on the wrong kernel tree ? I'm running kernel 5.16.13 by the way

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          You'll want to run that git am command at root of your checkout. If you don't see drivers/nvme/host/pci.c in that directory then it will fail.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Forget about that, I was trying to apply the patch to my binary kernel.. so I’ll have to download the linux source code, apply the patch to the kernel tree and compile the whole thing right ?

          Edited by Christos Papadopoulos
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Correct. I suggest that you download 5.17-rc8, try it. Then add the patch and try it.

          Edited by Mario Limonciello
        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Well, git am <path to the patch> didn't work since it still couldn't find the pci.c file (really not sure why) , anyway I applied the patch manually by running patch -p1 < <path to the patch> and that one worked. Compiling it right now

        • Please register or sign in to reply
        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Unfortunately, the patch didn't help the situation, that's sad :(

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Okay thanks for confirming. It was a long shot that it was same root cause as that problem.

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Another shot in the dark here. Can you see if you unbind all the PCIe devices from XHCI driver if it helps suspend when IOMMU is enabled? To do this, switch into /sys/bus/pci/drivers/xhci_hcd/ and then run ls. You'll see symlinks for each PCIE BDF. Echo each PCIe BDF into the unbind file. For example:

          cd /sys/bus/pci/drivers/xhci_hcd
echo 0000:63:00.3 | sudo tee unbind
          Edited by Mario Limonciello
        • Matthew Haughton
          Matthew Haughton @snafu109 ·

          No joy on my Gen 1 (kernel 5.15)

          I had three PCIe devices in xhci_hcd, unbound each individually as instructed, but couldn't resume successfully.

          Edited by Matthew Haughton
        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          I can also confirm that my Thinkpad couldn't resume from sleep even after unbinding all the PCIe devices from XHCI driver.

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Ok thanks for checking that. There might be two separate (but related) issues. The same W/A iommu=pt works on both.

          • One where it takes +10s to resume, and one where NVME fails to resume. I've found the unbinding from xhci_hcd appears to help that one.
          • One where the NVME failing to resume appears to be specific to this Micron SSD you have, and it's not tied to FW version as @snafu109 also has it happen but with different FW verison.
        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          That’s definitely a big issue for the ones who buy this laptop with this particular Nvme Drive and just expect it to work out of the box. The problem is that contacting Micron or Lenovo, feels like next to impossible, I keep getting negative responds about this issue. Like « we don’t support linux on this laptop so we can’t help you »… I’m getting out of ideas about that. Maybe could you @snafu109 try on your end to get in touch with either Lenovo or Micron and link them to this thread till they finally decide to do something. I absolutely refuse to give up on a simple issue like this one to ruin my experience with linux and Lenovo at the same time. It’s not like Lenovo is not known to be one of the greatest brand to run linux perfectly with nearly few issues!

          Edited by Christos Papadopoulos
        • Please register or sign in to reply
        • Matthew Haughton
          Matthew Haughton @snafu109 ·

          I can confirm this issue on a Gen 1 variant of this machine (Lenovo ThinkPad P14s Gen 1 AMD), which also uses Micron MTFDHBA512TDV, though mine has firmware version 3010P4LN. BIOS is up to date, and the Lenovo SSD firmware updater has no available updates for the SSD.

          I cannot resume with s0ix on Ubuntu 22.04 dev branch (ISO downloaded around March 14), which uses kernel 5.15, with the same error reported above:

          nvme nvme0: Device not ready; aborting reset, CSTS=0x1
nvme nvme0: Removing after probe failure status: -19

          It works with iommu=pt at the kernel command line.

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          Finally someone who has the same drive and the same issue, I really thought I was the only one haha

          As for the firmware version I don’t know how you got your hands into this one but I searched everywhere and I couldn’t find any firmware file for this drive, even on Lenovo’s website they didn’t list any update

          Edit : Is your thinkpad p14s Gen 1 certified for linux ?

          Edited by Christos Papadopoulos
        • Matthew Haughton
          Matthew Haughton @snafu109 ·

          It came with that firmware from the factory as far as I know - I've run Lenovo's SSD firmware updater a couple of times but it never had updates for the drive.

          It appears to be certified: https://ubuntu.com/certified/202006-27980 but the certified system used a SanDisk NVMe drive. It would be certified for S3 sleep only though, not s0ix: https://forums.lenovo.com/t5/Other-Linux-Discussions/Linux-S0ix-support-on-AMD-platforms/m-p/5098254

          AMD have delivered S0ix support upstream in the 5.14 kernel, but it is not officially supported in the G1 and G2 platforms. On these platforms Lenovo is still supporting and recommend using S3 - we have not certified or internally tested S0i support

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          That's odd, I can't find your specific firmware update.

          As for the certification, there is no mention for my specific Thinkpad(they only mentioned the Intel ones). As for the Lenovo website, they say that my Thinkpad is certified for RHEL 5.8, but they surely used another nvme drive

        • Please register or sign in to reply
        • Matthew Haughton
          Matthew Haughton @snafu109 ·

          I'm not sure if this is relevant, but in case it was missed in the earlier dmesg output provided by Christos, I also noticed these lines in my dmesg output (using kernel 5.15):

          # dmesg|grep 0000:00:00.2
[    0.379218] pci 0000:00:00.2: [1022:1631] type 00 class 0x080600
[    0.410832] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
[    0.410899] pci 0000:00:00.2: can't derive routing for PCI INT A
[    0.410899] pci 0000:00:00.2: PCI INT A: not connected
[    0.413132] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
          # lspci -s 0000:00:00.2
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU

          And when I apply iommu=pt and can resume, I see some errors like "pci 0000:00:00.2: PCI INT A no GSI" after resuming.

          Edited by Matthew Haughton
        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          That's a good catch, as said earlier, I can also resume with iommu=pt as a kernel parameter Wich is the workaround for the moment, but I never compared the logs with this parameter on/off. Maybe that's hiding something relevant. Unfortunately, I'm not this advanced and I can't really help, I can only provide logs and output tests :d

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          And when I apply iommu=pt and can resume, I see some errors like "pci 0000:00:00.2: PCI INT A no GSI" after resuming.

          I double checked on a system that has the symptom of longer (but successful) resume and see no notable difference from the default kernel messages w/ iommu in passthrough versus enabled. If you want to double check on your end you can run dmesg -t to filter out timestamps.

        • Please register or sign in to reply
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Something that recently came to light is this drive you guys both have failures with is a OPAL SSD.

          Do you happen to have an NVME password enabled in firmware setup? If so and you remove it; does the behavior change at all?

        • Matthew Haughton
          Matthew Haughton @snafu109 ·

          Yes, the order receipt says it's an Opal 2 drive. I've never set a password on it in the UEFI setup though - I just checked to make sure, and the option "Hard Disk1 Password" is set to "Disabled".

        • Christos Papadopoulos
          Christos Papadopoulos @Bodanor ·
          Author

          It says that it’s an opal 2 drive too. And I’ve never set any password on it. I hoped that the latest bios update (1.15) would fix something but they only mentioned that they fixed batteries drain for the S3 sleep mode on linux which is great but not the main concern here unfortunately..

        • Please register or sign in to reply
      • Mario Limonciello mentioned in issue #1689 (closed)

        mentioned in issue #1689 (closed)

      • Mario Limonciello
        Mario Limonciello @superm1 ·
        Developer

        OK from the internal investigation at AMD - both #1910 (closed) and #1689 (closed) are the same root cause. The Lenovo firmware needs to be fixed to avoid it.

        There are a few ways that Lenovo can address it, and that will be up to them which way they choose to do it. Their firmware team can discuss details with AMD if necessary. From an end user perspective the best workaround until Lenovo has issued a fix will remain to use iommu=pt on the kernel command line.

        As such, I'm closing this issue in AMD's bug tracker.

      • Mario Limonciello closed

        closed

      • Ghost User mentioned in commit nouveau@455cd867

        mentioned in commit nouveau@455cd867

        • Christophe Declercq
          Christophe Declercq @declercq-c ·

          Hi, It seems I have a similar issue with my laptop Lenovo Thinkpad X13 Gen 2 with a SSD 1To OPAL 2. After trying ubuntu 22.04 LTS with an USB live, as I tried to install it replacing windows 11, there was many I/O errors and crash install. Now I can only boot with Ubuntu live. When I try to install, it says not enough memory (doesn't see SSD). Opening a term, I can read syslog and find same errors :

          Aug 25 07:09:47 ubuntu kernel: [ 1.397039] nvme 0000:04:00.0: platform quirk: setting simple suspend Aug 25 07:09:47 ubuntu kernel: [ 1.397150] nvme nvme0: pci function 0000:04:00.0 Aug 25 07:09:47 ubuntu kernel: [ 1.402569] nvme nvme0: Identify Controller failed (17089) Aug 25 07:09:47 ubuntu kernel: [ 1.402644] nvme nvme0: Removing after probe failure status: -5

          No SSD with df or lsblk Does your idea be usefull in this case : iommu = pt ?

          I never patch kernel so I don't know where to write this option on my USB live or in file system.

          Thanks in advance, Christophe Declercq

          PS : Sorry for my poor english...

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Your issue at least looks different. I suspect it's a hardware failure from the above desription.

        • Please register or sign in to reply
      • Loading
      • Loading
      • Loading
      • Loading
      • Loading
      • Loading
      • Loading
      • Loading
      • Loading
      • Loading
      Please register or sign in to reply