[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Ne se met plus en veille depuis dernière MAJ



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.

damien@MBP-Debian-Damien:~/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…
>


Reply to: