# X1 11th gen se réveille tout seul **URL:** \ **Category:** Support Debian\ **Created:** [Novembre 27, 2023, 11:49 UTC](https://www.debian-fr.org/t/x1-11th-gen-se-reveille-tout-seul/89238 "2023-11-27T11:49:41Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![leatherface](https://www.debian-fr.org/user_avatar/www.debian-fr.org/leatherface/32/2994_2.png) [@leatherface](https://www.debian-fr.org/u/leatherface)\ **Post date:** [Novembre 27, 2023, 11:49 UTC](https://www.debian-fr.org/t/x1-11th-gen-se-reveille-tout-seul/89238/1 "2023-11-27T11:49:41Z")
Bonjour, Je possède un X1 Carbon 11e génération avec Testing installé dessus et KDE. Je le mets tout le temps en suspend-2-ram mais il se réveille tout seul aléatoirement. Je n’arrive pas à savoir pourquoi. Voici quelques sorties de commande. Pouvez-vous m’aider à regarder au bon endroit ? dmesg montrant le réveil: > [166718.692324] Freezing user space processes > [166718.694425] Freezing user space processes completed (elapsed 0.002 seconds) > [166718.694428] OOM killer disabled. > [166718.694428] Freezing remaining freezable tasks > [166718.695834] Freezing remaining freezable tasks completed (elapsed 0.001 seconds) > [166718.695836] printk: Suspending console(s) (use no\_console\_suspend to debug) > [166719.412052] ACPI: EC: interrupt blocked > [167082.209077] ACPI: EC: interrupt unblocked > [167082.438426] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp\_guc\_70.bin version 70.5.1 > [167082.438434] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl\_huc.bin version 7.9.3 > [167082.456093] i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads > [167082.456778] nvme nvme0: Shutdown timeout set to 10 seconds > [167082.457002] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled > [167082.457004] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled > [167082.457563] i915 0000:00:02.0: [drm] GT0: GUC: RC enabled > [167082.459138] nvme nvme0: 12/0/0 default/read/poll queues > [167082.606288] iwlwifi 0000:00:14.3: WFPM\_UMAC\_PD\_NOTIFICATION: 0x1f > [167082.606349] iwlwifi 0000:00:14.3: WFPM\_LMAC2\_PD\_NOTIFICATION: 0x1f > [167082.606412] iwlwifi 0000:00:14.3: WFPM\_AUTH\_KEY\_0: 0x90 > [167082.606475] iwlwifi 0000:00:14.3: CNVI\_SCU\_SEQ\_DATA\_DW9: 0x0 > [167085.426256] mei\_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915\_hdcp\_ops [i915]) > [167085.427170] OOM killer enabled. > [167085.427176] Restarting tasks … > [167085.427310] r8152-cfgselector 4-3.3: USB disconnect, device number 6 > [167085.427366] usb 4-3: USB disconnect, device number 5 > [167085.427371] usb 1-3: USB disconnect, device number 24 > [167085.427384] usb 1-3.4: USB disconnect, device number 25 > [167085.427571] mei\_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915\_pxp\_tee\_component\_ops [i915]) > [167085.428990] usb 1-3.5: USB disconnect, device number 26 > [167085.429823] usb 1-6: USB disconnect, device number 18 > [167085.434797] done. > [167085.434809] random: crng reseeded on system resumption > [167085.560551] usb 1-6: new full-speed USB device number 28 using xhci\_hcd > root@steelers:/sys/devices/platform/thinkpad\_acpi# cat /proc/acpi/wakeup > Device S-state Status Sysfs node > PEG0 S4 \*enabled pci:0000:00:06.0 > PEGP S4 \*disabled pci:0000:04:00.0 > PEG1 S4 \*disabled > PEGP S4 \*disabled > PEG2 S4 \*disabled > PEGP S4 \*disabled > XHCI S3 \*enabled pci:0000:00:14.0 > XDCI S4 \*disabled > HDAS S4 \*disabled pci:0000:00:1f.3 > CNVW S4 \*disabled pci:0000:00:14.3 > RP01 S4 \*enabled pci:0000:00:1c.0 > PXSX S4 \*disabled pci:0000:08:00.0 > RP02 S4 \*disabled > PXSX S4 \*disabled > PXSX S4 \*disabled > RP04 S4 \*disabled > PXSX S4 \*disabled > RP05 S4 \*disabled > PXSX S4 \*disabled > RP06 S4 \*disabled > PXSX S4 \*disabled > RP07 S4 \*disabled > PXSX S4 \*disabled > RP08 S4 \*disabled > PXSX S4 \*disabled > RP09 S4 \*disabled > PXSX S4 \*disabled > RP10 S4 \*disabled > PXSX S4 \*disabled > RP11 S4 \*disabled > PXSX S4 \*disabled > RP12 S4 \*disabled > PXSX S4 \*disabled > RP13 S4 \*disabled > PXSX S4 \*disabled > RP14 S4 \*disabled > PXSX S4 \*disabled > RP15 S4 \*disabled > PXSX S4 \*disabled > RP16 S4 \*disabled > PXSX S4 \*disabled > RP17 S4 \*disabled > PXSX S4 \*disabled > RP18 S4 \*disabled > PXSX S4 \*disabled > RP19 S4 \*disabled > PXSX S4 \*disabled > RP20 S4 \*disabled > PXSX S4 \*disabled > RP21 S4 \*disabled > PXSX S4 \*disabled > RP22 S4 \*disabled > PXSX S4 \*disabled > RP23 S4 \*disabled > PXSX S4 \*disabled > RP24 S4 \*disabled > PXSX S4 \*disabled > TXHC S4 \*enabled pci:0000:00:0d.0 > TDM0 S4 \*enabled pci:0000:00:0d.2 > TDM1 S4 \*enabled pci:0000:00:0d.3 > TRP0 S4 \*enabled pci:0000:00:07.0 > PXSX S4 \*disabled > TRP1 S4 \*disabled > PXSX S4 \*disabled > TRP2 S4 \*enabled pci:0000:00:07.2 > PXSX S4 \*disabled > TRP3 S4 \*disabled > PXSX S4 \*disabled > AWAC S4 \*enabled platform:ACPI000E:00 > SLPB S3 \*enabled platform:PNP0C0E:00 > LID S4 \*enabled platform:PNP0C0D:00 ---
**Author:** ![Clochette](https://www.debian-fr.org/user_avatar/www.debian-fr.org/clochette/32/8757_2.png) [@Clochette](https://www.debian-fr.org/u/Clochette)\ **Post date:** [Novembre 27, 2023, 12:02 UTC](https://www.debian-fr.org/t/x1-11th-gen-se-reveille-tout-seul/89238/2 "2023-11-27T12:02:35Z")
> [@leatherface](#): > > [167085.426256] mei\_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915\_hdcp\_ops [i915]) > [167085.427170] OOM killer enabled. > [167085.427176] Restarting tasks … > [167085.427310] r8152-cfgselector 4-3.3: USB disconnect, device number 6 Tu es sûr d’avoir assez de RAM pour maintenir un suspend to ram ? ---
**Author:** ![leatherface](https://www.debian-fr.org/user_avatar/www.debian-fr.org/leatherface/32/2994_2.png) [@leatherface](https://www.debian-fr.org/u/leatherface)\ **Post date:** [Novembre 27, 2023, 12:16 UTC](https://www.debian-fr.org/t/x1-11th-gen-se-reveille-tout-seul/89238/3 "2023-11-27T12:16:55Z")
Bonjour, Merci pour ta réponse. Le laptop a 32 Go de RAM. Je pense que oui. J’ai toujours fait comme ça même avec mes anciens laptop qui n’en avaient que 16. J’avoue que le oomkiller est étonnant.