One of two Thinkpad Carbon X1 gen11 does not wake up after suspend. The other ThinkPad x1 gen11, with a different graphics subsystem, works fine with the same configuration.

Following please find a diff between lspci of the two devices. The difference on the freezing machine seems to be the Multimedia controller, the Serial controller, a KIOXIA memory controller, and a modem, as well as the different PCI bridge. In my eyes, those (especially the PCI bridge) seem to be substantial differences.

Anyway, I was wondering what I can do to debug and overcome those freezes.

diff -Nu /tmp/freeze.lspci /tmp/works.lspci
--- /tmp/freeze.lspci	2023-08-16 08:21:10.540213377 +0200
+++ /tmp/works.lspci	2023-08-15 11:02:42.104241104 +0200
@@ -1,7 +1,6 @@
 00:00.0 Host bridge: Intel Corporation Device a708 (rev 01)
 00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04)
 00:04.0 Signal processing controller: Intel Corporation Device a71d (rev 01)
-00:05.0 Multimedia controller: Intel Corporation Device a75d (rev 01)
 00:06.0 PCI bridge: Intel Corporation Device a74d (rev 01)
 00:07.0 PCI bridge: Intel Corporation Device a76e (rev 01)
 00:07.2 PCI bridge: Intel Corporation Device a72f (rev 01)
@@ -10,17 +9,22 @@
 00:0d.0 USB controller: Intel Corporation Device a71e (rev 01)
 00:0d.2 USB controller: Intel Corporation Device a73e (rev 01)
 00:0d.3 USB controller: Intel Corporation Device a76d (rev 01)
-00:12.0 Serial controller: Intel Corporation Alder Lake-P Integrated Sensor Hub (rev 01)
 00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01)
 00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01)
 00:14.3 Network controller: Intel Corporation Device 51f1 (rev 01)
 00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01)
 00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01)
-00:19.0 Serial bus controller: Intel Corporation Alder Lake-P Serial IO I2C Controller #0 (rev 01)
-00:1c.0 PCI bridge: Intel Corporation Device 51b8 (rev 01)
+00:16.3 Serial controller: Intel Corporation Alder Lake AMT SOL Redirection (rev 01)
 00:1f.0 ISA bridge: Intel Corporation Device 519d (rev 01)
 00:1f.3 Audio device: Intel Corporation Device 51ca (rev 01)
 00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01)
 00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01)
-04:00.0 Non-Volatile memory controller: KIOXIA Corporation Device 0010 (rev 01)
-08:00.0 Wireless controller [0d40]: Intel Corporation XMM7560 LTE Advanced Pro Modem (rev 01)
+04:00.0 Non-Volatile memory controller: Sandisk Corp WD PC SN810 / Black SN850 NVMe SSD (rev 01)
+50:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
+51:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
+51:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
+51:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
+51:03.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
+51:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
+52:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10)
+54:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10)
  • mbw@feddit.de
    0·
    1 year ago

    I don’t know if this will be terribly useful for helping with your problem. I had this problem very seldomly and I believe it was related to some X.org problem which was fixed after an update, but it could of course be something entirely different for you.

    As a very first step, I would maybe look if there is anything suspicious going on in the output of sudo journalctl -S . Possible invocations are sudo journalctl -S 2023-08-14, or -S today or -S yesterday, or just sudo journalctl but then there may be a lot of output.

    Oorrr, your distro doesn’t use systemd and this command doesn’t work (in which case you could try dmesg or looking under var/log manually, probably one of the most recently modified logfiles in there.

    Depending on your distro there may be of course dedicated forums where the problem may already be known. The usual advice about updating packages etc. I will assume you have already followed^^

    • bremen15@feddit.deOP
      0·
      1 year ago

      Thanks, I didn’t check the logfiles yet - mostly because I don’t expect it to log anything since it’s dead at that point. But that is speculation on my part, and I will do that.

      These are both fully updated Debian stable systems.

      • mbw@feddit.de
        0·
        1 year ago

        It might be a dud, but at least you’ll know :) In any case, I would consider checking https://forums.debian.net/ as well, in your case. Thinkpad + Debian sounds like a common combination, so the search function there might show some results.