# Mise en veille sur trixie?

**URL:** <https://www.debian-fr.org/t/mise-en-veille-sur-trixie/92575>\
**Category:** Support Debian\
**Created:** [Juillet 22, 2026, 9:21 UTC](https://www.debian-fr.org/t/mise-en-veille-sur-trixie/92575 "2026-07-22T09:21:34Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![bellad](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/b/e274bd/32.png) [@bellad](https://www.debian-fr.org/u/bellad)\
**Post date:** [Juillet 22, 2026, 9:21 UTC](https://www.debian-fr.org/t/mise-en-veille-sur-trixie/92575/1 "2026-07-22T09:21:34Z")

</div>

Bonjour , j’ai installé trixie en serveur sur un lenovo thinkcentre , tous les jours je suis obligé de le redemarrer electriquement car je n’ai plus acces  
y a t il une veille ou quelque chose comme ça ?  
merci

---

<div class="post-metadata">

**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:** [Juillet 22, 2026, 11:31 UTC](https://www.debian-fr.org/t/mise-en-veille-sur-trixie/92575/2 "2026-07-22T11:31:38Z")

</div>

que te renvoi ça ? :

```auto
cat /sys/power/state

```

Ou :

```auto
grep -R AllowSuspend /etc/systemd/

```

---

<div class="post-metadata">

**Author:** ![bellad](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/b/e274bd/32.png) [@bellad](https://www.debian-fr.org/u/bellad)\
**Post date:** [Juillet 23, 2026, 8:29 UTC](https://www.debian-fr.org/t/mise-en-veille-sur-trixie/92575/3 "2026-07-23T08:29:06Z")

</div>

> [@Clochette](#):
>
> `grep -R AllowSuspend /etc/systemd/`

merci , voici les réponses

```auto
    root@debthink:~# cat /sys/power/state
    freeze mem disk

```

```auto
    root@debthink:~# grep -R AllowSuspend /etc/systemd/
    /etc/systemd/sleep.conf:#AllowSuspend=yes
    /etc/systemd/sleep.conf:#AllowSuspendThenHibernate=yes

```

dans /etc/systemd/sleep.conf ils ont tous un # devant , que dois je faire ?

---

<div class="post-metadata">

**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:** [Juillet 23, 2026, 8:47 UTC](https://www.debian-fr.org/t/mise-en-veille-sur-trixie/92575/4 "2026-07-23T08:47:50Z")

</div>

Donc d’après le premier retour le noyau accepte la mise en veille/hibernation, d’après le deuxième retour c’est pas gérer par systemd à première vue.

Que renvoie ceci :

```auto
systemctl status sleep.target suspend.target hibernate.target hybrid-sleep.target

```

et

```auto
journalctl -b -1 | grep -Ei "suspend|sleep|freeze|hibernate|PM:"

```

Le matériel est-il toujours alimenté lorsqu’il est inaccessible (led, ventilateur qui tourne, etc) ?

---

<div class="post-metadata">

**Author:** ![bellad](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/b/e274bd/32.png) [@bellad](https://www.debian-fr.org/u/bellad)\
**Post date:** [Juillet 23, 2026, 8:52 UTC](https://www.debian-fr.org/t/mise-en-veille-sur-trixie/92575/5 "2026-07-23T08:52:58Z")

</div>

> [@Clochette](#):
>
> `systemctl status sleep.target suspend.target hibernate.target hybrid-sleep.target`

```
root@debthink:~# systemctl status sleep.target suspend.target hibernate.target hybrid- sleep.target
○ sleep.target - Sleep
 Loaded: loaded (/usr/lib/systemd/system/sleep.target; static)
 Active: inactive (dead)
   Docs: man:systemd.special(7)

○ suspend.target - Suspend
 Loaded: loaded (/usr/lib/systemd/system/suspend.target; static)
 Active: inactive (dead)
   Docs: man:systemd.special(7)

○ hibernate.target - System Hibernation
 Loaded: loaded (/usr/lib/systemd/system/hibernate.target; static)
 Active: inactive (dead)
   Docs: man:systemd.special(7)

○ hybrid-sleep.target - Hybrid Suspend+Hibernate
 Loaded: loaded (/usr/lib/systemd/system/hybrid-sleep.target; static)
 Active: inactive (dead)
   Docs: man:systemd.special(7)

```

et

```auto
    root@debthink:~# journalctl -b -1 | grep -Ei "suspend|sleep|freeze|hibernate|PM:"
    juil. 21 09:02:44 debthink kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
    juil. 21 09:02:44 debthink kernel: PM: hibernation: Registered nosave memory: [mem 0x0005f000-0x0005ffff]
    juil. 21 09:02:44 debthink kernel: PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff]
    juil. 21 09:02:44 debthink kernel: PM: hibernation: Registered nosave memory: [mem 0x94cec000-0x94d34fff]
    juil. 21 09:02:44 debthink kernel: PM: hibernation: Registered nosave memory: [mem 0x97609000-0x97609fff]
    juil. 21 09:02:44 debthink kernel: PM: hibernation: Registered nosave memory: [mem 0x9927b000-0x9bc0efff]
    juil. 21 09:02:44 debthink kernel: PM: hibernation: Registered nosave memory: [mem 0x9bc10000-0xffffffff]
    juil. 21 09:02:44 debthink kernel: ACPI: PM: Registering ACPI NVS region [mem 0x9ae17000-0x9b264fff] (4513792 bytes)
    juil. 21 09:02:44 debthink kernel: ACPI: PM: (supports S0 S3 S4 S5)
    juil. 21 09:02:44 debthink kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
    juil. 21 09:02:44 debthink kernel: PM: genpd: Disabling unused power domains
    juil. 21 09:02:44 debthink kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
    juil. 21 09:02:44 debthink kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
    juil. 21 09:02:44 debthink kernel: PM: Image not found (code -22)
    juil. 21 09:02:44 debthink systemd[1]: systemd-hibernate-clear.service - Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
    juil. 21 09:02:44 debthink kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4
    juil. 21 09:02:44 debthink kernel: ACPI: button: Sleep Button [SLPB]
    juil. 21 09:02:53 debthink systemd-logind[723]: Watching system buttons on /dev/input/event4 (Sleep Button)

```

oui il est toujours alimenté et inaccessible  
désolé pour le formatage du texte ,

---

<div class="post-metadata">

**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:** [Juillet 23, 2026, 11:12 UTC](https://www.debian-fr.org/t/mise-en-veille-sur-trixie/92575/6 "2026-07-23T11:12:03Z")

</div>

Il est pas en veille, mais il a soit un problème réseau soit il est planté, si tu n’as pas de retour clavier/écran il y a de forte chance qu’il soit planté, sinon la carte réseau ce mets peut-être ne veille 😕

```auto
uptime
last -x | head -20
journalctl -b -1 -p err..alert

```

---

<div class="post-metadata">

**Author:** ![bellad](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/b/e274bd/32.png) [@bellad](https://www.debian-fr.org/u/bellad)\
**Post date:** [Juillet 23, 2026, 11:41 UTC](https://www.debian-fr.org/t/mise-en-veille-sur-trixie/92575/7 "2026-07-23T11:41:44Z")

</div>

> [@Clochette](#):
>
> `journalctl -b -1 -p err..alert`

voilà ce qui me sort :  
uptime  
13:40:05 up 3:36, 1 user, load average: 0,04, 0,03, 0,00  
root@debthink:~# last -x | head -20  
root pts/0 192.168.1.11 Thu Jul 23 13:38 - still logged in  
root pts/0 192.168.1.11 Thu Jul 23 10:27 - 11:55 (01:28)  
reboot system boot 6.12.94+deb13-am Thu Jul 23 10:03 - still running  
root tty1 Tue Jul 21 09:03 - crash  
reboot system boot 6.12.94+deb13-am Tue Jul 21 09:02 - crash  
root pts/0 192.168.1.11 Sun Jul 19 19:16 - 19:36 (00:19)  
root pts/1 192.168.1.51 Sun Jul 19 18:12 - 18:19 (00:06)  
root pts/0 192.168.1.11 Sun Jul 19 17:51 - 18:20 (00:29)  
root pts/1 192.168.1.11 Sun Jul 19 14:50 - 15:30 (00:39)  
root pts/0 192.168.1.11 Sun Jul 19 14:49 - 16:30 (01:41)  
root pts/1 192.168.1.11 Sun Jul 19 10:45 - 12:06 (01:21)  
root pts/1 192.168.1.11 Sat Jul 18 17:28 - 17:32 (00:03)  
root pts/0 192.168.1.11 Sat Jul 18 14:28 - 18:07 (03:39)  
reboot system boot 6.12.94+deb13-am Sat Jul 18 14:27 - crash  
reboot system boot 6.12.94+deb13-am Thu Jul 16 18:02 - crash  
root tty1 Thu Jul 16 14:17 - 14:17 (00:00)  
root pts/1 192.168.1.11 Thu Jul 16 14:11 - 14:13 (00:02)  
root pts/0 192.168.1.11 Wed Jul 15 19:07 - 19:40 (00:33)  
root pts/0 192.168.1.11 Wed Jul 15 11:19 - 11:46 (00:26)  
reboot system boot 6.12.94+deb13-am Wed Jul 15 11:16 - 14:17 (1+03:00)  
root@debthink:~# journalctl -b -1 -p err..alert  
juil. 21 09:02:44 debthink kernel: x86/cpu: SGX disabled or unsupported by BIOS.  
juil. 21 09:02:47 debthink kernel: i915 0000:00:02.0: [drm] _ERROR_ CPU pipe A FIFO underrun

---

<div class="post-metadata">

**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:** [Juillet 23, 2026, 11:55 UTC](https://www.debian-fr.org/t/mise-en-veille-sur-trixie/92575/8 "2026-07-23T11:55:53Z")

</div>

J’ai pas plus d’idée, rien de probant là il faudrait creuser plus les messages systèmes avant les éventuels blocage.

---

<div class="post-metadata">

**Author:** ![bellad](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/b/e274bd/32.png) [@bellad](https://www.debian-fr.org/u/bellad)\
**Post date:** [Juillet 23, 2026, 11:58 UTC](https://www.debian-fr.org/t/mise-en-veille-sur-trixie/92575/9 "2026-07-23T11:58:34Z")

</div>

merci quand meme