Ne se met plus en veille depuis dernière MAJ

Le
Damien TOURDE
Bonjour,

Je suis en testing, depuis la dernière MAJ que j'ai faite (assez
importante avec gnome->3.16, linux-image -> 4.0), mon laptop ne se met
plus en veille à chaque fois.

Lorsque je souhaite le mettre en veille, au vu des clignotements
d'écran, il a l'air de se mettre en veille 3 fois pour finalement re=
ster
allumé.

Lorsque je baisse l'écran, il n'a pas l'air de détecter à =
chaque coup
que l'écran est baissé.

Voici le résultat de dmesg après une tentative de mise en veill=
e, via le
menu de Gnome 3 (le fait de baisser l'écran n'a rien déclenchÃ=
© ce coup-ci).
Les messages du type "pciehp 0000:00:01.0:pcie04: Device 0000:01:00.0
already exists at 0000:01:00, cannot hot-add" ont toujours étés=
présents
à la sortie de la veille (suspend to ram) sans que je prenne le temp=
s de
savoir à quoi ils étaient dus, et ils n'ont jamais gêné=
s la mise en
veille (et le maintient dans cet état) jusqu'à présent.

Puis le dmesg d'une mise en veille réussie (peu après un redÃ=
©marrage).

Une petite idée ?


[104635.283917] sky2 0000:0c:00.0 eth0: disabling interface
[104635.288529] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[104635.312316] wlan0: deauthenticating from 14:0c:76:6f:58:9c by local
choice (Reason: 3=DEAUTH_LEAVING)
[104635.326882] cfg80211: Calling CRDA to update world regulatory domain
[104635.372660] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[104635.377651] cfg80211: World regulatory domain updated:
[104635.377655] cfg80211: DFS Master region: unset
[104635.377657] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp), (dfs_cac_time)
[104635.377659] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz),
(N/A, 2000 mBm), (N/A)
[104635.377661] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm), (N/A)
[104635.377663] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz),
(N/A, 2000 mBm), (N/A)
[104635.377666] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz,
160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[104635.377668] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz,
160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[104635.377670] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz),
(N/A, 2000 mBm), (0 s)
[104635.377672] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz),
(N/A, 2000 mBm), (N/A)
[104635.377675] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz),
(N/A, 0 mBm), (N/A)
[104640.340787] PM: Syncing filesystems done.
[104640.360538] PM: Preparing system for mem sleep
[104642.337698] Freezing user space processes (elapsed 0.001
seconds) done.
[104642.339611] Freezing remaining freezable tasks (elapsed 0.001
seconds) done.
[104642.340913] PM: Entering mem sleep
[104642.341065] Suspending console(s) (use no_console_suspend to debug)
[104642.342163] sd 2:0:0:0: [sda] Synchronizing SCSI cache
[104642.342489] sd 2:0:0:0: [sda] Stopping disk
[104642.629451] PM: suspend of devices complete after 288.020 msecs
[104642.629945] PM: late suspend of devices complete after 0.488 msecs
[104642.630832] ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI
[104642.630873] uhci_hcd 0000:00:1d.2: System wakeup enabled by ACPI
[104642.630927] uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI
[104642.630955] uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI
[104642.631249] ehci-pci 0000:00:1a.7: System wakeup enabled by ACPI
[104642.631278] uhci_hcd 0000:00:1a.1: System wakeup enabled by ACPI
[104642.631342] uhci_hcd 0000:00:1a.0: System wakeup enabled by ACPI
[104642.784146] PM: noirq suspend of devices complete after 154.196 msecs=

[104642.784514] ACPI: Preparing to enter system sleep state S3
[104642.848087] PM: Saving platform NVS memory
[104642.850486] Disabling non-boot CPUs
[104642.851783] kvm: disabling virtualization on CPU1
[104642.851804] smpboot: CPU 1 is now offline
[104642.864191] ACPI: Low-level resume complete
[104642.864191] PM: Restoring platform NVS memory
[104642.864191] Enabling non-boot CPUs
[104642.864191] x86: Booting SMP configuration:
[104642.864191] smpboot: Booting Node 0 Processor 1 APIC 0x1
[104642.851795] kvm: enabling virtualization on CPU1
[104642.900564] CPU1 is up
[104642.902887] ACPI: Waking up from system sleep state S3
[104643.204225] uhci_hcd 0000:00:1a.0: System wakeup disabled by ACPI
[104643.204289] uhci_hcd 0000:00:1a.1: System wakeup disabled by ACPI
[104643.204761] uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI
[104643.204787] uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI
[104643.204842] uhci_hcd 0000:00:1d.2: System wakeup disabled by ACPI
[104643.220186] ehci-pci 0000:00:1a.7: System wakeup disabled by ACPI
[104643.220846] ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI
[104643.360828] PM: noirq resume of devices complete after 156.772 msecs
[104643.360879] pciehp 0000:00:01.0:pcie04: Card present on Slot(1)
[104643.360897] pciehp 0000:00:1c.5:pcie04: Card present on Slot(5)
[104643.360903] pciehp 0000:00:1c.5:pcie04: slot(5): Link Up event
[104643.360918] pciehp 0000:00:1c.4:pcie04: Card present on Slot(4)
[104643.360924] pciehp 0000:00:1c.4:pcie04: slot(4): Link Up event
[104643.360938] pciehp 0000:00:1c.5:pcie04: Link Up event ignored on
slot(5): already powering on
[104643.360943] pciehp 0000:00:1c.4:pcie04: Link Up event ignored on
slot(4): already powering on
[104643.361089] PM: early resume of devices complete after 0.225 msecs
[104643.361182] usb usb1: root hub lost power or was reset
[104643.361247] usb usb2: root hub lost power or was reset
[104643.361428] usb usb3: root hub lost power or was reset
[104643.361430] usb usb4: root hub lost power or was reset
[104643.361511] usb usb5: root hub lost power or was reset
[104643.364211] pciehp 0000:00:1c.0:pcie04: Timeout on hotplug command
0x1038 (issued 5463088 msec ago)
[104643.364270] pciehp 0000:00:1c.2:pcie04: Timeout on hotplug command
0x1038 (issued 5463088 msec ago)
[104643.364287] pciehp 0000:00:1c.4:pcie04: Timeout on hotplug command
0x1038 (issued 5463088 msec ago)
[104643.364295] pciehp 0000:00:1c.5:pcie04: Timeout on hotplug command
0x1038 (issued 5463088 msec ago)
[104643.367443] sd 2:0:0:0: [sda] Starting disk
[104643.464097] pciehp 0000:00:1c.5:pcie04: Device 0000:0c:00.0 already
exists at 0000:0c:00, cannot hot-add
[104643.464100] pciehp 0000:00:1c.5:pcie04: Cannot add device at 0000:0c:=
00
[104643.464320] pciehp 0000:00:1c.4:pcie04: Device 0000:0b:00.0 already
exists at 0000:0b:00, cannot hot-add
[104643.464322] pciehp 0000:00:1c.4:pcie04: Cannot add device at 0000:0b:=
00
[104643.546369] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)
filtered out
[104643.546371] ata1.00: ACPI cmd ef/03:44:00:00:00:a0 (SET FEATURES)
filtered out
[104643.546548] ata3.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)
filtered out
[104643.546550] ata3.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES)
filtered out
[104643.546690] ata3.00: supports DRM functions and may not be fully
accessible
[104643.552451] ata3.00: supports DRM functions and may not be fully
accessible
[104643.552789] ata3.00: configured for UDMA/133
[104643.560537] ata1.00: configured for UDMA/66
[104643.568142] pciehp 0000:00:1c.5:pcie04: Device 0000:0c:00.0 already
exists at 0000:0c:00, cannot hot-add
[104643.568145] pciehp 0000:00:1c.5:pcie04: Cannot add device at 0000:0c:=
00
[104643.568353] pciehp 0000:00:1c.4:pcie04: Device 0000:0b:00.0 already
exists at 0000:0b:00, cannot hot-add
[104643.568354] pciehp 0000:00:1c.4:pcie04: Cannot add device at 0000:0b:=
00
[104643.692203] usb 1-1: reset full-speed USB device number 2 using uhci_=
hcd
[104643.840060] usb 5-1: reset low-speed USB device number 2 using uhci_h=
cd
[104643.916146] firewire_core 0000:0d:03.0: rediscovered device fw0
[104644.125693] usb 1-1.1: reset full-speed USB device number 3 using
uhci_hcd
[104644.240118] usb 5-2: reset full-speed USB device number 4 using uhci_=
hcd
[104644.468121] pciehp 0000:00:01.0:pcie04: Device 0000:01:00.0 already
exists at 0000:01:00, cannot hot-add
[104644.468125] pciehp 0000:00:01.0:pcie04: Cannot add device at 0000:01:=
00
[104645.576163] pciehp 0000:00:01.0:pcie04: Device 0000:01:00.0 already
exists at 0000:01:00, cannot hot-add
[104645.576172] pciehp 0000:00:01.0:pcie04: Cannot add device at 0000:01:=
00
[104645.576262] rtc_cmos 00:03: System wakeup disabled by ACPI
[104646.352724] PM: resume of devices complete after 2991.628 msecs
[104646.352908] input: bcm5974 as
/devices/pci0000:00/0000:00:1d.2/usb5/5-2/5-2:1.2/input/input30
[104646.355537] PM: Finishing wakeup.
[104646.355539] Restarting tasks done.
[104646.437214] sky2 0000:0c:00.0 eth0: enabling interface
[104646.620263] b43-phy0: Loading firmware version 666.2 (2011-02-23
01:15:07)
[104654.503194] wlan0: authenticate with 14:0c:76:6f:58:9c
[104654.520499] wlan0: send auth to 14:0c:76:6f:58:9c (try 1/3)
[104654.522573] wlan0: authenticated
[104654.524386] wlan0: associate with 14:0c:76:6f:58:9c (try 1/3)
[104654.527680] wlan0: RX AssocResp from 14:0c:76:6f:58:9c (capab=0x411=

status=0 aid=2)
[104654.528059] wlan0: associated


En revanche, lorsqu'il se met en veille "correctement", le dmesg donne Ã=
§a :

[ 7396.806113] sky2 0000:0c:00.0 eth0: disabling interface
[ 7396.813068] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7396.837859] wlan0: deauthenticating from 14:0c:76:6f:58:9c by local
choice (Reason: 3=DEAUTH_LEAVING)
[ 7396.892916] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 7396.894531] cfg80211: Calling CRDA to update world regulatory domain
[ 7396.909047] cfg80211: World regulatory domain updated:
[ 7396.909052] cfg80211: DFS Master region: unset
[ 7396.909054] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp), (dfs_cac_time)
[ 7396.909057] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz),
(N/A, 2000 mBm), (N/A)
[ 7396.909059] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm), (N/A)
[ 7396.909061] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz),
(N/A, 2000 mBm), (N/A)
[ 7396.909063] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz,
160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 7396.909066] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz,
160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 7396.909068] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz),
(N/A, 2000 mBm), (0 s)
[ 7396.909070] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz),
(N/A, 2000 mBm), (N/A)
[ 7396.909072] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz),
(N/A, 0 mBm), (N/A)
[ 7402.043318] PM: Syncing filesystems done.
[ 7402.066653] PM: Preparing system for mem sleep
[ 7404.527102] Freezing user space processes (elapsed 0.001 seconds)
done.
[ 7404.528837] Freezing remaining freezable tasks (elapsed 0.001
seconds) done.
[ 7404.530000] PM: Entering mem sleep
[ 7404.530128] Suspending console(s) (use no_console_suspend to debug)
[ 7404.531393] sd 2:0:0:0: [sda] Synchronizing SCSI cache
[ 7404.531710] sd 2:0:0:0: [sda] Stopping disk
[ 7405.060287] PM: suspend of devices complete after 529.819 msecs
[ 7405.060779] PM: late suspend of devices complete after 0.486 msecs
[ 7405.061553] ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI
[ 7405.061702] uhci_hcd 0000:00:1d.2: System wakeup enabled by ACPI
[ 7405.061724] uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI
[ 7405.061785] uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI
[ 7405.062048] ehci-pci 0000:00:1a.7: System wakeup enabled by ACPI
[ 7405.062154] uhci_hcd 0000:00:1a.1: System wakeup enabled by ACPI
[ 7405.062172] uhci_hcd 0000:00:1a.0: System wakeup enabled by ACPI
[ 7405.216131] PM: noirq suspend of devices complete after 155.347 msecs
[ 7405.216498] ACPI: Preparing to enter system sleep state S3
[ 7407.132040] PM: Saving platform NVS memory
[ 7407.134358] Disabling non-boot CPUs
[ 7407.135725] kvm: disabling virtualization on CPU1
[ 7407.135741] smpboot: CPU 1 is now offline
[ 7407.156194] ACPI: Low-level resume complete
[ 7407.156194] PM: Restoring platform NVS memory
[ 7407.156194] Enabling non-boot CPUs
[ 7407.156194] x86: Booting SMP configuration:
[ 7407.156194] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 7407.135733] kvm: enabling virtualization on CPU1
[ 7407.188557] CPU1 is up
[ 7407.190820] ACPI: Waking up from system sleep state S3
[ 7407.524243] uhci_hcd 0000:00:1a.0: System wakeup disabled by ACPI
[ 7407.524338] uhci_hcd 0000:00:1a.1: System wakeup disabled by ACPI
[ 7407.524904] uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI
[ 7407.524922] uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI
[ 7407.525002] uhci_hcd 0000:00:1d.2: System wakeup disabled by ACPI
[ 7407.540189] ehci-pci 0000:00:1a.7: System wakeup disabled by ACPI
[ 7407.540868] ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI
[ 7407.680727] PM: noirq resume of devices complete after 156.673 msecs
[ 7407.680768] pciehp 0000:00:01.0:pcie04: Card present on Slot(1)
[ 7407.680786] pciehp 0000:00:1c.5:pcie04: Card present on Slot(5)
[ 7407.680791] pciehp 0000:00:1c.5:pcie04: slot(5): Link Up event
[ 7407.680807] pciehp 0000:00:1c.4:pcie04: Card present on Slot(4)
[ 7407.680812] pciehp 0000:00:1c.4:pcie04: slot(4): Link Up event
[ 7407.680884] pciehp 0000:00:1c.5:pcie04: Link Up event ignored on
slot(5): already powering on
[ 7407.680889] pciehp 0000:00:1c.4:pcie04: Link Up event ignored on
slot(4): already powering on
[ 7407.680913] PM: early resume of devices complete after 0.155 msecs
[ 7407.680992] usb usb2: root hub lost power or was reset
[ 7407.681064] usb usb3: root hub lost power or was reset
[ 7407.681255] usb usb4: root hub lost power or was reset
[ 7407.681267] usb usb5: root hub lost power or was reset
[ 7407.681317] usb usb6: root hub lost power or was reset
[ 7407.684085] pciehp 0000:00:1c.5:pcie04: Timeout on hotplug command
0x1038 (issued 88048 msec ago)
[ 7407.684096] pciehp 0000:00:1c.0:pcie04: Timeout on hotplug command
0x1038 (issued 88048 msec ago)
[ 7407.684122] pciehp 0000:00:1c.2:pcie04: Timeout on hotplug command
0x1038 (issued 88048 msec ago)
[ 7407.684134] sd 2:0:0:0: [sda] Starting disk
[ 7407.684148] pciehp 0000:00:1c.4:pcie04: Timeout on hotplug command
0x1038 (issued 88048 msec ago)
[ 7407.784151] pciehp 0000:00:1c.5:pcie04: Device 0000:0c:00.0 already
exists at 0000:0c:00, cannot hot-add
[ 7407.784152] pciehp 0000:00:1c.5:pcie04: Cannot add device at 0000:0c:0=

0
[ 7407.784355] pciehp 0000:00:1c.4:pcie04: Device 0000:0b:00.0 already
exists at 0000:0b:00, cannot hot-add
[ 7407.784357] pciehp 0000:00:1c.4:pcie04: Cannot add device at 0000:0b:0=

0
[ 7407.857151] ata3.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)
filtered out
[ 7407.857153] ata3.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES)
filtered out
[ 7407.857392] ata3.00: supports DRM functions and may not be fully
accessible
[ 7407.864932] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)
filtered out
[ 7407.864933] ata1.00: ACPI cmd ef/03:44:00:00:00:a0 (SET FEATURES)
filtered out
[ 7407.880519] ata1.00: configured for UDMA/66
[ 7407.888134] pciehp 0000:00:1c.5:pcie04: Device 0000:0c:00.0 already
exists at 0000:0c:00, cannot hot-add
[ 7407.888136] pciehp 0000:00:1c.5:pcie04: Cannot add device at 0000:0c:0=

0
[ 7407.888345] pciehp 0000:00:1c.4:pcie04: Device 0000:0b:00.0 already
exists at 0000:0b:00, cannot hot-add
[ 7407.888346] pciehp 0000:00:1c.4:pcie04: Cannot add device at 0000:0b:0=

0
[ 7407.889046] ata3.00: supports DRM functions and may not be fully
accessible
[ 7407.889366] ata3.00: configured for UDMA/133
[ 7408.012088] usb 2-1: reset full-speed USB device number 2 using uhci_h=
cd
[ 7408.160066] usb 6-1: reset low-speed USB device number 2 using uhci_hc=
d
[ 7408.236071] firewire_core 0000:0d:03.0: rediscovered device fw0
[ 7408.445725] usb 2-1.1: reset full-speed USB device number 3 using
uhci_hcd
[ 7408.560062] usb 6-2: reset full-speed USB device number 3 using uhci_h=
cd
[ 7408.788054] pciehp 0000:00:01.0:pcie04: Device 0000:01:00.0 already
exists at 0000:01:00, cannot hot-add
[ 7408.788057] pciehp 0000:00:01.0:pcie04: Cannot add device at 0000:01:0=

0
[ 7409.896086] pciehp 0000:00:01.0:pcie04: Device 0000:01:00.0 already
exists at 0000:01:00, cannot hot-add
[ 7409.896087] pciehp 0000:00:01.0:pcie04: Cannot add device at 0000:01:0=

0
[ 7409.896152] rtc_cmos 00:03: System wakeup disabled by ACPI
[ 7410.844536] PM: resume of devices complete after 3163.615 msecs
[ 7410.844800] input: bcm5974 as
/devices/pci0000:00/0000:00:1d.2/usb6/6-2/6-2:1.2/input/input17
[ 7410.847811] PM: Finishing wakeup.
[ 7410.847812] Restarting tasks done.
[ 7411.084575] systemd[1]: suspend.target: Unit is bound to inactive
unit systemd-suspend.service. Stopping, too.
[ 7411.097178] sky2 0000:0c:00.0 eth0: enabling interface
[ 7411.283269] b43-phy0: Loading firmware version 666.2 (2011-02-23
01:15:07)
[ 7419.491533] wlan0: authenticate with 14:0c:76:6f:58:9c
[ 7419.600680] wlan0: send auth to 14:0c:76:6f:58:9c (try 1/3)
[ 7419.602726] wlan0: authenticated
[ 7419.604105] wlan0: associate with 14:0c:76:6f:58:9c (try 1/3)
[ 7419.608401] wlan0: RX AssocResp from 14:0c:76:6f:58:9c (capab=0x411
status=0 aid=3)
[ 7419.609128] wlan0: associated


--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe"
vers debian-user-french-REQUEST@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmaster@lists.debian.org
Archive: https://lists.debian.org/55B33AEE.8070707@tourde.org
Vidéos High-Tech et Jeu Vidéo
Téléchargements
Vos réponses
Gagnez chaque mois un abonnement Premium avec GNT : Inscrivez-vous !
Trier par : date / pertinence
Sylvain L. Sauvage
Le #26361300
Le samedi 25 juillet 2015, 09:29:50 Damien TOURDE a écrit :
Bonjour,



’jour,

Je suis en testing, depuis la dernière MAJ que j'ai faite
(assez importante avec gnome->3.16, linux-image -> 4.0), mon
laptop ne se met plus en veille à chaque fois.



Déjà, regarde les logs et cherche quels paquets ont ét é mis à
jour (noyau ?).

[…]
Voici le résultat de dmesg […]
En revanche, lorsqu'il se met en veille "correctement", le
dmesg donne ça : […]



Enlève les horaires (colonne de gauche) et fais un diff, parce
que, franchement, faut être courageux pour le faire « à la
main » sur un courriel…

--
Sylvain Sauvage

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe"
vers
En cas de soucis, contactez EN ANGLAIS
Archive: https://lists.debian.org/
Damien TOURDE
Le #26361364
Bonjour,

Désolé, en effet c'était illisible. Après un passage dans emacs pour
virer les dates voilà le diff :


Je vais jeter un coup d'oeuil au log d'aptitude aussi.

:~/Documents/temp/diffsuspend$ diff -b
--suppress-common-lines ok notok
4d3
< IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
5a5
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready


19c19
< Freezing user space processes ... (elapsed 0.001 seconds)done.
---
Freezing user space processes ... (elapsed 0.001seconds) done.


25,26c25,26
< PM: suspend of devices complete after 529.819 msecs
< PM: late suspend of devices complete after 0.486 msecs
---
PM: suspend of devices complete after 288.020 msecs
PM: late suspend of devices complete after 0.488 msecs


34c34
< PM: noirq suspend of devices complete after 155.347 msecs
---
PM: noirq suspend of devices complete after 154.196 msecs


55c55
< PM: noirq resume of devices complete after 156.673 msecs
---
PM: noirq resume of devices complete after 156.772 msecs


63c63,64
< PM: early resume of devices complete after 0.155 msecs
---
PM: early resume of devices complete after 0.225 msecs
usb usb1: root hub lost power or was reset


68,71c69,72
< usb usb6: root hub lost power or was reset
< pciehp 0000:00:1c.5:pcie04: Timeout on hotplug command0x1038 (issued
88048 msec ago)
< pciehp 0000:00:1c.0:pcie04: Timeout on hotplug command0x1038 (issued
88048 msec ago)
< pciehp 0000:00:1c.2:pcie04: Timeout on hotplug command0x1038 (issued
88048 msec ago)
---
pciehp 0000:00:1c.0:pcie04: Timeout on hotplug command0x1038 (issued


5463088 msec ago)
pciehp 0000:00:1c.2:pcie04: Timeout on hotplug command0x1038 (issued


5463088 msec ago)
pciehp 0000:00:1c.4:pcie04: Timeout on hotplug command0x1038 (issued


5463088 msec ago)
pciehp 0000:00:1c.5:pcie04: Timeout on hotplug command0x1038 (issued


5463088 msec ago)
73d73
< pciehp 0000:00:1c.4:pcie04: Timeout on hotplug command0x1038 (issued
88048 msec ago)
77a78,79
ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)filtered out
ata1.00: ACPI cmd ef/03:44:00:00:00:a0 (SET FEATURES)filtered out


81,82c83,84
< ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)filtered out
< ata1.00: ACPI cmd ef/03:44:00:00:00:a0 (SET FEATURES)filtered out
---
ata3.00: supports DRM functions and may not be fullyaccessible
ata3.00: configured for UDMA/133


88,91c90,91
< ata3.00: supports DRM functions and may not be fullyaccessible
< ata3.00: configured for UDMA/133
< usb 2-1: reset full-speed USB device number 2 using uhci_hcd
< usb 6-1: reset low-speed USB device number 2 using uhci_hcd
---
usb 1-1: reset full-speed USB device number 2 using uhci_hcd
usb 5-1: reset low-speed USB device number 2 using uhci_hcd


93,94c93,94
< usb 2-1.1: reset full-speed USB device number 3 usinguhci_hcd
< usb 6-2: reset full-speed USB device number 3 using uhci_hcd
---
usb 1-1.1: reset full-speed USB device number 3 usinguhci_hcd
usb 5-2: reset full-speed USB device number 4 using uhci_hcd


100,101c100,101
< PM: resume of devices complete after 3163.615 msecs
< input: bcm5974
as/devices/pci0000:00/0000:00:1d.2/usb6/6-2/6-2:1.2/input/input17
---
PM: resume of devices complete after 2991.628 msecs
input: bcm5974


as/devices/pci0000:00/0000:00:1d.2/usb5/5-2/5-2:1.2/input/input30
104d103
< systemd[1]: suspend.target: Unit is bound to inactiveunit
systemd-suspend.service. Stopping, too.
111c110
< wlan0: RX AssocResp from 14:0c:76:6f:58:9c (capab=0x411status=0 aid=3)
---
wlan0: RX AssocResp from 14:0c:76:6f:58:9c (capab=0x411status=0 aid=2)







Le 25/07/2015 16:47, Sylvain L. Sauvage a écrit :
Le samedi 25 juillet 2015, 09:29:50 Damien TOURDE a écrit :
Bonjour,


’jour,

Je suis en testing, depuis la dernière MAJ que j'ai faite
(assez importante avec gnome->3.16, linux-image -> 4.0), mon
laptop ne se met plus en veille à chaque fois.


Déjà, regarde les logs et cherche quels paquets ont été mis à
jour (noyau ?).

[…]
Voici le résultat de dmesg […]
En revanche, lorsqu'il se met en veille "correctement", le
dmesg donne ça : […]


Enlève les horaires (colonne de gauche) et fais un diff, parce
que, franchement, faut être courageux pour le faire « à la
main » sur un courriel…




--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe"
vers
En cas de soucis, contactez EN ANGLAIS
Archive: https://lists.debian.org/
Sylvain L. Sauvage
Le #26361371
Le dimanche 26 juillet 2015, 14:55:21 Damien TOURDE a écrit :
Bonjour,



’jour,

Désolé, en effet c'était illisible. Après un pass age dans
emacs pour virer les dates voilà le diff :



Ok, j’aurais préféré un diff -U0 mais c’ est quand même plus
lisible ;oP
Bon, perso, je n’y vois rien de concluant…

Je vais jeter un coup d'oeuil au log d'aptitude aussi.



Si c’est le noyau (grosse suspicion quand même), essaie de
revenir au précédent un attendant.
Je ne sais pas trop où ça en est¹ mais tu pourrais aus si
essayer de jouer avec les options ACPI du noyau.


¹ il y a des progrès qui sont faits tout le temps pour que à §a
fonctionne sans qu’on fasse rien mais des vieilles docs parfois
contre-productives sont souvent les premières que l’on tro uve…

--
Sylvain Sauvage

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe"
vers
En cas de soucis, contactez EN ANGLAIS
Archive: https://lists.debian.org/
Damien TOURDE
Le #26361376
Merci,

Je vais voir ça, je ne me suis jamais penché dessus ;-)

Si je trouve quelque chose je posterais ça en réponse.

Le 26/07/2015 15:25, Sylvain L. Sauvage a écrit :
Le dimanche 26 juillet 2015, 14:55:21 Damien TOURDE a écrit :
Bonjour,


’jour,

Désolé, en effet c'était illisible. Après un passage dans
emacs pour virer les dates voilà le diff :


Ok, j’aurais préféré un diff -U0 mais c’est quand même plus
lisible ;oP
Bon, perso, je n’y vois rien de concluant…

Je vais jeter un coup d'oeuil au log d'aptitude aussi.


Si c’est le noyau (grosse suspicion quand même), essaie de
revenir au précédent un attendant.
Je ne sais pas trop où ça en est¹ mais tu pourrais aussi
essayer de jouer avec les options ACPI du noyau.


¹ il y a des progrès qui sont faits tout le temps pour que ça
fonctionne sans qu’on fasse rien mais des vieilles docs parfois
contre-productives sont souvent les premières que l’on trouve…




--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe"
vers
En cas de soucis, contactez EN ANGLAIS
Archive: https://lists.debian.org/
Damien TOURDE
Le #26363113
Bonjour,

Comme promis, un retour.

En effet le passage temporaire au noyau 3..... 16 ? (il me semble) a
"corrigé" le problème, ou plutôt a remis en fonction ce qui fonctionnait
déjà :-)

Suite à un patch du noyau (fait par le développeur Debian, pas par moi)
4.0, la mise en veille semble refonctionner comme avant, de ce que j'ai
pu en voir pour l'instant.


Merci,
Damien

Le 26/07/2015 16:42, Damien TOURDE a écrit :
Merci,

Je vais voir ça, je ne me suis jamais penché dessus ;-)

Si je trouve quelque chose je posterais ça en réponse.

Le 26/07/2015 15:25, Sylvain L. Sauvage a écrit :
Le dimanche 26 juillet 2015, 14:55:21 Damien TOURDE a écrit :
Bonjour,


’jour,

Désolé, en effet c'était illisible. Après un passage dans
emacs pour virer les dates voilà le diff :


Ok, j’aurais préféré un diff -U0 mais c’est quand même plus
lisible ;oP
Bon, perso, je n’y vois rien de concluant…

Je vais jeter un coup d'oeuil au log d'aptitude aussi.


Si c’est le noyau (grosse suspicion quand même), essaie de
revenir au précédent un attendant.
Je ne sais pas trop où ça en est¹ mais tu pourrais aussi
essayer de jouer avec les options ACPI du noyau.


¹ il y a des progrès qui sont faits tout le temps pour que ça
fonctionne sans qu’on fasse rien mais des vieilles docs parfois
contre-productives sont souvent les premières que l’on trouve…






--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe"
vers
En cas de soucis, contactez EN ANGLAIS
Archive: https://lists.debian.org/
Publicité
Poster une réponse
Anonyme