freeze après mise en veille et hibernation

16 réponses

HEGRON Florian

01/03/2011 à 20:50

--=-4zckk9dFY2QKN/buiSdE
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

Bonjour,

VoilÃ j'ai un gros problÃ¨me de "freeze" lorsque je mets en veille ou en
hibernation mon ordinateur (COMPAQ Presario A900). La mise en veille en
elle mÃªme se passe bien. Mais au redÃ©marrage, je tape le mot de passe de
la session verrouillÃ©e, et hop, l'ordinateur ne rÃ©ponds plus du tout
(image bloquÃ©e et impossible d'accÃ©der Ã la console).

Pour ceux qui savent lire le syslog (20:17 - mise en veille; 20:18 -
tentative de rÃ©veil) je le mets en dessous.
Et encore en dessous, mon lspci.
Si je dois faire un reportbug, je ne sais sur quel paquet.

Merci beaucoup

Florian HEGRON

Mar 1 20:17:21 MumuAndFlo anacron[4267]: Anacron 2.3 started on
2011-03-01
Mar 1 20:17:21 MumuAndFlo anacron[4267]: Normal exit (0 jobs run)
Mar 1 20:17:21 MumuAndFlo dhclient: Internet Systems Consortium DHCP
Client 4.1.1-P1
Mar 1 20:17:21 MumuAndFlo dhclient: Copyright 2004-2010 Internet
Systems Consortium.
Mar 1 20:17:21 MumuAndFlo dhclient: All rights reserved.
Mar 1 20:17:21 MumuAndFlo dhclient: For info, please visit
https://www.isc.org/software/dhcp/
Mar 1 20:17:21 MumuAndFlo dhclient:
Mar 1 20:17:21 MumuAndFlo dhclient: Listening on
LPF/ath0/00:23:4d:01:c3:55
Mar 1 20:17:21 MumuAndFlo dhclient: Sending on
LPF/ath0/00:23:4d:01:c3:55
Mar 1 20:17:22 MumuAndFlo dhclient: Sending on Socket/fallback
Mar 1 20:17:22 MumuAndFlo avahi-daemon[1278]: Withdrawing address
record for 192.168.1.2 on ath0.
Mar 1 20:17:22 MumuAndFlo avahi-daemon[1278]: Leaving mDNS multicast
group on interface ath0.IPv4 with address 192.168.1.2.
Mar 1 20:17:22 MumuAndFlo avahi-daemon[1278]: Interface ath0.IPv4 no
longer relevant for mDNS.
Mar 1 20:17:22 MumuAndFlo avahi-daemon[1278]: Interface ath0.IPv6 no
longer relevant for mDNS.
Mar 1 20:17:22 MumuAndFlo avahi-daemon[1278]: Leaving mDNS multicast
group on interface ath0.IPv6 with address fe80::223:4dff:fe01:c355.
Mar 1 20:17:22 MumuAndFlo avahi-daemon[1278]: Withdrawing address
record for fe80::223:4dff:fe01:c355 on ath0.
Mar 1 20:17:22 MumuAndFlo kernel: [ 1373.273338] ADDRCONF(NETDEV_UP):
ath0: link is not ready
Mar 1 20:17:22 MumuAndFlo kernel: [ 1373.277406]
ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
Mar 1 20:17:22 MumuAndFlo dhclient: Internet Systems Consortium DHCP
Client 4.1.1-P1
Mar 1 20:17:22 MumuAndFlo dhclient: Copyright 2004-2010 Internet
Systems Consortium.
Mar 1 20:17:22 MumuAndFlo dhclient: All rights reserved.
Mar 1 20:17:22 MumuAndFlo dhclient: For info, please visit
https://www.isc.org/software/dhcp/
Mar 1 20:17:22 MumuAndFlo dhclient:
Mar 1 20:17:22 MumuAndFlo dhclient: Listening on
LPF/eth0/00:1e:ec:89:19:be
Mar 1 20:17:22 MumuAndFlo dhclient: Sending on
LPF/eth0/00:1e:ec:89:19:be
Mar 1 20:17:22 MumuAndFlo dhclient: Sending on Socket/fallback
Mar 1 20:17:22 MumuAndFlo dhclient: DHCPRELEASE on eth0 to 192.168.1.1
port 67
Mar 1 20:17:22 MumuAndFlo avahi-autoipd(eth0)[2165]: Got SIGTERM,
quitting.
Mar 1 20:17:22 MumuAndFlo avahi-autoipd(eth0)[2165]: Callout STOP,
address 169.254.8.172 on interface eth0
Mar 1 20:17:22 MumuAndFlo avahi-daemon[1278]: Withdrawing address
record for 169.254.8.172 on eth0.
Mar 1 20:17:22 MumuAndFlo avahi-daemon[1278]: Leaving mDNS multicast
group on interface eth0.IPv4 with address 169.254.8.172.
Mar 1 20:17:22 MumuAndFlo avahi-daemon[1278]: Interface eth0.IPv4 no
longer relevant for mDNS.
Mar 1 20:17:22 MumuAndFlo dhclient: receive_packet failed on eth0:
Network is down
Mar 1 20:17:22 MumuAndFlo kernel: [ 1373.508604] eth0: link down
Mar 1 20:17:22 MumuAndFlo kernel: [ 1373.509346] ADDRCONF(NETDEV_UP):
eth0: link is not ready
Mar 1 20:17:22 MumuAndFlo dhclient: Internet Systems Consortium DHCP
Client 4.1.1-P1
Mar 1 20:17:22 MumuAndFlo dhclient: Copyright 2004-2010 Internet
Systems Consortium.
Mar 1 20:17:22 MumuAndFlo dhclient: All rights reserved.
Mar 1 20:17:22 MumuAndFlo dhclient: For info, please visit
https://www.isc.org/software/dhcp/
Mar 1 20:17:22 MumuAndFlo dhclient:
Mar 1 20:17:22 MumuAndFlo dhclient: Listening on
LPF/ath0/00:23:4d:01:c3:55
Mar 1 20:17:22 MumuAndFlo dhclient: Sending on
LPF/ath0/00:23:4d:01:c3:55
Mar 1 20:17:22 MumuAndFlo dhclient: Sending on Socket/fallback
Mar 1 20:17:22 MumuAndFlo kernel: [ 1373.601084] ADDRCONF(NETDEV_UP):
ath0: link is not ready
Mar 1 20:17:22 MumuAndFlo kernel: [ 1373.607129]
ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
Mar 1 20:17:22 MumuAndFlo dhclient: Internet Systems Consortium DHCP
Client 4.1.1-P1
Mar 1 20:17:22 MumuAndFlo dhclient: Copyright 2004-2010 Internet
Systems Consortium.
Mar 1 20:17:22 MumuAndFlo dhclient: All rights reserved.
Mar 1 20:17:22 MumuAndFlo dhclient: For info, please visit
https://www.isc.org/software/dhcp/
Mar 1 20:17:22 MumuAndFlo dhclient:
Mar 1 20:17:22 MumuAndFlo dhclient: Listening on
LPF/eth0/00:1e:ec:89:19:be
Mar 1 20:17:22 MumuAndFlo dhclient: Sending on
LPF/eth0/00:1e:ec:89:19:be
Mar 1 20:17:22 MumuAndFlo dhclient: Sending on Socket/fallback
Mar 1 20:17:22 MumuAndFlo dhclient: DHCPRELEASE on eth0 to 192.168.1.1
port 67
Mar 1 20:17:22 MumuAndFlo dhclient: send_packet: Network is unreachable
Mar 1 20:17:22 MumuAndFlo dhclient: send_packet: please consult README
file regarding broadcast address.
Mar 1 20:17:22 MumuAndFlo dhclient: receive_packet failed on eth0:
Network is down
Mar 1 20:17:22 MumuAndFlo kernel: [ 1373.706023] eth0: link down
Mar 1 20:17:22 MumuAndFlo kernel: [ 1373.706765] ADDRCONF(NETDEV_UP):
eth0: link is not ready
Mar 1 20:17:22 MumuAndFlo kernel: [ 1373.866322] PM: Syncing
filesystems ... done.
Mar 1 20:17:22 MumuAndFlo kernel: [ 1373.878136] PM: Preparing system
for mem sleep
Mar 1 20:18:21 MumuAndFlo kernel: [ 1374.152969] Freezing user space
processes ... (elapsed 0.00 seconds) done.
Mar 1 20:18:21 MumuAndFlo kernel: [ 1374.154062] Freezing remaining
freezable tasks ... (elapsed 0.00 seconds) done.
Mar 1 20:18:21 MumuAndFlo kernel: [ 1374.154119] PM: Entering mem sleep
Mar 1 20:18:21 MumuAndFlo kernel: [ 1374.154138] Suspending console(s)
(use no_console_suspend to debug)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1374.184050] sd 2:0:0:0: [sda]
Synchronizing SCSI cache
Mar 1 20:18:21 MumuAndFlo kernel: [ 1374.184173] sd 2:0:0:0: [sda]
Stopping disk
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.131265] ath_pci 0000:01:00.0:
PCI INT A disabled
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.176225] ata_piix 0000:00:1f.1:
PCI INT B disabled
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.176239] ehci_hcd 0000:00:1d.7:
PCI INT A disabled
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.176248] uhci_hcd 0000:00:1d.2:
PCI INT C disabled
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.176256] uhci_hcd 0000:00:1d.1:
PCI INT B disabled
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.176265] uhci_hcd 0000:00:1d.0:
PCI INT D disabled
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.280840] HDA Intel
0000:00:1b.0: PCI INT A disabled
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.380320] ACPI: Preparing to
enter system sleep state S3
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.382391] Disabling non-boot
CPUs ...
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.382410] CPU0 attaching NULL
sched-domain.
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.382413] CPU1 attaching NULL
sched-domain.
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.429029] CPU0 attaching NULL
sched-domain.
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.532030] CPU 1 is now offline
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.532033] SMP alternatives:
switching to UP code
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.537366] Back to C!
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU0: Thermal
monitoring enabled (TM1)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.537366] Enabling non-boot
CPUs ...
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.537366] SMP alternatives:
switching to SMP code
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.542420] Booting processor 1
APIC 0x1 ip 0x6000
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.537366] Initializing CPU#1
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU: L1 I cache: 32K,
L1 D cache: 32K
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU: L2 cache: 1024K
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU 1/0x1 -> Node 0
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU: Physical
Processor ID: 0
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU: Processor Core
ID: 1
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU1: Thermal
monitoring enabled (TM1)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.632107] CPU1: Intel(R)
Pentium(R) Dual CPU T2390 @ 1.86GHz stepping 0d
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.632163] CPU0 attaching NULL
sched-domain.
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.660035] CPU0 attaching
sched-domain:
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.660039] domain 0: span 0-1
level MC
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.660041] groups: 0 1
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.660046] CPU1 attaching
sched-domain:
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.660048] domain 0: span 0-1
level MC
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.660050] groups: 1 0
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.660556] CPU1 is up
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.660872] ACPI: Waking up from
system sleep state S3
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663038] i915 0000:00:02.0:
restoring config space at offset 0xf (was 0x100, writing 0x10b)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663048] i915 0000:00:02.0:
restoring config space at offset 0x8 (was 0x1, writing 0x30d1)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663053] i915 0000:00:02.0:
restoring config space at offset 0x6 (was 0xc, writing 0x8000000c)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663057] i915 0000:00:02.0:
restoring config space at offset 0x4 (was 0x4, writing 0x91000004)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663063] i915 0000:00:02.0:
restoring config space at offset 0x1 (was 0x900000, writing 0x900407)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663116] HDA Intel
0000:00:1b.0: restoring config space at offset 0xf (was 0x100, writing
0x10b)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663137] HDA Intel
0000:00:1b.0: restoring config space at offset 0x4 (was 0x4, writing
0x92400004)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663147] HDA Intel
0000:00:1b.0: restoring config space at offset 0x1 (was 0x100000,
writing 0x100002)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663182] pcieport 0000:00:1c.0:
restoring config space at offset 0xf (was 0x100, writing 0x10b)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663196] pcieport 0000:00:1c.0:
restoring config space at offset 0x9 (was 0x10001, writing 0x90f19001)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663202] pcieport 0000:00:1c.0:
restoring config space at offset 0x8 (was 0x0, writing 0x92309130)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663207] pcieport 0000:00:1c.0:
restoring config space at offset 0x7 (was 0x0, writing 0x2020)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663213] pcieport 0000:00:1c.0:
restoring config space at offset 0x6 (was 0x0, writing 0x10100)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663226] pcieport 0000:00:1c.0:
restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663290] uhci_hcd 0000:00:1d.0:
restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663324] uhci_hcd 0000:00:1d.1:
restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663359] uhci_hcd 0000:00:1d.2:
restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663403] ehci_hcd 0000:00:1d.7:
restoring config space at offset 0x1 (was 0x2900006, writing 0x2900002)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663438] pci 0000:00:1e.0:
restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663444] pci 0000:00:1e.0:
restoring config space at offset 0x8 (was 0x0, writing 0x91209120)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663450] pci 0000:00:1e.0:
restoring config space at offset 0x7 (was 0x22800000, writing
0x22801010)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663464] pci 0000:00:1e.0:
restoring config space at offset 0x1 (was 0x100000, writing 0x100007)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663552] ata_piix 0000:00:1f.1:
restoring config space at offset 0x1 (was 0x2800005, writing 0x2880005)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663599] ahci 0000:00:1f.2:
restoring config space at offset 0x1 (was 0x2b00007, writing 0x2b00407)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663689] ath_pci 0000:01:00.0:
restoring config space at offset 0xf (was 0x100, writing 0x10b)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663718] ath_pci 0000:01:00.0:
restoring config space at offset 0x4 (was 0x4, writing 0x91300004)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663725] ath_pci 0000:01:00.0:
restoring config space at offset 0x3 (was 0x0, writing 0x10)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663735] ath_pci 0000:01:00.0:
restoring config space at offset 0x1 (was 0x100000, writing 0x100007)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663796] 8139too 0000:02:01.0:
restoring config space at offset 0x5 (was 0x0, writing 0x91200000)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663802] 8139too 0000:02:01.0:
restoring config space at offset 0x4 (was 0x1, writing 0x1001)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663808] 8139too 0000:02:01.0:
restoring config space at offset 0x3 (was 0x0, writing 0x4000)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.663817] 8139too 0000:02:01.0:
restoring config space at offset 0x1 (was 0x2900000, writing 0x2900007)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.910092] i915 0000:00:02.0:
setting latency timer to 64
Mar 1 20:18:21 MumuAndFlo kernel: [ 1375.932495] [Firmware Bug]: ACPI:
ACPI brightness control misses _BQC function
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.028169] HDA Intel
0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.028177] HDA Intel
0000:00:1b.0: setting latency timer to 64
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.117857] uhci_hcd 0000:00:1d.0:
PCI INT D -> GSI 21 (level, low) -> IRQ 21
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.117864] uhci_hcd 0000:00:1d.0:
setting latency timer to 64
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.117896] usb usb2: root hub
lost power or was reset
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.117923] uhci_hcd 0000:00:1d.1:
PCI INT B -> GSI 20 (level, low) -> IRQ 20
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.117930] uhci_hcd 0000:00:1d.1:
setting latency timer to 64
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.117962] usb usb3: root hub
lost power or was reset
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.117988] uhci_hcd 0000:00:1d.2:
PCI INT C -> GSI 19 (level, low) -> IRQ 19
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.117995] uhci_hcd 0000:00:1d.2:
setting latency timer to 64
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.118027] usb usb4: root hub
lost power or was reset
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.118049] ehci_hcd 0000:00:1d.7:
PCI INT A -> GSI 23 (level, low) -> IRQ 23
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.118056] ehci_hcd 0000:00:1d.7:
setting latency timer to 64
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.118086] pci 0000:00:1e.0:
setting latency timer to 64
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.118098] ata_piix 0000:00:1f.1:
PCI INT B -> GSI 19 (level, low) -> IRQ 19
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.118103] ata_piix 0000:00:1f.1:
setting latency timer to 64
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.118129] ahci 0000:00:1f.2:
setting latency timer to 64
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.118211] ath_pci 0000:01:00.0:
PCI INT A -> GSI 16 (level, low) -> IRQ 16
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.118220] ath_pci 0000:01:00.0:
setting latency timer to 64
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.120118] eth0: link down
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.260102] sd 2:0:0:0: [sda]
Starting disk
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.328451] ata1.00: ACPI cmd
ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.328455] ata1.00: ACPI cmd
ef/03:22:00:00:00:a0 (SET FEATURES) filtered out
Mar 1 20:18:21 MumuAndFlo kernel: [ 1376.344353] ata1.00: configured
for MWDMA2
Mar 1 20:18:21 MumuAndFlo kernel: [ 1378.000081] ata3: SATA link up 1.5
Gbps (SStatus 113 SControl 300)
Mar 1 20:18:21 MumuAndFlo kernel: [ 1378.002843] ata3.00: ACPI cmd
ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Mar 1 20:18:21 MumuAndFlo kernel: [ 1378.005685] ata3.00: ACPI cmd
ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Mar 1 20:18:21 MumuAndFlo kernel: [ 1378.005713] ata3.00: configured
for UDMA/100
Mar 1 20:18:21 MumuAndFlo kernel: [ 1378.144081] usb 1-5: reset high
speed USB device using ehci_hcd and address 2
Mar 1 20:18:21 MumuAndFlo kernel: [ 1378.936081] usb 1-6: reset high
speed USB device using ehci_hcd and address 3
Mar 1 20:18:21 MumuAndFlo kernel: [ 1379.085367] PM: Finishing wakeup.
Mar 1 20:18:21 MumuAndFlo avahi-daemon[1278]: Joining mDNS multicast
group on interface ath0.IPv6 with address fe80::223:4dff:fe01:c355.
Mar 1 20:18:21 MumuAndFlo avahi-daemon[1278]: New relevant interface
ath0.IPv6 for mDNS.
Mar 1 20:18:21 MumuAndFlo avahi-daemon[1278]: Registering new address
record for fe80::223:4dff:fe01:c355 on ath0.*.
Mar 1 20:18:21 MumuAndFlo acpid: client 2127[0:0] has disconnected
Mar 1 20:18:21 MumuAndFlo acpid: client connected from 2127[0:0]
Mar 1 20:18:21 MumuAndFlo acpid: 1 client rule loaded
Mar 1 20:18:21 MumuAndFlo kernel: [ 1379.085370] Restarting tasks ...
done.
Mar 1 20:18:21 MumuAndFlo anacron[4441]: Anacron 2.3 started on
2011-03-01
Mar 1 20:18:21 MumuAndFlo anacron[4441]: Normal exit (0 jobs run)
Mar 1 20:18:23 MumuAndFlo anacron[4497]: Anacron 2.3 started on
2011-03-01
Mar 1 20:18:23 MumuAndFlo anacron[4497]: Normal exit (0 jobs run)
Mar 1 20:18:26 MumuAndFlo kernel: [ 1384.364079] ath0: no IPv6 routers
present

--=-4zckk9dFY2QKN/buiSdE
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.30.3">
</HEAD>
<BODY>
Bonjour, 
 
Voilà j'ai un gros problème de "freeze" lorsque je mets en veille ou en hibernation mon ordinateur (COMPAQ Presario A900). La mise en veille en elle même se passe bien. Mais au redémarrage, je tape le mot de passe de la session verrouillée, et hop, l'ordinateur ne réponds plus du tout (image bloquée et impossible d'accéder à la console). 
 
Pour ceux qui savent lire le syslog (20:17 - mise en veille; 20:18 - tentative de réveil) je le mets en dessous. 
Et encore en dessous, mon lspci. 
Si je dois faire un reportbug, je ne sais sur quel paquet. 
 
Merci beaucoup 
 
 
 
Florian HEGRON 
 
 
 
Mar  1 20:17:21 MumuAndFlo anacron[4267]: Anacron 2.3 started on 2011-03-01 
Mar  1 20:17:21 MumuAndFlo anacron[4267]: Normal exit (0 jobs run) 
Mar  1 20:17:21 MumuAndFlo dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1 
Mar  1 20:17:21 MumuAndFlo dhclient: Copyright 2004-2010 Internet Systems Consortium. 
Mar  1 20:17:21 MumuAndFlo dhclient: All rights reserved. 
Mar  1 20:17:21 MumuAndFlo dhclient: For info, please visit https://www.isc.org/software/dhcp/ 
Mar  1 20:17:21 MumuAndFlo dhclient: 
Mar  1 20:17:21 MumuAndFlo dhclient: Listening on LPF/ath0/00:23:4d:01:c3:55 
Mar  1 20:17:21 MumuAndFlo dhclient: Sending on   LPF/ath0/00:23:4d:01:c3:55 
Mar  1 20:17:22 MumuAndFlo dhclient: Sending on   Socket/fallback 
Mar  1 20:17:22 MumuAndFlo avahi-daemon[1278]: Withdrawing address record for 192.168.1.2 on ath0. 
Mar  1 20:17:22 MumuAndFlo avahi-daemon[1278]: Leaving mDNS multicast group on interface ath0.IPv4 with address 192.168.1.2. 
Mar  1 20:17:22 MumuAndFlo avahi-daemon[1278]: Interface ath0.IPv4 no longer relevant for mDNS. 
Mar  1 20:17:22 MumuAndFlo avahi-daemon[1278]: Interface ath0.IPv6 no longer relevant for mDNS. 
Mar  1 20:17:22 MumuAndFlo avahi-daemon[1278]: Leaving mDNS multicast group on interface ath0.IPv6 with address fe80::223:4dff:fe01:c355. 
Mar  1 20:17:22 MumuAndFlo avahi-daemon[1278]: Withdrawing address record for fe80::223:4dff:fe01:c355 on ath0. 
Mar  1 20:17:22 MumuAndFlo kernel: [ 1373.273338] ADDRCONF(NETDEV_UP): ath0: link is not ready 
Mar  1 20:17:22 MumuAndFlo kernel: [ 1373.277406] ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready 
Mar  1 20:17:22 MumuAndFlo dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1 
Mar  1 20:17:22 MumuAndFlo dhclient: Copyright 2004-2010 Internet Systems Consortium. 
Mar  1 20:17:22 MumuAndFlo dhclient: All rights reserved. 
Mar  1 20:17:22 MumuAndFlo dhclient: For info, please visit https://www.isc.org/software/dhcp/ 
Mar  1 20:17:22 MumuAndFlo dhclient: 
Mar  1 20:17:22 MumuAndFlo dhclient: Listening on LPF/eth0/00:1e:ec:89:19:be 
Mar  1 20:17:22 MumuAndFlo dhclient: Sending on   LPF/eth0/00:1e:ec:89:19:be 
Mar  1 20:17:22 MumuAndFlo dhclient: Sending on   Socket/fallback 
Mar  1 20:17:22 MumuAndFlo dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67 
Mar  1 20:17:22 MumuAndFlo avahi-autoipd(eth0)[2165]: Got SIGTERM, quitting. 
Mar  1 20:17:22 MumuAndFlo avahi-autoipd(eth0)[2165]: Callout STOP, address 169.254.8.172 on interface eth0 
Mar  1 20:17:22 MumuAndFlo avahi-daemon[1278]: Withdrawing address record for 169.254.8.172 on eth0. 
Mar  1 20:17:22 MumuAndFlo avahi-daemon[1278]: Leaving mDNS multicast group on interface eth0.IPv4 with address 169.254.8.172. 
Mar  1 20:17:22 MumuAndFlo avahi-daemon[1278]: Interface eth0.IPv4 no longer relevant for mDNS. 
Mar  1 20:17:22 MumuAndFlo dhclient: receive_packet failed on eth0: Network is down 
Mar  1 20:17:22 MumuAndFlo kernel: [ 1373.508604] eth0: link down 
Mar  1 20:17:22 MumuAndFlo kernel: [ 1373.509346] ADDRCONF(NETDEV_UP): eth0: link is not ready 
Mar  1 20:17:22 MumuAndFlo dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1 
Mar  1 20:17:22 MumuAndFlo dhclient: Copyright 2004-2010 Internet Systems Consortium. 
Mar  1 20:17:22 MumuAndFlo dhclient: All rights reserved. 
Mar  1 20:17:22 MumuAndFlo dhclient: For info, please visit https://www.isc.org/software/dhcp/ 
Mar  1 20:17:22 MumuAndFlo dhclient: 
Mar  1 20:17:22 MumuAndFlo dhclient: Listening on LPF/ath0/00:23:4d:01:c3:55 
Mar  1 20:17:22 MumuAndFlo dhclient: Sending on   LPF/ath0/00:23:4d:01:c3:55 
Mar  1 20:17:22 MumuAndFlo dhclient: Sending on   Socket/fallback 
Mar  1 20:17:22 MumuAndFlo kernel: [ 1373.601084] ADDRCONF(NETDEV_UP): ath0: link is not ready 
Mar  1 20:17:22 MumuAndFlo kernel: [ 1373.607129] ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready 
Mar  1 20:17:22 MumuAndFlo dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1 
Mar  1 20:17:22 MumuAndFlo dhclient: Copyright 2004-2010 Internet Systems Consortium. 
Mar  1 20:17:22 MumuAndFlo dhclient: All rights reserved. 
Mar  1 20:17:22 MumuAndFlo dhclient: For info, please visit https://www.isc.org/software/dhcp/ 
Mar  1 20:17:22 MumuAndFlo dhclient: 
Mar  1 20:17:22 MumuAndFlo dhclient: Listening on LPF/eth0/00:1e:ec:89:19:be 
Mar  1 20:17:22 MumuAndFlo dhclient: Sending on   LPF/eth0/00:1e:ec:89:19:be 
Mar  1 20:17:22 MumuAndFlo dhclient: Sending on   Socket/fallback 
Mar  1 20:17:22 MumuAndFlo dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67 
Mar  1 20:17:22 MumuAndFlo dhclient: send_packet: Network is unreachable 
Mar  1 20:17:22 MumuAndFlo dhclient: send_packet: please consult README file regarding broadcast address. 
Mar  1 20:17:22 MumuAndFlo dhclient: receive_packet failed on eth0: Network is down 
Mar  1 20:17:22 MumuAndFlo kernel: [ 1373.706023] eth0: link down 
Mar  1 20:17:22 MumuAndFlo kernel: [ 1373.706765] ADDRCONF(NETDEV_UP): eth0: link is not ready 
Mar  1 20:17:22 MumuAndFlo kernel: [ 1373.866322] PM: Syncing filesystems ... done. 
Mar  1 20:17:22 MumuAndFlo kernel: [ 1373.878136] PM: Preparing system for mem sleep 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1374.152969] Freezing user space processes ... (elapsed 0.00 seconds) done. 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1374.154062] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1374.154119] PM: Entering mem sleep 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1374.154138] Suspending console(s) (use no_console_suspend to debug) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1374.184050] sd 2:0:0:0: [sda] Synchronizing SCSI cache 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1374.184173] sd 2:0:0:0: [sda] Stopping disk 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.131265] ath_pci 0000:01:00.0: PCI INT A disabled 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.176225] ata_piix 0000:00:1f.1: PCI INT B disabled 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.176239] ehci_hcd 0000:00:1d.7: PCI INT A disabled 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.176248] uhci_hcd 0000:00:1d.2: PCI INT C disabled 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.176256] uhci_hcd 0000:00:1d.1: PCI INT B disabled 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.176265] uhci_hcd 0000:00:1d.0: PCI INT D disabled 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.280840] HDA Intel 0000:00:1b.0: PCI INT A disabled 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.380320] ACPI: Preparing to enter system sleep state S3 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.382391] Disabling non-boot CPUs ... 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.382410] CPU0 attaching NULL sched-domain. 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.382413] CPU1 attaching NULL sched-domain. 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.429029] CPU0 attaching NULL sched-domain. 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.532030] CPU 1 is now offline 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.532033] SMP alternatives: switching to UP code 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.537366] Back to C! 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU0: Thermal monitoring enabled (TM1) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.537366] Enabling non-boot CPUs ... 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.537366] SMP alternatives: switching to SMP code 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.542420] Booting processor 1 APIC 0x1 ip 0x6000 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.537366] Initializing CPU#1 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU: L1 I cache: 32K, L1 D cache: 32K 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU: L2 cache: 1024K 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU 1/0x1 -> Node 0 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU: Physical Processor ID: 0 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU: Processor Core ID: 1 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.537366] CPU1: Thermal monitoring enabled (TM1) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.632107] CPU1: Intel(R) Pentium(R) Dual  CPU  T2390  @ 1.86GHz stepping 0d 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.632163] CPU0 attaching NULL sched-domain. 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.660035] CPU0 attaching sched-domain: 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.660039]  domain 0: span 0-1 level MC 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.660041]   groups: 0 1 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.660046] CPU1 attaching sched-domain: 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.660048]  domain 0: span 0-1 level MC 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.660050]   groups: 1 0 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.660556] CPU1 is up 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.660872] ACPI: Waking up from system sleep state S3 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663038] i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663048] i915 0000:00:02.0: restoring config space at offset 0x8 (was 0x1, writing 0x30d1) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663053] i915 0000:00:02.0: restoring config space at offset 0x6 (was 0xc, writing 0x8000000c) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663057] i915 0000:00:02.0: restoring config space at offset 0x4 (was 0x4, writing 0x91000004) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663063] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900000, writing 0x900407) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663116] HDA Intel 0000:00:1b.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663137] HDA Intel 0000:00:1b.0: restoring config space at offset 0x4 (was 0x4, writing 0x92400004) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663147] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100002) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663182] pcieport 0000:00:1c.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663196] pcieport 0000:00:1c.0: restoring config space at offset 0x9 (was 0x10001, writing 0x90f19001) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663202] pcieport 0000:00:1c.0: restoring config space at offset 0x8 (was 0x0, writing 0x92309130) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663207] pcieport 0000:00:1c.0: restoring config space at offset 0x7 (was 0x0, writing 0x2020) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663213] pcieport 0000:00:1c.0: restoring config space at offset 0x6 (was 0x0, writing 0x10100) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663226] pcieport 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663290] uhci_hcd 0000:00:1d.0: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663324] uhci_hcd 0000:00:1d.1: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663359] uhci_hcd 0000:00:1d.2: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663403] ehci_hcd 0000:00:1d.7: restoring config space at offset 0x1 (was 0x2900006, writing 0x2900002) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663438] pci 0000:00:1e.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663444] pci 0000:00:1e.0: restoring config space at offset 0x8 (was 0x0, writing 0x91209120) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663450] pci 0000:00:1e.0: restoring config space at offset 0x7 (was 0x22800000, writing 0x22801010) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663464] pci 0000:00:1e.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100007) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663552] ata_piix 0000:00:1f.1: restoring config space at offset 0x1 (was 0x2800005, writing 0x2880005) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663599] ahci 0000:00:1f.2: restoring config space at offset 0x1 (was 0x2b00007, writing 0x2b00407) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663689] ath_pci 0000:01:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663718] ath_pci 0000:01:00.0: restoring config space at offset 0x4 (was 0x4, writing 0x91300004) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663725] ath_pci 0000:01:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663735] ath_pci 0000:01:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100007) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663796] 8139too 0000:02:01.0: restoring config space at offset 0x5 (was 0x0, writing 0x91200000) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663802] 8139too 0000:02:01.0: restoring config space at offset 0x4 (was 0x1, writing 0x1001) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663808] 8139too 0000:02:01.0: restoring config space at offset 0x3 (was 0x0, writing 0x4000) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.663817] 8139too 0000:02:01.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900007) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.910092] i915 0000:00:02.0: setting latency timer to 64 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1375.932495] [Firmware Bug]: ACPI: ACPI brightness control misses _BQC function 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.028169] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.028177] HDA Intel 0000:00:1b.0: setting latency timer to 64 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.117857] uhci_hcd 0000:00:1d.0: PCI INT D -> GSI 21 (level, low) -> IRQ 21 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.117864] uhci_hcd 0000:00:1d.0: setting latency timer to 64 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.117896] usb usb2: root hub lost power or was reset 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.117923] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 20 (level, low) -> IRQ 20 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.117930] uhci_hcd 0000:00:1d.1: setting latency timer to 64 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.117962] usb usb3: root hub lost power or was reset 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.117988] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 19 (level, low) -> IRQ 19 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.117995] uhci_hcd 0000:00:1d.2: setting latency timer to 64 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.118027] usb usb4: root hub lost power or was reset 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.118049] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.118056] ehci_hcd 0000:00:1d.7: setting latency timer to 64 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.118086] pci 0000:00:1e.0: setting latency timer to 64 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.118098] ata_piix 0000:00:1f.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.118103] ata_piix 0000:00:1f.1: setting latency timer to 64 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.118129] ahci 0000:00:1f.2: setting latency timer to 64 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.118211] ath_pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.118220] ath_pci 0000:01:00.0: setting latency timer to 64 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.120118] eth0: link down 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.260102] sd 2:0:0:0: [sda] Starting disk 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.328451] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.328455] ata1.00: ACPI cmd ef/03:22:00:00:00:a0 (SET FEATURES) filtered out 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1376.344353] ata1.00: configured for MWDMA2 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1378.000081] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1378.002843] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1378.005685] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1378.005713] ata3.00: configured for UDMA/100 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1378.144081] usb 1-5: reset high speed USB device using ehci_hcd and address 2 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1378.936081] usb 1-6: reset high speed USB device using ehci_hcd and address 3 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1379.085367] PM: Finishing wakeup. 
Mar  1 20:18:21 MumuAndFlo avahi-daemon[1278]: Joining mDNS multicast group on interface ath0.IPv6 with address fe80::223:4dff:fe01:c355. 
Mar  1 20:18:21 MumuAndFlo avahi-daemon[1278]: New relevant interface ath0.IPv6 for mDNS. 
Mar  1 20:18:21 MumuAndFlo avahi-daemon[1278]: Registering new address record for fe80::223:4dff:fe01:c355 on ath0.*. 
Mar  1 20:18:21 MumuAndFlo acpid: client 2127[0:0] has disconnected 
Mar  1 20:18:21 MumuAndFlo acpid: client connected from 2127[0:0] 
Mar  1 20:18:21 MumuAndFlo acpid: 1 client rule loaded 
Mar  1 20:18:21 MumuAndFlo kernel: [ 1379.085370] Restarting tasks ... done. 
Mar  1 20:18:21 MumuAndFlo anacron[4441]: Anacron 2.3 started on 2011-03-01 
Mar  1 20:18:21 MumuAndFlo anacron[4441]: Normal exit (0 jobs run) 
Mar  1 20:18:23 MumuAndFlo anacron[4497]: Anacron 2.3 started on 2011-03-01 
Mar  1 20:18:23 MumuAndFlo anacron[4497]: Normal exit (0 jobs run) 
Mar  1 20:18:26 MumuAndFlo kernel: [ 1384.364079] ath0: no IPv6 routers present 
 
 
 
 
 
</BODY>
</HTML>

--=-4zckk9dFY2QKN/buiSdE--

--
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: http://lists.debian.org/1299008592.3015.10.camel@MumuAndFlo

6 réponses

1 2

Bernard Schoenacker

05/03/2011 à 16:50

Le Sat, 05 Mar 2011 12:50:25 +0100,
a Ã©crit :
.....

Bonjour,

Maintenant, j'en ai ma claque de tes gÃ©missements et voici
ce que je constate :

Serait il possible de pouvoir rÃ©pondre Ã la suite du message
Ã©crit ...
Pour florian c'est : non

Serait il possible de pouvoir relire les instructions et de
les retranscrire ...

Pour florian c'est : non

Serait il possible de pouvoir rÃ©diger un courriel sans html

Pour florian c'est : non

Serait il possible de pouvoir respecter la pagination ...

Pour florian c'est : non

Voici ton programme :

-a) Relire et Ã©crire proprement ce qui est demandÃ©
-b) Ãcrire convenablement sur la liste sans employer de html
-c) AmmÃ©liore tes connaissances basiques en informatique
-d) Ãviter de crier "Ã§a marche pÃ´ et chais pÃ´ quoi"
-e) Essaye d'Ãªtre le plus clair et conscis possible
pour se faire comprendre ...

en premier :

apprendre les instructions de base pour pouvoir se
dÃ©patouiller sans interface graphique ....

en consÃ©quence :

-a) installer les outils nÃ©cessaires Ã l'administration
de ton poste de travail informatisÃ©

-b) mettre en place un ensemble de paquets pouvant Ãªtre employÃ©s
sans interface X11 (mode ncurses uniquement)

les outils prÃ©caunisÃ©s (liste non exaustive) :

-a) elinks || links || w3m || lynx
-b) mc(edit) || nano
-c) gpm ( pour la souris )
-d) ssh
-e) less || most
-f) egrep
-g) gawk & sed
-h) html2text & unhtml

attention :

je ne met pas vim ou emacs en avant pour un novice
qui vient de dÃ©barquer dans un monde plus vaste ...

c'est Ã l'utilisateur d'apprendre Ã s'en servir ...

remarque :

Personne n'a atteind son niveau actuel sans faire
d'effort ...

je te promet "du sang de la sueur et des larmes" avant
de pouvoir simplement dÃ©couvrir la pleine puissance de
linux ...

tu disposes de toutes les cartes en main et c'est Ã toi de faire
tes preuves pour vouloir progresser ...

pour ta culture gÃ©nÃ©rale :

http://fr.wikipedia.org/wiki/La_CathÃ©drale_et_le_Bazar

le systÃ¨me linux et linux in a nutshell :

http://www.librairiedialogues.fr/livre/997373-linux-in-a-nutshell-guide-de -reference-jessica-perry-hekman-o-reilly-and-associates-inc--o-reilly

http://www.delafond.org/survielinux/

en plus comme tu es dans une Ã©cole, il faudrais voir avec
la documentaliste pour avoir accÃ¨s Ã la bibliothÃ¨que
universitaire ...

rÃ©fÃ©rences :

http://fr.wikipedia.org/wiki/Centre_de_documentation_et_dâinformat ion_en_Ã©tablissement_scolaire

prend le temps de te documenter et Ã©vite de foncer tout droit et
tÃªte baissÃ©e ou tu ira tout seul dans le bac Ã gravier
au premier tournant ...

exemples (pris sur la liste) :

-a) acpi
-b) menus gnome

alors, Ã partir de maintenant tu serres les dents et tu avances
Ã ton rythme ...

l'ensemble des lecteurs de cette liste ne peuvent pas deviner
tes errements et autres soucis de conduite de ton poste de
travail ...

Pour conclure, la courbe d'aprentissage entre un utilisateur
autonome :

-a) maÃ®trsise des logiciels basiques et du systÃ¨me d'exploitation
microsoft : 6 mois

-b) maÃ®trsise des logiciels basiques et du systÃ¨me d'exploitation
linux : 3 ans

et c'est Ã mÃ©diter et Ã prendre en compte ....

je le rÃ©pÃ¨te :

"C'EST Ã TOI DE JOUER DE TOUTES LES CARTES DONT TU DISPOSES"

slt
bernard

--
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: http://lists.debian.org/

Le Sat, 05 Mar 2011 12:50:25 +0100,
hogren@iiiha.com a Ã©crit :
.....

Bonjour,

Maintenant, j'en ai ma claque de tes gÃ©missements et voici
ce que je constate :

Serait il possible de pouvoir rÃ©pondre Ã la suite du message
Ã©crit ...
Pour florian c'est : non

Serait il possible de pouvoir relire les instructions et de
les retranscrire ...

Pour florian c'est : non

Serait il possible de pouvoir rÃ©diger un courriel sans html

Pour florian c'est : non

Serait il possible de pouvoir respecter la pagination ...

Pour florian c'est : non

Voici ton programme :

-a) Relire et Ã©crire proprement ce qui est demandÃ©
-b) Ãcrire convenablement sur la liste sans employer de html
-c) AmmÃ©liore tes connaissances basiques en informatique
-d) Ãviter de crier "Ã§a marche pÃ´ et chais pÃ´ quoi"
-e) Essaye d'Ãªtre le plus clair et conscis possible
pour se faire comprendre ...

en premier :

apprendre les instructions de base pour pouvoir se
dÃ©patouiller sans interface graphique ....

en consÃ©quence :

-a) installer les outils nÃ©cessaires Ã l'administration
de ton poste de travail informatisÃ©

-b) mettre en place un ensemble de paquets pouvant Ãªtre employÃ©s
sans interface X11 (mode ncurses uniquement)

les outils prÃ©caunisÃ©s (liste non exaustive) :

-a) elinks || links || w3m || lynx
-b) mc(edit) || nano
-c) gpm ( pour la souris )
-d) ssh
-e) less || most
-f) egrep
-g) gawk & sed
-h) html2text & unhtml

attention :

je ne met pas vim ou emacs en avant pour un novice
qui vient de dÃ©barquer dans un monde plus vaste ...

c'est Ã l'utilisateur d'apprendre Ã s'en servir ...

remarque :

Personne n'a atteind son niveau actuel sans faire
d'effort ...

je te promet "du sang de la sueur et des larmes" avant
de pouvoir simplement dÃ©couvrir la pleine puissance de
linux ...

tu disposes de toutes les cartes en main et c'est Ã toi de faire
tes preuves pour vouloir progresser ...

pour ta culture gÃ©nÃ©rale :

http://fr.wikipedia.org/wiki/La_CathÃ©drale_et_le_Bazar

le systÃ¨me linux et linux in a nutshell :

http://www.librairiedialogues.fr/livre/997373-linux-in-a-nutshell-guide-de -reference-jessica-perry-hekman-o-reilly-and-associates-inc--o-reilly

http://www.delafond.org/survielinux/

en plus comme tu es dans une Ã©cole, il faudrais voir avec
la documentaliste pour avoir accÃ¨s Ã la bibliothÃ¨que
universitaire ...

rÃ©fÃ©rences :

http://fr.wikipedia.org/wiki/Centre_de_documentation_et_dâinformat ion_en_Ã©tablissement_scolaire

prend le temps de te documenter et Ã©vite de foncer tout droit et
tÃªte baissÃ©e ou tu ira tout seul dans le bac Ã gravier
au premier tournant ...

exemples (pris sur la liste) :

-a) acpi
-b) menus gnome

alors, Ã partir de maintenant tu serres les dents et tu avances
Ã ton rythme ...

l'ensemble des lecteurs de cette liste ne peuvent pas deviner
tes errements et autres soucis de conduite de ton poste de
travail ...

Pour conclure, la courbe d'aprentissage entre un utilisateur
autonome :

-a) maÃ®trsise des logiciels basiques et du systÃ¨me d'exploitation
microsoft : 6 mois

-b) maÃ®trsise des logiciels basiques et du systÃ¨me d'exploitation
linux : 3 ans

et c'est Ã mÃ©diter et Ã prendre en compte ....

je le rÃ©pÃ¨te :

"C'EST Ã TOI DE JOUER DE TOUTES LES CARTES DONT TU DISPOSES"

slt
bernard

--
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: http://lists.debian.org/20110305164452.188bde3c.bernard.schoenacker_free.fr@hamtaro

Vous avez filtré cet utilisateur ! Consultez son message

manuk7

05/03/2011 à 17:40

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le 01/03/2011 20:43, HEGRON Florian a écrit :

Bonjour,

Voilà j'ai un gros problème de "freeze" lorsque je mets en veille ou en
hibernation mon ordinateur (COMPAQ Presario A900). La mise en veille en
elle même se passe bien. Mais au redémarrage, je tape le mot de passe de
la session verrouillée, et hop, l'ordinateur ne réponds plus du tout
(image bloquée et impossible d'accéder à la console).

Pour ceux qui savent lire le syslog (20:17 - mise en veille; 20:18 -
tentative de réveil) je le mets en dessous.
Et encore en dessous, mon lspci.
Si je dois faire un reportbug, je ne sais sur quel paquet.

Merci beaucoup

[...]

Bonjour,

Je ne sais pas quelle interface graphique tu utilises (probablement
Gnome ?), ni quel outil elle appelle derrière la fonction veille.
Cependant par un moment j'utilisais s2ram (paquet uswsusp) pour passer
en veille, et ça freezait (généralement quelques minutes après la sortie
de veille). On m'a alors conseillé d'utiliser pm-suspend (paquet
pm-utils), et je n'avais plus de problème de freeze ensuite.

Tu peut donc essayer de passer en veille avec pm-suspend (depuis une
console en root) et voir si ça freeze aussi au réveil.

Par curiosité, le réseau fonctionne encore après le freeze ? Sinon
comment fais tu pour récupérer le syslog ?

Manuel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1yY+0ACgkQnyDZfoiOigkBNQCfQk3nPPgUWDcK2e9iS85C+25o
oOkAoLFQ7hpqcSoSuZTMzC0zXUt0Dw+0
=3+yl
-----END PGP SIGNATURE-----

--
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: http://lists.debian.org/

Daniel Caillibaud

15/03/2011 à 10:30

Le 04/03/11 Ã 23:15, Bernard Schoenacker a Ã©crit :
BS> dpkg -l |grep ii |grep acpi | awk '{print $2" "$3}'>>list-pkg-acpi.txt

Je tombe lÃ -dessus par hasard et tardivement, mais je me permet de sug gÃ©rer

dpkg -l |awk '/ii.*acpi/ {print $2 " " $3}' >> list-pkg-acpi.txt
ou (plus lent car aptitude plus lourd, mais syntaxe peut-Ãªtre plus sim ple Ã mÃ©moriser)
aptitude search acpi~i >> list-pkg-acpi.txt

--
Daniel

Quand on regarde le ciel dans l'eau, on voit les poissons dans les arbres.
Sancho P.

--
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: http://lists.debian.org/

hogren

26/03/2011 à 14:10

Bonjour, tout d'abord désolé du temps d'absence. Je n'ai que très de
temps pour "bidouiller" sur cet ordinateur.

On Tue, 15 Mar 2011 10:28:46 +0100, Daniel Caillibaud wrote:

dpkg -l |awk '/ii.*acpi/ {print " " }' >> list-pkg-acpi.txt
ou (plus lent car aptitude plus lourd, mais syntaxe peut-être plus
simple à mémoriser)
aptitude search acpi~i >> list-pkg-acpi.txt

Voici mon fichier list-pkg-acpi.txt :
acpi 1.5-2
acpi-fakekey 0.137-5
acpi-support 0.137-5
acpi-support-base 0.137-5
acpid 1:2.0.7-1

On Sat, 05 Mar 2011 17:25:18 +0100, manuk7 wrote:

Cependant par un moment j'utilisais s2ram (paquet uswsusp) pour
passer en veille, et ça freezait (généralement quelques minutes après
la sortie de veille). On m'a alors conseillé d'utiliser pm-suspend
(paquet pm-utils), et je n'avais plus de problème de freeze ensuite.

J'ai regardé, en console, la commande s2ram est introuvable et le
paquet uswsusp n'existe pas sur les dêpots. En revanche pm-suspend est
présent. J'en déduit donc que c'est celui qui est utilisé.

Sinon je continue à faire des tests. Merci pour votre aide !

Florian HEGRON

--
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: http://lists.debian.org/

hogren

26/03/2011 à 14:50

Bonjour,

Après avoir eu le temps de "bidouiller" comme expliqué dans mon
précédent message, J'ai trouvé une solution.
Entre le probleme de manuk7 et le problème inverse cité ici,
http://bugs.debian.org/cgi-bin/bugreport.cgi?bugV1877 (dont la
solution ne marche pas chez moi, car ce n'est pas le même modèle de pc
(ni la même marque)), j'ai remarqué que ce pour qui ça ne marchait pas
avec pm-suspend, cela fonctionnait avec s2ram, et vice et versa.

J'ai donc pris sur les dếpots sid le paquet uswsusp et je peux
désinstallé désormais pm-utils.

Reste plus qu'à me documenter pour savoir comment remplacer le chemin
du bouton "mettre en veille" de gnome.

Merci à tous,

Amicalement,

Florian HEGRON

--
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: http://lists.debian.org/

Bernard Schoenacker

26/03/2011 à 15:50

Bonjour,

AprÃ¨s avoir eu le temps de "bidouiller" comme expliquÃ© dans mo n
prÃ©cÃ©dent message, J'ai trouvÃ© une solution.
Entre le probleme de manuk7 et le problÃ¨me inverse citÃ© ici,
http://bugs.debian.org/cgi-bin/bugreport.cgi?bugV1877 (dont la
solution ne marche pas chez moi, car ce n'est pas le mÃªme modÃ¨ le de
pc (ni la mÃªme marque)), j'ai remarquÃ© que ce pour qui Ã§a ne marchait
pas avec pm-suspend, cela fonctionnait avec s2ram, et vice et versa.

J'ai donc pris sur les dáº¿pots sid le paquet uswsusp et je peux
dÃ©sinstallÃ© dÃ©sormais pm-utils.

Reste plus qu'Ã me documenter pour savoir comment remplacer le
chemin du bouton "mettre en veille" de gnome.

Merci Ã tous,

Amicalement,

Florian HEGRON

Bonjour,

Enfin un message encourageant et indiquant l'Ã©volution positive
et les progrÃ¨s du novice ...

FÃ©licitation, il est dans la bonne voie

slt
bernard

--
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: http://lists.debian.org/

1 2

freeze après mise en veille et hibernation

6 réponses

Veuillez sélectionner un problème