Debian-facile

Bienvenue sur Debian-Facile, site d'aide pour les nouveaux utilisateurs de Debian.

Vous n'êtes pas identifié(e).

#1 09-11-2015 20:33:10

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Probleme Mise en veille/ Hibernation/ Screensaver

Voila j'ai un bug qui semble récurent sur Debian.
Comme le post de pili36 https://debian-facile.org/viewtopic.php?id=11584 sauf que moi c'est un ordinateur bureau.
Comme j'aime bien tester plusieurs chose a la fois, ce coup ci le prob demeure depuis j'ai installé ce pc (j'attendais vois si une MAJ aurait réglé le trouble) donc pas du a une fausse manipulation.

Que ce soit via le GTK mise en vielle ou en ligne de commande rien n'y fait. Sauf après un reboot la première tentative de mise en veille fonctionne les suivante non.
J'ai installer uswsusp, s2ram, s2disk ....

uswsusp


bash: uswsusp : commande introuvable


sudo s2ram


This kernel doesn't have KMS support.
Machine is unknown.
This machine can be identified by:
    sys_vendor   = "Hewlett-Packard"
    sys_product  = "HP Compaq dc7600 Convertible Minitower"
    sys_version  = " "
    bios_version = "786D1 v01.61"


Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#2 09-11-2015 21:44:47

Severian
Membre
Distrib. : Debian GNU/Linux 8.6 (jessie)
Noyau : Linux 4.6.0-0.bpo.1-amd64
(G)UI : Openbox 3.6.1-2
Inscription : 13-12-2014

Re : Probleme Mise en veille/ Hibernation/ Screensaver

j'ai un peu de mal à comprendre le sujet smile
Probleme Mise en veille/ Hibernation -> ok c'est dans la même veine smile

s2ram, s2disk > pas dans jessie, du coup je ne connais pas smile

si tu as le même log que pili36, ça me ferait presque penser à du WOL (bref ta connexion qui empêche la mise en veille)

sinon, Screensaver c'est quoi le soucis ?

"il est urgent d'attendre" (bendia)
ob3-debian2-150x50.png

Hors ligne

#3 09-11-2015 22:07:43

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Pas de WOL ici, Screensaver empêche selon moi l'hibernation/mise en veille

s2ram https://packages.debian.org/search?keyw … lla-search si tu regarde ma description PC tu verra je ne suis pas sous jessie mais plutot stretch/sid Debian 9.0 !

Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#4 09-11-2015 22:14:18

Severian
Membre
Distrib. : Debian GNU/Linux 8.6 (jessie)
Noyau : Linux 4.6.0-0.bpo.1-amd64
(G)UI : Openbox 3.6.1-2
Inscription : 13-12-2014

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Ir0nsh007er a écrit :

Pas de WOL ici, Screensaver empêche selon moi l'hibernation/mise en veille



et donc tu as désactivé Screensaver pour voir si ça venait de là ?


"il est urgent d'attendre" (bendia)
ob3-debian2-150x50.png

Hors ligne

#5 09-11-2015 22:29:28

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Nop pas désactivé screensaver puisque je veux qu’après 15min mon pc active le screensaver et après 1hrs la mise en veille s'active ..
Pour la gestion de suspend j'ai 

uswsusp:
  Installé : 1.0+20120915-6.1
  Candidat : 1.0+20120915-6.1


Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#6 09-11-2015 22:53:01

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

cat /sys/power/state


freeze standby mem disk


cat /sys/power/disk


[platform] shutdown reboot suspend


Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#7 09-11-2015 22:55:50

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Severian a écrit :

Ir0nsh007er a écrit :

Pas de WOL ici, Screensaver empêche selon moi l'hibernation/mise en veille



et donc tu as désactivé Screensaver pour voir si ça venait de là ?


Test fait en désactivant le screensaver et mise en veille activé aussitôt l'ordi reviens a lui tout seul ..

Edit: J'ai même tuer le démon .. avec mon épée de glace .. !!!! Rien ne vas.

Dernière modification par Ir0nsh007er (09-11-2015 22:57:39)


Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#8 09-11-2015 23:07:15

Severian
Membre
Distrib. : Debian GNU/Linux 8.6 (jessie)
Noyau : Linux 4.6.0-0.bpo.1-amd64
(G)UI : Openbox 3.6.1-2
Inscription : 13-12-2014

Re : Probleme Mise en veille/ Hibernation/ Screensaver

donc tu peux écarter screensaver des raisons smile

il faudrait voir les logs du moment de la mise en veille smile

"il est urgent d'attendre" (bendia)
ob3-debian2-150x50.png

Hors ligne

#9 09-11-2015 23:16:25

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Ok pour les logs

Dernière modification par Ir0nsh007er (09-11-2015 23:27:55)


Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#10 09-11-2015 23:25:21

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

/var/log/sys/

Nov  9 15:56:22 puissant NetworkManager[728]: <info>  (eth0): DHCPv4 state changed bound -> done
Nov  9 15:56:22 puissant avahi-daemon[733]: Withdrawing address record for 192.168.2.230 on eth0.
Nov  9 15:56:22 puissant avahi-daemon[733]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.2.230.
Nov  9 15:56:22 puissant avahi-daemon[733]: Interface eth0.IPv4 no longer relevant for mDNS.
Nov  9 15:56:22 puissant avahi-daemon[733]: Withdrawing address record for fe80::960c:6dff:fe81:e825 on eth0.
Nov  9 15:56:22 puissant avahi-daemon[733]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::960c:6dff:fe81:e825.
Nov  9 15:56:22 puissant avahi-daemon[733]: Interface eth0.IPv6 no longer relevant for mDNS.
Nov  9 15:56:22 puissant NetworkManager[728]: <info>  NetworkManager state is now ASLEEP
Nov  9 15:56:22 puissant dbus[671]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Nov  9 15:56:22 puissant NetworkManager[728]: <info>  (eth0): link disconnected
Nov  9 15:56:22 puissant systemd[1]: Reached target Sleep.
Nov  9 15:56:22 puissant systemd[1]: Starting Suspend...
Nov  9 15:56:22 puissant systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov  9 15:56:22 puissant systemd-sleep[8036]: Suspending system...
Nov  9 15:56:22 puissant dbus[671]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov  9 15:56:22 puissant systemd[1]: Started Network Manager Script Dispatcher Service.
Nov  9 15:56:22 puissant nm-dispatcher: Dispatching action 'down' for eth0
Nov  9 15:56:22 puissant kernel: [ 3688.404424] PM: Syncing filesystems ... done.
Nov  9 15:56:22 puissant kernel: [ 3688.616449] PM: Preparing system for sleep (mem)
Nov  9 15:56:25 puissant kernel: [ 3688.848637] Freezing user space processes ... (elapsed 0.004 seconds) done.
Nov  9 15:56:25 puissant kernel: [ 3688.853318] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Nov  9 15:56:25 puissant kernel: [ 3688.854593] PM: Suspending system (mem)
Nov  9 15:56:25 puissant kernel: [ 3688.854613] Suspending console(s) (use no_console_suspend to debug)
Nov  9 15:56:25 puissant kernel: [ 3688.855205] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Nov  9 15:56:25 puissant kernel: [ 3688.855384] sd 0:0:0:0: [sda] Stopping disk
Nov  9 15:56:25 puissant kernel: [ 3688.908051] tpm_tis 00:06: Error (38) sending savestate before suspend
Nov  9 15:56:25 puissant kernel: [ 3688.908062] __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x1b0 [tpm] returns 38
Nov  9 15:56:25 puissant kernel: [ 3688.908068] dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 38
Nov  9 15:56:25 puissant kernel: [ 3688.908071] PM: Device 00:06 failed to suspend: error 38
Nov  9 15:56:25 puissant kernel: [ 3689.160141] PM: Some devices failed to suspend, or early wake event detected
Nov  9 15:56:25 puissant kernel: [ 3689.161387] sd 0:0:0:0: [sda] Starting disk
Nov  9 15:56:25 puissant kernel: [ 3689.327464] ata1.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
Nov  9 15:56:25 puissant kernel: [ 3689.327468] ata1.01: ACPI cmd ef/03:43:00:00:00:b0 (SET FEATURES) filtered out
Nov  9 15:56:25 puissant kernel: [ 3689.340317] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
Nov  9 15:56:25 puissant kernel: [ 3689.340321] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
Nov  9 15:56:25 puissant kernel: [ 3689.340447] PM: resume of devices complete after 180.301 msecs
Nov  9 15:56:25 puissant kernel: [ 3689.340636] ata1.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
Nov  9 15:56:25 puissant kernel: [ 3691.138456] ata1.00: ACPI cmd e3/00:00:00:00:00:a0 (IDLE) succeeded
Nov  9 15:56:25 puissant kernel: [ 3691.138460] ata1.00: ACPI cmd b1/c1:00:00:00:00:a0 (DEVICE CONFIGURATION OVERLAY) filtered out
Nov  9 15:56:25 puissant kernel: [ 3691.138462] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Nov  9 15:56:25 puissant kernel: [ 3691.152334] ata1.00: configured for UDMA/100
Nov  9 15:56:25 puissant kernel: [ 3691.168324] ata1.01: configured for UDMA/66
Nov  9 15:56:25 puissant kernel: [ 3691.194453] PM: Finishing wakeup.
Nov  9 15:56:25 puissant kernel: [ 3691.194457] Restarting tasks ... done.
Nov  9 15:56:25 puissant systemd-sleep[8036]: System resumed.
Nov  9 15:56:25 puissant systemd[1]: Started Suspend.
Nov  9 15:56:25 puissant systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Nov  9 15:56:25 puissant systemd[1]: Stopped target Sleep.
Nov  9 15:56:25 puissant systemd[1]: Reached target Suspend.
Nov  9 15:56:25 puissant systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service. Stopping, too.
Nov  9 15:56:25 puissant systemd[1]: Stopped target Suspend.
Nov  9 15:56:25 puissant systemd[1]: Started Run anacron jobs at resume.
Nov  9 15:56:25 puissant NetworkManager[728]: <info>  wake requested (sleeping: yes  enabled: yes)
Nov  9 15:56:25 puissant NetworkManager[728]: <info>  waking up...
Nov  9 15:56:25 puissant NetworkManager[728]: <info>  (eth1): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Nov  9 15:56:25 puissant systemd[1]: Started Run anacron jobs.
Nov  9 15:56:25 puissant anacron[8051]: Anacron 2.3 started on 2015-11-09
Nov  9 15:56:25 puissant anacron[8051]: Normal exit (0 jobs run)
Nov  9 15:56:25 puissant NetworkManager[728]: <info>  (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov  9 15:56:25 puissant kernel: [ 3691.351754] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov  9 15:56:25 puissant kernel: [ 3691.361214] r8169 0000:05:09.0 eth0: link down
Nov  9 15:56:25 puissant kernel: [ 3691.361368] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov  9 15:56:25 puissant kernel: [ 3691.361426] r8169 0000:05:09.0 eth0: link down
Nov  9 15:56:25 puissant NetworkManager[728]: <info>  (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov  9 15:56:25 puissant kernel: [ 3691.373158] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Nov  9 15:56:25 puissant NetworkManager[728]: <info>  NetworkManager state is now DISCONNECTED
Nov  9 15:56:25 puissant kernel: [ 3691.424222] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Nov  9 15:56:26 puissant kernel: [ 3693.019851] r8169 0000:05:09.0 eth0: link up
Nov  9 15:56:26 puissant kernel: [ 3693.019867] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  (eth0): link connected
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  Auto-activating connection 'Connexion Ethernet 1'.
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  (eth0): Activation: starting connection 'Connexion Ethernet 1' (7b758612-c117-41f0-b7fc-9c1e17051d3c)
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  NetworkManager state is now CONNECTING
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  dhclient started with pid 8055
Nov  9 15:56:27 puissant dhclient[8055]: DHCPREQUEST of 192.168.2.230 on eth0 to 255.255.255.255 port 67
Nov  9 15:56:28 puissant dhclient[8055]: DHCPACK of 192.168.2.230 from 192.168.2.1
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    address 192.168.2.230
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    plen 24 (255.255.255.0)
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    gateway 192.168.2.1
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    server identifier 192.168.2.1
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    lease time 259200
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    nameserver '192.168.2.1'
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    domain name 'home'
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  (eth0): DHCPv4 state changed unknown -> bound
Nov  9 15:56:28 puissant avahi-daemon[733]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.2.230.
Nov  9 15:56:28 puissant avahi-daemon[733]: New relevant interface eth0.IPv4 for mDNS.
Nov  9 15:56:28 puissant avahi-daemon[733]: Registering new address record for 192.168.2.230 on eth0.IPv4.
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  NetworkManager state is now CONNECTED_LOCAL
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  NetworkManager state is now CONNECTED_GLOBAL
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  Policy set 'Connexion Ethernet 1' (eth0) as default for IPv4 routing and DNS.
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  (eth0): Activation: successful, device activated.
Nov  9 15:56:28 puissant dhclient[8055]: bound to 192.168.2.230 -- renewal in 118890 seconds.
Nov  9 15:56:28 puissant nm-dispatcher: Dispatching action 'up' for eth0
Nov  9 15:56:28 puissant avahi-daemon[733]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::960c:6dff:fe81:e825.
Nov  9 15:56:28 puissant avahi-daemon[733]: New relevant interface eth0.IPv6 for mDNS.
Nov  9 15:56:28 puissant avahi-daemon[733]: Registering new address record for fe80::960c:6dff:fe81:e825 on eth0.*.
Nov  9 15:56:29 puissant freshclam[704]: Received signal: wake up
Nov  9 15:56:29 puissant freshclam[704]: ClamAV update process started at Mon Nov  9 15:56:29 2015
Nov  9 15:56:30 puissant freshclam[704]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Nov  9 15:56:30 puissant freshclam[704]: daily.cld is up to date (version: 21049, sigs: 1673890, f-level: 63, builder: neo)
Nov  9 15:56:30 puissant freshclam[704]: bytecode.cld is up to date (version: 270, sigs: 46, f-level: 63, builder: shurley)
Nov  9 15:56:34 puissant nslcd[1174]: caught signal SIGUSR1 (10), refresh retries
Nov  9 15:56:34 puissant nm-dispatcher[8037]: Sending network state change signal to nslcd...done.
Nov  9 15:56:34 puissant nslcd[1174]: caught signal SIGUSR1 (10), refresh retries
Nov  9 15:56:34 puissant nm-dispatcher[8037]: Sending network state change signal to nslcd...done.
Nov  9 15:56:38 puissant clamd[737]: No stats for Database check - forcing reload
Nov  9 15:56:39 puissant clamd[737]: Reading databases from /var/lib/clamav
Nov  9 15:56:59 puissant clamd[737]: Database correctly reloaded (4092594 signatures)
Nov  9 15:58:09 puissant kernel: [ 3795.992049] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
Nov  9 15:58:10 puissant kernel: [ 3796.112046] usb 3-2: device descriptor read/64, error -71
Nov  9 15:58:41 puissant nslcd[1174]: [884adc] <authz="ir0n"> failed to bind to LDAP server ldapi:///192.168.2.214: Can't contact LDAP server: Connection refused
Nov  9 15:58:41 puissant nslcd[1174]: [884adc] <authz="ir0n"> no available LDAP server found: Can't contact LDAP server: Connection refused
Nov  9 15:58:42 puissant kernel: [ 3828.952060] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
Nov  9 15:58:43 puissant kernel: [ 3829.072053] usb 3-2: device descriptor read/64, error -71
Nov  9 16:01:20 puissant nslcd[1174]: [ead36b] <group/member="redis"> failed to bind to LDAP server ldapi:///192.168.2.214: Can't contact LDAP server: Connection refused
Nov  9 16:01:20 puissant nslcd[1174]: [ead36b] <group/member="redis"> no available LDAP server found: Can't contact LDAP server: Connection refused
Nov  9 16:01:20 puissant nslcd[1174]: [ead36b] <group/member="redis"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:03:13 puissant kernel: [ 4099.032029] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
Nov  9 16:03:13 puissant kernel: [ 4099.152026] usb 3-2: device descriptor read/64, error -71
Nov  9 16:07:49 puissant nslcd[1174]: [517796] <group/member="avahi"> failed to bind to LDAP server ldapi:///192.168.2.214: Can't contact LDAP server: Connection refused
Nov  9 16:07:49 puissant nslcd[1174]: [517796] <group/member="avahi"> no available LDAP server found: Can't contact LDAP server: Connection refused
Nov  9 16:07:49 puissant nslcd[1174]: [517796] <group/member="avahi"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:07:49 puissant nslcd[1174]: [0bd78f] <group/member="colord"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [0bd78f] <group/member="colord"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [3ea438] <group/member="dnsmasq"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [3ea438] <group/member="dnsmasq"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [55585c] <group/member="systemd-resolve"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [55585c] <group/member="systemd-resolve"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [a64e2a] <group/member="pulse"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [a64e2a] <group/member="pulse"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [2342ec] <group/member="systemd-network"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [2342ec] <group/member="systemd-network"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [487cb0] <group/member="messagebus"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [487cb0] <group/member="messagebus"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [4ed43b] <group/member="openldap"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [4ed43b] <group/member="openldap"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [5a06fb] <group/member="rtkit"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [5a06fb] <group/member="rtkit"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [d89a32] <group/member="geoclue"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [d89a32] <group/member="geoclue"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [e4ccaf] <group/member="mysql"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [e4ccaf] <group/member="mysql"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:08:04 puissant nslcd[1174]: [6d8d3c] <group/member="nslcd"> failed to bind to LDAP server ldapi:///192.168.2.214: Can't contact LDAP server: Connection refused
Nov  9 16:08:04 puissant nslcd[1174]: [6d8d3c] <group/member="nslcd"> no available LDAP server found: Can't contact LDAP server: Connection refused
Nov  9 16:08:04 puissant nslcd[1174]: [6d8d3c] <group/member="nslcd"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [588f54] <group/member="www-data"> failed to bind to LDAP server ldapi:///192.168.2.214: Can't contact LDAP server: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [588f54] <group/member="www-data"> no available LDAP server found: Can't contact LDAP server: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [588f54] <group/member="www-data"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [2289ec] <group/member="www-data"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [2289ec] <group/member="www-data"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [e91b18] <group/member="www-data"> no available LDAP server found: Server is unavailable
Nov  9 16:08:19 puissant nslcd[1174]: [e91b18] <group/member="www-data"> no available LDAP server found: Server is unavailable
Nov  9 16:08:19 puissant nslcd[1174]: [437fdb] <group/member="www-data"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:08:19 puissant nslcd[1174]: [437fdb] <group/member="www-data"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:08:19 puissant nslcd[1174]: [44a45c] <group/member="www-data"> no available LDAP server found: Server is unavailable
Nov  9 16:08:19 puissant nslcd[1174]: [44a45c] <group/member="www-data"> no available LDAP server found: Server is unavailable
Nov  9 16:08:19 puissant nslcd[1174]: [fff902] <group/member="lightdm"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [fff902] <group/member="lightdm"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:08:19 puissant kernel: [ 4405.976032] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
Nov  9 16:08:20 puissant kernel: [ 4406.096030] usb 3-2: device descriptor read/64, error -71
Nov  9 16:08:52 puissant kernel: [ 4439.000035] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
Nov  9 16:08:53 puissant kernel: [ 4439.120032] usb 3-2: device descriptor read/64, error -71
Nov  9 16:09:02 puissant CRON[8499]: (root) CMD (  [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Nov  9 16:13:29 puissant kernel: [ 4715.992041] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
Nov  9 16:13:30 puissant kernel: [ 4716.116045] usb 3-2: device descriptor read/64, error -71
Nov  9 16:14:02 puissant kernel: [ 4749.016059] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
Nov  9 16:14:03 puissant kernel: [ 4749.136034] usb 3-2: device descriptor read/64, error -71
Nov  9 16:15:16 puissant kernel: [ 4822.675837] perf interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
Nov  9 16:17:01 puissant CRON[8625]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Nov  9 16:17:52 puissant systemd[1]: Created slice user-0.slice.
Nov  9 16:17:52 puissant systemd[1]: Starting User Manager for UID 0...
Nov  9 16:17:52 puissant systemd[1]: Started Session c2 of user root.
Nov  9 16:17:53 puissant systemd[8639]: Reached target Sockets.
Nov  9 16:17:53 puissant systemd[8639]: Removed slice Root Slice.
Nov  9 16:17:53 puissant systemd[8639]: Reached target Paths.
Nov  9 16:17:53 puissant systemd[8639]: Reached target Timers.
Nov  9 16:17:53 puissant systemd[8639]: Reached target Basic System.
Nov  9 16:17:53 puissant systemd[8639]: Reached target Default.
Nov  9 16:17:53 puissant systemd[8639]: Startup finished in 86ms.
Nov  9 16:17:53 puissant systemd[1]: Started User Manager for UID 0.
Nov  9 16:17:53 puissant systemd[1]: Stopping User Manager for UID 0...
Nov  9 16:17:53 puissant systemd[8639]: Reached target Shutdown.
Nov  9 16:17:53 puissant systemd[8639]: Stopped target Default.
Nov  9 16:17:53 puissant systemd[8639]: Stopped target Basic System.
Nov  9 16:17:53 puissant systemd[8639]: Stopped target Sockets.
Nov  9 16:17:53 puissant systemd[8639]: Stopped target Timers.
Nov  9 16:17:53 puissant systemd[8639]: Created slice Root Slice.
Nov  9 16:17:53 puissant systemd[8639]: Starting Exit the Session...
Nov  9 16:17:53 puissant systemd[8639]: Stopped target Paths.
Nov  9 16:17:53 puissant systemd[8639]: Received SIGRTMIN+24 from PID 8644 (kill).
Nov  9 16:17:53 puissant systemd[1]: Stopped User Manager for UID 0.
Nov  9 16:17:53 puissant systemd[1]: Removed slice user-0.slice.



/var/log/daemon.log

Nov  9 15:54:51 puissant NetworkManager[728]: <info>  wake requested (sleeping: yes  enabled: yes)
Nov  9 15:54:51 puissant NetworkManager[728]: <info>  waking up...
Nov  9 15:54:51 puissant NetworkManager[728]: <info>  (eth1): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Nov  9 15:54:51 puissant NetworkManager[728]: <info>  (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov  9 15:54:51 puissant NetworkManager[728]: <info>  (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov  9 15:54:51 puissant NetworkManager[728]: <info>  NetworkManager state is now DISCONNECTED
Nov  9 15:54:53 puissant NetworkManager[728]: <info>  (eth0): link connected
Nov  9 15:54:53 puissant NetworkManager[728]: <info>  (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Nov  9 15:54:53 puissant NetworkManager[728]: <info>  Auto-activating connection 'Connexion Ethernet 1'.
Nov  9 15:54:53 puissant NetworkManager[728]: <info>  (eth0): Activation: starting connection 'Connexion Ethernet 1' (7b758612-c117-41f0-b7fc-9c1e17051d3c)
Nov  9 15:54:53 puissant NetworkManager[728]: <info>  (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov  9 15:54:53 puissant NetworkManager[728]: <info>  NetworkManager state is now CONNECTING
Nov  9 15:54:53 puissant NetworkManager[728]: <info>  (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov  9 15:54:53 puissant NetworkManager[728]: <info>  (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Nov  9 15:54:53 puissant NetworkManager[728]: <info>  Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov  9 15:54:53 puissant NetworkManager[728]: <info>  dhclient started with pid 7881
Nov  9 15:54:53 puissant dhclient[7881]: DHCPREQUEST of 192.168.2.230 on eth0 to 255.255.255.255 port 67
Nov  9 15:54:54 puissant dhclient[7881]: DHCPACK of 192.168.2.230 from 192.168.2.1
Nov  9 15:54:54 puissant NetworkManager[728]: <info>    address 192.168.2.230
Nov  9 15:54:54 puissant NetworkManager[728]: <info>    plen 24 (255.255.255.0)
Nov  9 15:54:54 puissant NetworkManager[728]: <info>    gateway 192.168.2.1
Nov  9 15:54:54 puissant NetworkManager[728]: <info>    server identifier 192.168.2.1
Nov  9 15:54:54 puissant NetworkManager[728]: <info>    lease time 259200
Nov  9 15:54:54 puissant NetworkManager[728]: <info>    nameserver '192.168.2.1'
Nov  9 15:54:54 puissant NetworkManager[728]: <info>    domain name 'home'
Nov  9 15:54:54 puissant NetworkManager[728]: <info>  (eth0): DHCPv4 state changed unknown -> bound
Nov  9 15:54:54 puissant avahi-daemon[733]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.2.230.
Nov  9 15:54:54 puissant avahi-daemon[733]: New relevant interface eth0.IPv4 for mDNS.
Nov  9 15:54:54 puissant avahi-daemon[733]: Registering new address record for 192.168.2.230 on eth0.IPv4.
Nov  9 15:54:54 puissant NetworkManager[728]: <info>  (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Nov  9 15:54:54 puissant NetworkManager[728]: <info>  (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Nov  9 15:54:54 puissant NetworkManager[728]: <info>  (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Nov  9 15:54:54 puissant NetworkManager[728]: <info>  NetworkManager state is now CONNECTED_LOCAL
Nov  9 15:54:54 puissant dhclient[7881]: bound to 192.168.2.230 -- renewal in 122648 seconds.
Nov  9 15:54:54 puissant NetworkManager[728]: <info>  NetworkManager state is now CONNECTED_GLOBAL
Nov  9 15:54:54 puissant NetworkManager[728]: <info>  Policy set 'Connexion Ethernet 1' (eth0) as default for IPv4 routing and DNS.
Nov  9 15:54:54 puissant NetworkManager[728]: <info>  (eth0): Activation: successful, device activated.
Nov  9 15:54:54 puissant nm-dispatcher: Dispatching action 'up' for eth0
Nov  9 15:54:54 puissant avahi-daemon[733]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::960c:6dff:fe81:e825.
Nov  9 15:54:54 puissant avahi-daemon[733]: New relevant interface eth0.IPv6 for mDNS.
Nov  9 15:54:54 puissant avahi-daemon[733]: Registering new address record for fe80::960c:6dff:fe81:e825 on eth0.*.
Nov  9 15:54:57 puissant nslcd[1174]: caught signal SIGUSR1 (10), refresh retries
Nov  9 15:54:57 puissant nm-dispatcher[7833]: Sending network state change signal to nslcd...done.
Nov  9 15:54:58 puissant nslcd[1174]: caught signal SIGUSR1 (10), refresh retries
Nov  9 15:54:58 puissant nm-dispatcher[7833]: Sending network state change signal to nslcd...done.
Nov  9 15:55:44 puissant smartd[702]: Device: /dev/sda [SAT], SMART Prefailure Attribute: 3 Spin_Up_Time changed from 177 to 183
Nov  9 15:55:44 puissant smartd[702]: Device: /dev/sdb [USB JMicron], 38 Currently unreadable (pending) sectors
Nov  9 15:56:17 puissant nslcd[1174]: [63b9ea] <group/member="ir0n"> failed to bind to LDAP server ldapi:///192.168.2.214: Can't contact LDAP server: Connection refused
Nov  9 15:56:17 puissant nslcd[1174]: [63b9ea] <group/member="ir0n"> no available LDAP server found: Can't contact LDAP server: Connection refused
Nov  9 15:56:17 puissant nslcd[1174]: [63b9ea] <group/member="ir0n"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 15:56:22 puissant NetworkManager[728]: <info>  sleep requested (sleeping: no  enabled: yes)
Nov  9 15:56:22 puissant NetworkManager[728]: <info>  sleeping...
Nov  9 15:56:22 puissant NetworkManager[728]: <info>  (eth0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Nov  9 15:56:22 puissant NetworkManager[728]: <info>  (eth0): canceled DHCP transaction, DHCP client pid 7881
Nov  9 15:56:22 puissant NetworkManager[728]: <info>  (eth0): DHCPv4 state changed bound -> done
Nov  9 15:56:22 puissant avahi-daemon[733]: Withdrawing address record for 192.168.2.230 on eth0.
Nov  9 15:56:22 puissant avahi-daemon[733]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.2.230.
Nov  9 15:56:22 puissant avahi-daemon[733]: Interface eth0.IPv4 no longer relevant for mDNS.
Nov  9 15:56:22 puissant avahi-daemon[733]: Withdrawing address record for fe80::960c:6dff:fe81:e825 on eth0.
Nov  9 15:56:22 puissant avahi-daemon[733]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::960c:6dff:fe81:e825.
Nov  9 15:56:22 puissant avahi-daemon[733]: Interface eth0.IPv6 no longer relevant for mDNS.
Nov  9 15:56:22 puissant NetworkManager[728]: <info>  NetworkManager state is now ASLEEP
Nov  9 15:56:22 puissant dbus[671]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Nov  9 15:56:22 puissant NetworkManager[728]: <info>  (eth0): link disconnected
Nov  9 15:56:22 puissant systemd[1]: Reached target Sleep.
Nov  9 15:56:22 puissant systemd[1]: Starting Suspend...
Nov  9 15:56:22 puissant systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov  9 15:56:22 puissant systemd-sleep[8036]: Suspending system...
Nov  9 15:56:22 puissant dbus[671]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov  9 15:56:22 puissant systemd[1]: Started Network Manager Script Dispatcher Service.
Nov  9 15:56:22 puissant nm-dispatcher: Dispatching action 'down' for eth0
Nov  9 15:56:25 puissant systemd-sleep[8036]: System resumed.
Nov  9 15:56:25 puissant systemd[1]: Started Suspend.
Nov  9 15:56:25 puissant systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Nov  9 15:56:25 puissant systemd[1]: Stopped target Sleep.
Nov  9 15:56:25 puissant systemd[1]: Reached target Suspend.
Nov  9 15:56:25 puissant systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service. Stopping, too.
Nov  9 15:56:25 puissant systemd[1]: Stopped target Suspend.
Nov  9 15:56:25 puissant systemd[1]: Started Run anacron jobs at resume.
Nov  9 15:56:25 puissant NetworkManager[728]: <info>  wake requested (sleeping: yes  enabled: yes)
Nov  9 15:56:25 puissant NetworkManager[728]: <info>  waking up...
Nov  9 15:56:25 puissant NetworkManager[728]: <info>  (eth1): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Nov  9 15:56:25 puissant systemd[1]: Started Run anacron jobs.
Nov  9 15:56:25 puissant NetworkManager[728]: <info>  (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov  9 15:56:25 puissant NetworkManager[728]: <info>  (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov  9 15:56:25 puissant NetworkManager[728]: <info>  NetworkManager state is now DISCONNECTED
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  (eth0): link connected
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  Auto-activating connection 'Connexion Ethernet 1'.
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  (eth0): Activation: starting connection 'Connexion Ethernet 1' (7b758612-c117-41f0-b7fc-9c1e17051d3c)
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  NetworkManager state is now CONNECTING
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov  9 15:56:27 puissant NetworkManager[728]: <info>  dhclient started with pid 8055
Nov  9 15:56:27 puissant dhclient[8055]: DHCPREQUEST of 192.168.2.230 on eth0 to 255.255.255.255 port 67
Nov  9 15:56:28 puissant dhclient[8055]: DHCPACK of 192.168.2.230 from 192.168.2.1
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    address 192.168.2.230
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    plen 24 (255.255.255.0)
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    gateway 192.168.2.1
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    server identifier 192.168.2.1
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    lease time 259200
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    nameserver '192.168.2.1'
Nov  9 15:56:28 puissant NetworkManager[728]: <info>    domain name 'home'
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  (eth0): DHCPv4 state changed unknown -> bound
Nov  9 15:56:28 puissant avahi-daemon[733]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.2.230.
Nov  9 15:56:28 puissant avahi-daemon[733]: New relevant interface eth0.IPv4 for mDNS.
Nov  9 15:56:28 puissant avahi-daemon[733]: Registering new address record for 192.168.2.230 on eth0.IPv4.
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  NetworkManager state is now CONNECTED_LOCAL
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  NetworkManager state is now CONNECTED_GLOBAL
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  Policy set 'Connexion Ethernet 1' (eth0) as default for IPv4 routing and DNS.
Nov  9 15:56:28 puissant NetworkManager[728]: <info>  (eth0): Activation: successful, device activated.
Nov  9 15:56:28 puissant dhclient[8055]: bound to 192.168.2.230 -- renewal in 118890 seconds.
Nov  9 15:56:28 puissant nm-dispatcher: Dispatching action 'up' for eth0
Nov  9 15:56:28 puissant avahi-daemon[733]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::960c:6dff:fe81:e825.
Nov  9 15:56:28 puissant avahi-daemon[733]: New relevant interface eth0.IPv6 for mDNS.
Nov  9 15:56:28 puissant avahi-daemon[733]: Registering new address record for fe80::960c:6dff:fe81:e825 on eth0.*.
Nov  9 15:56:29 puissant freshclam[704]: Received signal: wake up
Nov  9 15:56:29 puissant freshclam[704]: ClamAV update process started at Mon Nov  9 15:56:29 2015
Nov  9 15:56:30 puissant freshclam[704]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Nov  9 15:56:30 puissant freshclam[704]: daily.cld is up to date (version: 21049, sigs: 1673890, f-level: 63, builder: neo)
Nov  9 15:56:30 puissant freshclam[704]: bytecode.cld is up to date (version: 270, sigs: 46, f-level: 63, builder: shurley)
Nov  9 15:56:34 puissant nslcd[1174]: caught signal SIGUSR1 (10), refresh retries
Nov  9 15:56:34 puissant nm-dispatcher[8037]: Sending network state change signal to nslcd...done.
Nov  9 15:56:34 puissant nslcd[1174]: caught signal SIGUSR1 (10), refresh retries
Nov  9 15:56:34 puissant nm-dispatcher[8037]: Sending network state change signal to nslcd...done.
Nov  9 15:56:38 puissant clamd[737]: No stats for Database check - forcing reload
Nov  9 15:56:39 puissant clamd[737]: Reading databases from /var/lib/clamav
Nov  9 15:56:59 puissant clamd[737]: Database correctly reloaded (4092594 signatures)
Nov  9 15:58:41 puissant nslcd[1174]: [884adc] <authz="ir0n"> failed to bind to LDAP server ldapi:///192.168.2.214: Can't contact LDAP server: Connection refused
Nov  9 15:58:41 puissant nslcd[1174]: [884adc] <authz="ir0n"> no available LDAP server found: Can't contact LDAP server: Connection refused
Nov  9 16:01:20 puissant nslcd[1174]: [ead36b] <group/member="redis"> failed to bind to LDAP server ldapi:///192.168.2.214: Can't contact LDAP server: Connection refused
Nov  9 16:01:20 puissant nslcd[1174]: [ead36b] <group/member="redis"> no available LDAP server found: Can't contact LDAP server: Connection refused
Nov  9 16:01:20 puissant nslcd[1174]: [ead36b] <group/member="redis"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:07:49 puissant nslcd[1174]: [517796] <group/member="avahi"> failed to bind to LDAP server ldapi:///192.168.2.214: Can't contact LDAP server: Connection refused
Nov  9 16:07:49 puissant nslcd[1174]: [517796] <group/member="avahi"> no available LDAP server found: Can't contact LDAP server: Connection refused
Nov  9 16:07:49 puissant nslcd[1174]: [517796] <group/member="avahi"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:07:49 puissant nslcd[1174]: [0bd78f] <group/member="colord"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [0bd78f] <group/member="colord"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [3ea438] <group/member="dnsmasq"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [3ea438] <group/member="dnsmasq"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [55585c] <group/member="systemd-resolve"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [55585c] <group/member="systemd-resolve"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [a64e2a] <group/member="pulse"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [a64e2a] <group/member="pulse"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [2342ec] <group/member="systemd-network"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [2342ec] <group/member="systemd-network"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [487cb0] <group/member="messagebus"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [487cb0] <group/member="messagebus"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [4ed43b] <group/member="openldap"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [4ed43b] <group/member="openldap"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [5a06fb] <group/member="rtkit"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [5a06fb] <group/member="rtkit"> no available LDAP server found: Server is unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [d89a32] <group/member="geoclue"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [d89a32] <group/member="geoclue"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [e4ccaf] <group/member="mysql"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:07:49 puissant nslcd[1174]: [e4ccaf] <group/member="mysql"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:08:04 puissant nslcd[1174]: [6d8d3c] <group/member="nslcd"> failed to bind to LDAP server ldapi:///192.168.2.214: Can't contact LDAP server: Connection refused
Nov  9 16:08:04 puissant nslcd[1174]: [6d8d3c] <group/member="nslcd"> no available LDAP server found: Can't contact LDAP server: Connection refused
Nov  9 16:08:04 puissant nslcd[1174]: [6d8d3c] <group/member="nslcd"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [588f54] <group/member="www-data"> failed to bind to LDAP server ldapi:///192.168.2.214: Can't contact LDAP server: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [588f54] <group/member="www-data"> no available LDAP server found: Can't contact LDAP server: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [588f54] <group/member="www-data"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [2289ec] <group/member="www-data"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [2289ec] <group/member="www-data"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [e91b18] <group/member="www-data"> no available LDAP server found: Server is unavailable
Nov  9 16:08:19 puissant nslcd[1174]: [e91b18] <group/member="www-data"> no available LDAP server found: Server is unavailable
Nov  9 16:08:19 puissant nslcd[1174]: [437fdb] <group/member="www-data"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:08:19 puissant nslcd[1174]: [437fdb] <group/member="www-data"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
Nov  9 16:08:19 puissant nslcd[1174]: [44a45c] <group/member="www-data"> no available LDAP server found: Server is unavailable
Nov  9 16:08:19 puissant nslcd[1174]: [44a45c] <group/member="www-data"> no available LDAP server found: Server is unavailable
Nov  9 16:08:19 puissant nslcd[1174]: [fff902] <group/member="lightdm"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:08:19 puissant nslcd[1174]: [fff902] <group/member="lightdm"> no available LDAP server found: Server is unavailable: Connection refused
Nov  9 16:17:52 puissant systemd[1]: Created slice user-0.slice.
Nov  9 16:17:52 puissant systemd[1]: Starting User Manager for UID 0...
Nov  9 16:17:52 puissant systemd[1]: Started Session c2 of user root.
Nov  9 16:17:53 puissant systemd[8639]: Reached target Sockets.
Nov  9 16:17:53 puissant systemd[8639]: Removed slice Root Slice.
Nov  9 16:17:53 puissant systemd[8639]: Reached target Paths.
Nov  9 16:17:53 puissant systemd[8639]: Reached target Timers.
Nov  9 16:17:53 puissant systemd[8639]: Reached target Basic System.
Nov  9 16:17:53 puissant systemd[8639]: Reached target Default.
Nov  9 16:17:53 puissant systemd[8639]: Startup finished in 86ms.
Nov  9 16:17:53 puissant systemd[1]: Started User Manager for UID 0.
Nov  9 16:17:53 puissant systemd[1]: Stopping User Manager for UID 0...
Nov  9 16:17:53 puissant systemd[8639]: Reached target Shutdown.
Nov  9 16:17:53 puissant systemd[8639]: Stopped target Default.
Nov  9 16:17:53 puissant systemd[8639]: Stopped target Basic System.
Nov  9 16:17:53 puissant systemd[8639]: Stopped target Sockets.
Nov  9 16:17:53 puissant systemd[8639]: Stopped target Timers.
Nov  9 16:17:53 puissant systemd[8639]: Created slice Root Slice.
Nov  9 16:17:53 puissant systemd[8639]: Starting Exit the Session...
Nov  9 16:17:53 puissant systemd[8639]: Stopped target Paths.
Nov  9 16:17:53 puissant systemd[8639]: Received SIGRTMIN+24 from PID 8644 (kill).
Nov  9 16:17:53 puissant systemd[1]: Stopped User Manager for UID 0.
Nov  9 16:17:53 puissant systemd[1]: Removed slice user-0.slice.



dmesg

[  880.389648] PM: resume of devices complete after 181.521 msecs
[  882.114207] ata1.00: ACPI cmd e3/00:00:00:00:00:a0 (IDLE) succeeded
[  882.114211] ata1.00: ACPI cmd b1/c1:00:00:00:00:a0 (DEVICE CONFIGURATION OVERLAY) filtered out
[  882.114214] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[  882.128333] ata1.00: configured for UDMA/100
[  882.144234] ata1.01: configured for UDMA/66
[  882.168469] PM: Finishing wakeup.
[  882.168473] Restarting tasks ... done.
[  882.313097] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  882.320561] r8169 0000:05:09.0 eth0: link down
[  882.320583] r8169 0000:05:09.0 eth0: link down
[  882.320687] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  882.324605] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  882.372222] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  883.999435] r8169 0000:05:09.0 eth0: link up
[  883.999452] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1033.944051] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 1034.064032] usb 3-2: device descriptor read/64, error -71
[ 1344.984045] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 1345.104058] usb 3-2: device descriptor read/64, error -71
[ 1378.008042] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 1378.132059] usb 3-2: device descriptor read/64, error -71
[ 1645.016037] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 1645.136046] usb 3-2: device descriptor read/64, error -71
[ 1954.968050] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 1955.088049] usb 3-2: device descriptor read/64, error -71
[ 2264.984553] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 2265.104052] usb 3-2: device descriptor read/64, error -71
[ 2297.944039] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 2298.064053] usb 3-2: device descriptor read/64, error -71
[ 2575.960033] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 2576.080034] usb 3-2: device descriptor read/64, error -71
[ 2608.984030] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 2609.104031] usb 3-2: device descriptor read/64, error -71
[ 2861.975686] PM: Syncing filesystems ... done.
[ 2862.471530] PM: Preparing system for sleep (mem)
[ 2862.670125] Freezing user space processes ...
[ 2875.992029] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 2876.112028] usb 3-2: device descriptor read/64, error -71
[ 2876.400788] (elapsed 13.730 seconds) done.
[ 2876.400796] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 2876.402082] PM: Suspending system (mem)
[ 2876.402105] Suspending console(s) (use no_console_suspend to debug)
[ 2876.402959] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 2876.403173] sd 0:0:0:0: [sda] Stopping disk
[ 2876.452048] tpm_tis 00:06: Error (38) sending savestate before suspend
[ 2876.452059] __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x1b0 [tpm] returns 38
[ 2876.452065] dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 38
[ 2876.452068] PM: Device 00:06 failed to suspend: error 38
[ 2876.708115] PM: Some devices failed to suspend, or early wake event detected
[ 2876.711998] sd 0:0:0:0: [sda] Starting disk
[ 2876.877413] PM: resume of devices complete after 169.291 msecs
[ 2876.886682] PM: Finishing wakeup.
[ 2876.886684] Restarting tasks ...
[ 2876.897773] ata1.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
[ 2876.897784] ata1.01: ACPI cmd ef/03:43:00:00:00:b0 (SET FEATURES) filtered out
[ 2876.901515] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[ 2876.901525] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[ 2876.901820] ata1.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
[ 2876.908106] done.
[ 2877.035523] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 2877.044599] r8169 0000:05:09.0 eth0: link down
[ 2877.044649] r8169 0000:05:09.0 eth0: link down
[ 2877.044695] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 2877.047059] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 2877.079267] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 2878.570307] ata1.00: ACPI cmd e3/00:00:00:00:00:a0 (IDLE) succeeded
[ 2878.570318] ata1.00: ACPI cmd b1/c1:00:00:00:00:a0 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 2878.570325] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 2878.588342] ata1.00: configured for UDMA/100
[ 2878.604240] ata1.01: configured for UDMA/66
[ 2878.706747] r8169 0000:05:09.0 eth0: link up
[ 2878.706765] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 2889.932068] PM: Syncing filesystems ... done.
[ 2890.400452] PM: Preparing system for sleep (mem)
[ 2890.636474] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 2890.639024] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 2890.640148] PM: Suspending system (mem)
[ 2890.640169] Suspending console(s) (use no_console_suspend to debug)
[ 2890.640808] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 2890.641005] sd 0:0:0:0: [sda] Stopping disk
[ 2890.692047] tpm_tis 00:06: Error (38) sending savestate before suspend
[ 2890.692058] __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x1b0 [tpm] returns 38
[ 2890.692064] dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 38
[ 2890.692067] PM: Device 00:06 failed to suspend: error 38
[ 2890.948107] PM: Some devices failed to suspend, or early wake event detected
[ 2890.948586] sd 0:0:0:0: [sda] Starting disk
[ 2891.124410] ata1.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
[ 2891.124414] ata1.01: ACPI cmd ef/03:43:00:00:00:b0 (SET FEATURES) filtered out
[ 2891.130236] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[ 2891.130240] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[ 2891.130496] ata1.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
[ 2891.132166] PM: resume of devices complete after 184.053 msecs
[ 2892.582448] ata1.00: ACPI cmd e3/00:00:00:00:00:a0 (IDLE) succeeded
[ 2892.582452] ata1.00: ACPI cmd b1/c1:00:00:00:00:a0 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 2892.582455] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 2892.596331] ata1.00: configured for UDMA/100
[ 2892.612228] ata1.01: configured for UDMA/66
[ 2892.633166] PM: Finishing wakeup.
[ 2892.633170] Restarting tasks ... done.
[ 2892.755722] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 2892.764853] r8169 0000:05:09.0 eth0: link down
[ 2892.764926] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 2892.764982] r8169 0000:05:09.0 eth0: link down
[ 2892.769944] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 2892.828234] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 2894.418416] r8169 0000:05:09.0 eth0: link up
[ 2894.418434] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 3183.960058] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 3184.080048] usb 3-2: device descriptor read/64, error -71
[ 3492.952052] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 3493.076062] usb 3-2: device descriptor read/64, error -71
[ 3594.787679] PM: Syncing filesystems ... done.
[ 3595.179255] PM: Preparing system for sleep (mem)
[ 3595.408143] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 3595.410538] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 3595.411799] PM: Suspending system (mem)
[ 3595.411820] Suspending console(s) (use no_console_suspend to debug)
[ 3595.412592] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 3595.412791] sd 0:0:0:0: [sda] Stopping disk
[ 3595.464046] tpm_tis 00:06: Error (38) sending savestate before suspend
[ 3595.464057] __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x1b0 [tpm] returns 38
[ 3595.464063] dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 38
[ 3595.464066] PM: Device 00:06 failed to suspend: error 38
[ 3595.720121] PM: Some devices failed to suspend, or early wake event detected
[ 3595.724162] sd 0:0:0:0: [sda] Starting disk
[ 3595.878091] PM: resume of devices complete after 157.962 msecs
[ 3595.878946] PM: Finishing wakeup.
[ 3595.878949] Restarting tasks ...
[ 3595.919792] ata1.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
[ 3595.919801] ata1.01: ACPI cmd ef/03:43:00:00:00:b0 (SET FEATURES) filtered out
[ 3595.928464] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[ 3595.928473] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[ 3595.928580] done.
[ 3595.930715] ata1.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
[ 3597.605677] ata1.00: ACPI cmd e3/00:00:00:00:00:a0 (IDLE) succeeded
[ 3597.605688] ata1.00: ACPI cmd b1/c1:00:00:00:00:a0 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 3597.605694] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 3597.620348] ata1.00: configured for UDMA/100
[ 3597.636250] ata1.01: configured for UDMA/66
[ 3597.752292] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3597.760546] r8169 0000:05:09.0 eth0: link down
[ 3597.760604] r8169 0000:05:09.0 eth0: link down
[ 3597.760656] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3597.762949] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 3597.795646] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 3599.462198] r8169 0000:05:09.0 eth0: link up
[ 3599.462215] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 3688.404424] PM: Syncing filesystems ... done.
[ 3688.616449] PM: Preparing system for sleep (mem)
[ 3688.848637] Freezing user space processes ... (elapsed 0.004 seconds) done.
[ 3688.853318] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 3688.854593] PM: Suspending system (mem)
[ 3688.854613] Suspending console(s) (use no_console_suspend to debug)
[ 3688.855205] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 3688.855384] sd 0:0:0:0: [sda] Stopping disk
[ 3688.908051] tpm_tis 00:06: Error (38) sending savestate before suspend
[ 3688.908062] __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x1b0 [tpm] returns 38
[ 3688.908068] dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 38
[ 3688.908071] PM: Device 00:06 failed to suspend: error 38
[ 3689.160141] PM: Some devices failed to suspend, or early wake event detected
[ 3689.161387] sd 0:0:0:0: [sda] Starting disk
[ 3689.327464] ata1.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
[ 3689.327468] ata1.01: ACPI cmd ef/03:43:00:00:00:b0 (SET FEATURES) filtered out
[ 3689.340317] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[ 3689.340321] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[ 3689.340447] PM: resume of devices complete after 180.301 msecs
[ 3689.340636] ata1.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
[ 3691.138456] ata1.00: ACPI cmd e3/00:00:00:00:00:a0 (IDLE) succeeded
[ 3691.138460] ata1.00: ACPI cmd b1/c1:00:00:00:00:a0 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 3691.138462] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 3691.152334] ata1.00: configured for UDMA/100
[ 3691.168324] ata1.01: configured for UDMA/66
[ 3691.194453] PM: Finishing wakeup.
[ 3691.194457] Restarting tasks ... done.
[ 3691.351754] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3691.361214] r8169 0000:05:09.0 eth0: link down
[ 3691.361368] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3691.361426] r8169 0000:05:09.0 eth0: link down
[ 3691.373158] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 3691.424222] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 3693.019851] r8169 0000:05:09.0 eth0: link up
[ 3693.019867] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 3795.992049] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 3796.112046] usb 3-2: device descriptor read/64, error -71
[ 3828.952060] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 3829.072053] usb 3-2: device descriptor read/64, error -71
[ 4099.032029] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 4099.152026] usb 3-2: device descriptor read/64, error -71
[ 4405.976032] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 4406.096030] usb 3-2: device descriptor read/64, error -71
[ 4439.000035] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 4439.120032] usb 3-2: device descriptor read/64, error -71
[ 4715.992041] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 4716.116045] usb 3-2: device descriptor read/64, error -71
[ 4749.016059] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 4749.136034] usb 3-2: device descriptor read/64, error -71
[ 4822.675837] perf interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[ 5019.992043] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[ 5020.112048] usb 3-2: device descriptor read/64, error -71



Kool voila qui pourrait aider

Nov  9 15:56:25 puissant kernel: [ 3688.855205] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Nov  9 15:56:25 puissant kernel: [ 3688.855384] sd 0:0:0:0: [sda] Stopping disk
Nov  9 15:56:25 puissant kernel: [ 3688.908051] tpm_tis 00:06: Error (38) sending savestate before suspend
Nov  9 15:56:25 puissant kernel: [ 3688.908062] __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x1b0 [tpm] returns 38
Nov  9 15:56:25 puissant kernel: [ 3688.908068] dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 38
Nov  9 15:56:25 puissant kernel: [ 3688.908071] PM: Device 00:06 failed to suspend: error 38
Nov  9 15:56:25 puissant kernel: [ 3689.160141] PM: Some devices failed to suspend, or early wake event detected


Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#11 10-11-2015 00:03:53

Severian
Membre
Distrib. : Debian GNU/Linux 8.6 (jessie)
Noyau : Linux 4.6.0-0.bpo.1-amd64
(G)UI : Openbox 3.6.1-2
Inscription : 13-12-2014

Re : Probleme Mise en veille/ Hibernation/ Screensaver

tpm_tis

peut être une solution à essayer
http://askubuntu.com/questions/486329/t … -14-04-lts

sinon trouver qui est "Device 00:06" et lui faire la peau tongue

"il est urgent d'attendre" (bendia)
ob3-debian2-150x50.png

Hors ligne

#12 10-11-2015 00:16:00

Severian
Membre
Distrib. : Debian GNU/Linux 8.6 (jessie)
Noyau : Linux 4.6.0-0.bpo.1-amd64
(G)UI : Openbox 3.6.1-2
Inscription : 13-12-2014

Re : Probleme Mise en veille/ Hibernation/ Screensaver

tu as envie de rire ? (ou pas)
https://debian-facile.org/viewtopic.php … 27#p132427
petit extrais du résultat de ta commande dmesg

417-               intel_rng: you are certain that your system has a functional
418-               intel_rng: RNG, try using the 'no_fwh_detect' option.
419-[   10.103996] wmi: Mapper loaded
420-[   10.168613] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
421:[   10.224061] tpm_tis 00:06: 1.2 TPM (device-id 0x1001, rev-id 1)
422:[   10.272123] tpm_tis 00:06: Adjusting TPM timeout parameters.
423:[   10.320060] tpm_tis 00:06: TPM is disabled/deactivated (0x6)
424-[   10.380721] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
425-[   10.381131] r8169 0000:05:09.0 (unnamed net_device) (uninitialized): not PCI Express
426-[   10.381690] r8169 0000:05:09.0 eth0: RTL8169sb/8110sb at 0xffffc90002736000, 94:0c:6d:81:e8:25, XID 10000000 IRQ 18
427-[   10.381699] r8169 0000:05:09.0 eth0: jumbo features [frames: 7152 bytes, tx checksumming: ok]
--
670-[17127.882766] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0xffffc9000291c418
671-[17127.899129] [drm] ring test on 0 succeeded in 1 usecs
672-[17127.899135] [drm] ring test on 3 succeeded in 2 usecs
673-[17127.902390] sd 0:0:0:0: [sda] Starting disk
674:[17127.908048] tpm_tis 00:06: A TPM error (38) occurred continue selftest
675-[17128.075203] r8169 0000:05:09.0 eth0: link down
676-[17128.075254] [drm] ring test on 5 succeeded in 1 usecs
677-[17128.075258] [drm] UVD initialized successfully.
678-[17128.075296] [drm] ib test on ring 0 succeeded in 0 usecs
--
712-[73880.628107] PM: Entering mem sleep
713-[73880.628129] Suspending console(s) (use no_console_suspend to debug)
714-[73880.629079] sd 0:0:0:0: [sda] Synchronizing SCSI cache
715-[73880.629233] sd 0:0:0:0: [sda] Stopping disk
716:[73880.680048] tpm_tis 00:06: Error (38) sending savestate before suspend
717-[73880.680069] __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x1c0 [tpm] returns 38
718-[73880.680076] dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 38
719-[73880.680079] PM: Device 00:06 failed to suspend: error 38
720-[73880.720094] PM: Some devices failed to suspend, or early wake event detected
--
752-[280208.801416] PM: Entering mem sleep
753-[280208.801438] Suspending console(s) (use no_console_suspend to debug)
754-[280208.802492] sd 0:0:0:0: [sda] Synchronizing SCSI cache
755-[280208.802669] sd 0:0:0:0: [sda] Stopping disk
756:[280208.852048] tpm_tis 00:06: Error (38) sending savestate before suspend
757-[280208.852069] __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x1c0 [tpm] returns 38
758-[280208.852075] dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 38
759-[280208.852078] PM: Device 00:06 failed to suspend: error 38
760-[280208.892069] PM: Some devices failed to suspend, or early wake event detected
--
784-[393889.893503] PM: Entering mem sleep
785-[393889.893526] Suspending console(s) (use no_console_suspend to debug)
786-[393889.894572] sd 0:0:0:0: [sda] Synchronizing SCSI cache
787-[393889.894746] sd 0:0:0:0: [sda] Stopping disk
788:[393889.944048] tpm_tis 00:06: Error (38) sending savestate before suspend
789-[393889.944069] __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x1c0 [tpm] returns 38
790-[393889.944075] dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 38
791-[393889.944078] PM: Device 00:06 failed to suspend: error 38
792-[393889.984096] PM: Some devices failed to suspend, or early wake event detecte



pas nouveau le problème wink


"il est urgent d'attendre" (bendia)
ob3-debian2-150x50.png

Hors ligne

#13 10-11-2015 00:27:34

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Ya 3 solution sur ton lien !!! humm
Comment trouver qui est Device 00:06 que jle bute

Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#14 10-11-2015 00:36:49

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

[   10.224061] tpm_tis 00:06: 1.2 TPM (device-id 0x1001, rev-id 1)
[   10.272123] tpm_tis 00:06: Adjusting TPM timeout parameters.
[   10.320060] tpm_tis 00:06: TPM is disabled/deactivated (0x6)


Dans ce temps le tpm_tis semblait OK non ?

Effectivement Device 00:06 semble être mon Disque dur sda defec sad
sda: 39 C (10 errors!) sdb: 40 C (730 errors!)

Dernière modification par Ir0nsh007er (10-11-2015 00:38:45)


Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#15 10-11-2015 00:37:38

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Oups

Dernière modification par Ir0nsh007er (10-11-2015 00:38:23)


Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#16 10-11-2015 01:00:35

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Editer /etc/default/grub

avec

GRUB_CMDLINE_LINUX_DEFAULT="acpi=nomsi quiet splash"
GRUB_CMDLINE_LINUX="tpm_tis.interrupts=0"


Rien ne change prob tjrs présent !


Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#17 10-11-2015 01:58:45

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Device 00:06 = Drivers ACPI\BCM0102 - HP
Mon ACPI est S3 serait-ce du a cela car selon wikipedia il faut minimum S4 sad

Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#18 10-11-2015 02:11:48

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Bug#776478: firmware-linux-nonfree: tigon driver for a Broadcom ethernet card prevents the computer from suspending to RAM
Il n'y a pas de solution ???

Dernière modification par Ir0nsh007er (10-11-2015 02:16:40)


Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#19 10-11-2015 10:52:00

paskal
autobahn
Lieu : ailleurs
Inscription : 14-06-2011
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Je vois que c'est la version Version: 0.36+wheezy.1, ça me parait étonnant que ça te concerne.

I'd love to change the world
But I don't know what to do
So I'll leave it up to you...

logo-sur-fond.png

Hors ligne

#20 11-11-2015 06:52:25

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

quelle paquet que je donne le résultat de

apt-cache policy paquet_qui_bug


Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#21 11-11-2015 06:53:22

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

firmware-linux-nonfree:
  Installé : 20151018-2
  Candidat : 20151018-2

Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#22 11-11-2015 10:32:06

paskal
autobahn
Lieu : ailleurs
Inscription : 14-06-2011
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Le 0.36+wheezy.1, c'est celui de Wheezy.
Je n'y trouve pas BCM0102 :

* Broadcom BCM5703/BCM5704 TSO firmware (tigon/tg3_tso.bin)
* Broadcom BCM5701A0 firmware (tigon/tg3.bin)
* Broadcom BCM5705 TSO firmware (tigon/tg3_tso5.bin)


Pas non plus dans firmware-misc-nonfree (20151018-2)  neutral


I'd love to change the world
But I don't know what to do
So I'll leave it up to you...

logo-sur-fond.png

Hors ligne

#23 11-11-2015 10:56:12

Severian
Membre
Distrib. : Debian GNU/Linux 8.6 (jessie)
Noyau : Linux 4.6.0-0.bpo.1-amd64
(G)UI : Openbox 3.6.1-2
Inscription : 13-12-2014

Hors ligne

#24 11-11-2015 16:55:38

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Ouais hummm je ne suis pas seul et ca date de 2008 ce bug !!
Pas de patch depuis ??

Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

#25 11-11-2015 16:57:59

Ir0nsh007er
Membre
Lieu : Montréal, PQ, Canada
Distrib. : Debian GNU/Linux 9.0 Stretch/Sid
Noyau : 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x
(G)UI : Xfce 4.12.3
Inscription : 30-04-2015
Site Web

Re : Probleme Mise en veille/ Hibernation/ Screensaver

Pourtant le bug report est classé Severity: important et date de 28 Jan 2015

Moé avec mon P4: Intel(R) Pentium(R) 4 CPU 3.40GHz, Mémoire: 6G DDR2, Carte Graphique: NVIDIA Corp GT216 [GeForce GT 220] (rev a2)
Ir0nsh007er (49 72 30 6E 73 68 30 30 37 65 72).  Mon CV
Noob un jour, noob toujours cool
01001001 01110010 00110000 01101110 01110011 01101000 00110000 00110000 00110111 01100101 01110010

Hors ligne

Pied de page des forums