You are not logged in.

Pages: 1

#1 2011-08-09 13:36:05

fengya
Member
Registered: 2011-04-29
Posts: 24

network problem after sleep

when i call back my computer from sleep, sometimes the network  can't work, but not everytime.

can you give me some suggestions.thx

Offline

#2 2011-08-09 13:36:50

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: network problem after sleep

Suggestion number one: post some more info: logs etc.

Offline

#3 2011-08-09 13:53:01

fengya
Member
Registered: 2011-04-29
Posts: 24

Re: network problem after sleep

karol wrote:

Suggestion number one: post some more info: logs etc.

in fact, i don't know which log i should post...
i think it just the network card didn't work after sleep and which log ?

Offline

#4 2011-08-09 13:57:14

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: network problem after sleep

The kernel.log should have some helpful info.
You can check using 'ip addr' which interfaces are available after waking your computer. If the one you use it's not there, the card is still asleep or at least the module isn't loaded. If the interface is there but it's not running, the problem lies elsewhere.

Offline

#5 2011-08-09 14:23:28

fengya
Member
Registered: 2011-04-29
Posts: 24

Re: network problem after sleep

ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:26:22:a5:e5:50 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::226:22ff:fea5:e550/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:21:00:f5:ec:20 brd ff:ff:ff:ff:ff:ff
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:26:22:a5:e5:50 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:21:00:f5:ec:20 brd ff:ff:ff:ff:ff:ff

the difference is eth0

Last edited by fengya (2011-08-09 15:11:16)

Offline

#6 2011-08-09 15:10:14

fengya
Member
Registered: 2011-04-29
Posts: 24

Re: network problem after sleep

kernel.log

9 23:01:08 localhost kernel: [  200.806774] ehci_hcd 0000:00:1a.7: restoring config space at offset 0xf (was 0x300, writing 0x30b)
Aug  9 23:01:08 localhost kernel: [  200.806802] ehci_hcd 0000:00:1a.7: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900002)
Aug  9 23:01:08 localhost kernel: [  200.806890] ehci_hcd 0000:00:1a.7: PME# disabled
Aug  9 23:01:08 localhost kernel: [  200.806905] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Aug  9 23:01:08 localhost kernel: [  200.806917] ehci_hcd 0000:00:1a.7: setting latency timer to 64
Aug  9 23:01:08 localhost kernel: [  200.838638] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Aug  9 23:01:08 localhost kernel: [  200.838647] uhci_hcd 0000:00:1a.0: setting latency timer to 64
Aug  9 23:01:08 localhost kernel: [  200.876986] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Aug  9 23:01:08 localhost kernel: [  200.877000] uhci_hcd 0000:00:1a.1: setting latency timer to 64
Aug  9 23:01:08 localhost kernel: [  200.918914] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 22 (level, low) -> IRQ 22
Aug  9 23:01:08 localhost kernel: [  200.918923] uhci_hcd 0000:00:1d.1: setting latency timer to 64
Aug  9 23:01:08 localhost kernel: [  200.956911] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Aug  9 23:01:08 localhost kernel: [  200.956924] uhci_hcd 0000:00:1d.2: setting latency timer to 64
Aug  9 23:01:09 localhost kernel: [  201.743352] r8169 0000:04:00.0: eth0: link up
Aug  9 23:01:09 localhost kernel: [  201.743633] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug  9 23:01:15 localhost kernel: [  207.903953] r8169 0000:04:00.0: PME# enabled
Aug  9 23:01:16 localhost kernel: [  209.016125] EXT4-fs (sda5): re-mounted. Opts: commit=0
Aug  9 23:01:16 localhost kernel: [  209.019173] EXT4-fs (sda6): re-mounted. Opts: commit=0
Aug  9 23:01:39 localhost kernel: [  212.113645] PM: Syncing filesystems ... done.
Aug  9 23:01:39 localhost kernel: [  212.115603] PM: Preparing system for mem sleep
Aug  9 23:01:39 localhost kernel: [  212.115621] Freezing user space processes ... (elapsed 0.01 seconds) done.
Aug  9 23:01:39 localhost kernel: [  212.130117] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Aug  9 23:01:39 localhost kernel: [  212.143442] PM: Entering mem sleep
Aug  9 23:01:39 localhost kernel: [  212.143480] Suspending console(s) (use no_console_suspend to debug)
Aug  9 23:01:39 localhost kernel: [  212.186798] r8169 0000:04:00.0: PME# disabled
Aug  9 23:01:39 localhost kernel: [  212.187378] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Aug  9 23:01:39 localhost kernel: [  212.223453] jmb38x_ms 0000:05:00.3: PCI INT A disabled
Aug  9 23:01:39 localhost kernel: [  212.223749] wl 0000:03:00.0: PCI INT A disabled
Aug  9 23:01:39 localhost kernel: [  212.223767] sdhci-pci 0000:05:00.0: PCI INT A disabled
Aug  9 23:01:39 localhost kernel: [  212.223867] ehci_hcd 0000:00:1d.7: PCI INT A disabled
Aug  9 23:01:39 localhost kernel: [  212.223880] uhci_hcd 0000:00:1d.2: PCI INT C disabled
Aug  9 23:01:39 localhost kernel: [  212.223893] uhci_hcd 0000:00:1d.1: PCI INT B disabled
Aug  9 23:01:39 localhost kernel: [  212.223906] uhci_hcd 0000:00:1d.0: PCI INT A disabled
Aug  9 23:01:39 localhost kernel: [  212.224497] ehci_hcd 0000:00:1a.7: PCI INT C disabled
Aug  9 23:01:39 localhost kernel: [  212.224508] uhci_hcd 0000:00:1a.1: PCI INT B disabled
Aug  9 23:01:39 localhost kernel: [  212.224517] uhci_hcd 0000:00:1a.0: PCI INT A disabled
Aug  9 23:01:39 localhost kernel: [  212.232994] sd 0:0:0:0: [sda] Stopping disk
Aug  9 23:01:39 localhost kernel: [  212.326866] HDA Intel 0000:00:1b.0: PCI INT B disabled
Aug  9 23:01:39 localhost kernel: [  212.370005] HDA Intel 0000:00:1b.0: power state changed by ACPI to D3
Aug  9 23:01:39 localhost kernel: [  213.253357] PM: suspend of devices complete after 1066.179 msecs
Aug  9 23:01:39 localhost kernel: [  213.253772] r8169 0000:04:00.0: PME# enabled
Aug  9 23:01:39 localhost kernel: [  213.283339] r8169 0000:04:00.0: wake-up capability enabled by ACPI
Aug  9 23:01:39 localhost kernel: [  213.323474] PM: late suspend of devices complete after 70.112 msecs
Aug  9 23:01:39 localhost kernel: [  213.323737] ACPI: Preparing to enter system sleep state S3
Aug  9 23:01:39 localhost kernel: [  213.323892] PM: Saving platform NVS memory
Aug  9 23:01:39 localhost kernel: [  213.324212] Disabling non-boot CPUs ...
Aug  9 23:01:39 localhost kernel: [  213.426677] CPU 1 is now offline
Aug  9 23:01:39 localhost kernel: [  213.426958] ACPI: Low-level resume complete
Aug  9 23:01:39 localhost kernel: [  213.426958] PM: Restoring platform NVS memory
Aug  9 23:01:39 localhost kernel: [  213.426958] Enabling non-boot CPUs ...
Aug  9 23:01:39 localhost kernel: [  213.433818] Booting Node 0 Processor 1 APIC 0x1
Aug  9 23:01:39 localhost kernel: [  213.433820] smpboot cpu 1: start_ip = 9a000
Aug  9 23:01:39 localhost kernel: [  213.325562] Initializing CPU#1
Aug  9 23:01:39 localhost kernel: [  213.534104] Switched to NOHz mode on CPU #1
Aug  9 23:01:39 localhost kernel: [  213.537913] NMI watchdog enabled, takes one hw-pmu counter.
Aug  9 23:01:39 localhost kernel: [  213.545769] CPU1 is up
Aug  9 23:01:39 localhost kernel: [  213.547138] ACPI: Waking up from system sleep state S3
Aug  9 23:01:39 localhost kernel: [  213.560317] pcieport 0000:00:01.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Aug  9 23:01:39 localhost kernel: [  213.560364] uhci_hcd 0000:00:1a.0: restoring config space at offset 0x1 (was 0x2900005, writing 0x2900001)
Aug  9 23:01:39 localhost kernel: [  213.560406] uhci_hcd 0000:00:1a.1: restoring config space at offset 0x1 (was 0x2900005, writing 0x2900001)
Aug  9 23:01:39 localhost kernel: [  213.560454] ehci_hcd 0000:00:1a.7: restoring config space at offset 0x1 (was 0x2900006, writing 0x2900002)
Aug  9 23:01:39 localhost kernel: [  213.560507] HDA Intel 0000:00:1b.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
Aug  9 23:01:39 localhost kernel: [  213.560513] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100006, writing 0x100002)
Aug  9 23:01:39 localhost kernel: [  213.560567] pcieport 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Aug  9 23:01:39 localhost kernel: [  213.560630] pcieport 0000:00:1c.2: restoring config space at offset 0x7 (was 0x4040, writing 0x20004040)
Aug  9 23:01:39 localhost kernel: [  213.560643] pcieport 0000:00:1c.2: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Aug  9 23:01:39 localhost kernel: [  213.560715] pcieport 0000:00:1c.3: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Aug  9 23:01:39 localhost kernel: [  213.560787] pcieport 0000:00:1c.4: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Aug  9 23:01:39 localhost kernel: [  213.560858] pcieport 0000:00:1c.5: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Aug  9 23:01:39 localhost kernel: [  213.560924] uhci_hcd 0000:00:1d.0: restoring config space at offset 0x1 (was 0x2900005, writing 0x2900001)
Aug  9 23:01:39 localhost kernel: [  213.560965] uhci_hcd 0000:00:1d.1: restoring config space at offset 0x1 (was 0x2900005, writing 0x2900001)
Aug  9 23:01:39 localhost kernel: [  213.561005] uhci_hcd 0000:00:1d.2: restoring config space at offset 0x1 (was 0x2900005, writing 0x2900001)
Aug  9 23:01:39 localhost kernel: [  213.561053] ehci_hcd 0000:00:1d.7: restoring config space at offset 0x1 (was 0x2900006, writing 0x2900002)
Aug  9 23:01:39 localhost kernel: [  213.561089] pci 0000:00:1e.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1)
Aug  9 23:01:39 localhost kernel: [  213.561094] pci 0000:00:1e.0: restoring config space at offset 0x8 (was 0x0, writing 0xfff0)
Aug  9 23:01:39 localhost kernel: [  213.561099] pci 0000:00:1e.0: restoring config space at offset 0x7 (was 0x22800000, writing 0x228000f0)
Aug  9 23:01:39 localhost kernel: [  213.561112] pci 0000:00:1e.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100007)
Aug  9 23:01:39 localhost kernel: [  213.561209] ahci 0000:00:1f.2: restoring config space at offset 0x1 (was 0x2b00007, writing 0x2b00407)
Aug  9 23:01:39 localhost kernel: [  213.561377] nvidia 0000:01:00.0: restoring config space at offset 0x9 (was 0x1, writing 0x6001)
Aug  9 23:01:39 localhost kernel: [  213.561385] nvidia 0000:01:00.0: restoring config space at offset 0x7 (was 0x4, writing 0x90000004)
Aug  9 23:01:39 localhost kernel: [  213.561600] wl 0000:03:00.0: restoring config space at offset 0x1 (was 0x180006, writing 0x100006)
Aug  9 23:01:39 localhost kernel: [  213.561712] r8169 0000:04:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
Aug  9 23:01:39 localhost kernel: [  213.561720] r8169 0000:04:00.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Aug  9 23:01:39 localhost kernel: [  213.561797] sdhci-pci 0000:05:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x10b)
Aug  9 23:01:39 localhost kernel: [  213.561835] sdhci-pci 0000:05:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100007)
Aug  9 23:01:39 localhost kernel: [  213.561884] pci 0000:05:00.2: restoring config space at offset 0xf (was 0x1ff, writing 0x10b)
Aug  9 23:01:39 localhost kernel: [  213.561922] pci 0000:05:00.2: restoring config space at offset 0x1 (was 0x100000, writing 0x100003)
Aug  9 23:01:39 localhost kernel: [  213.561971] jmb38x_ms 0000:05:00.3: restoring config space at offset 0xf (was 0x1ff, writing 0x10b)
Aug  9 23:01:39 localhost kernel: [  213.562009] jmb38x_ms 0000:05:00.3: restoring config space at offset 0x1 (was 0x100000, writing 0x100007)
Aug  9 23:01:39 localhost kernel: [  213.562058] pci 0000:05:00.4: restoring config space at offset 0xf (was 0x1ff, writing 0x10b)
Aug  9 23:01:39 localhost kernel: [  213.562096] pci 0000:05:00.4: restoring config space at offset 0x1 (was 0x100000, writing 0x100007)
Aug  9 23:01:39 localhost kernel: [  213.562310] PM: early resume of devices complete after 2.086 msecs
Aug  9 23:01:39 localhost kernel: [  213.562456] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Aug  9 23:01:39 localhost kernel: [  213.562464] uhci_hcd 0000:00:1a.0: setting latency timer to 64
Aug  9 23:01:39 localhost kernel: [  213.562491] usb usb3: root hub lost power or was reset
Aug  9 23:01:39 localhost kernel: [  213.562507] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Aug  9 23:01:39 localhost kernel: [  213.562513] uhci_hcd 0000:00:1a.1: setting latency timer to 64
Aug  9 23:01:39 localhost kernel: [  213.562542] usb usb4: root hub lost power or was reset
Aug  9 23:01:39 localhost kernel: [  213.562557] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Aug  9 23:01:39 localhost kernel: [  213.562563] ehci_hcd 0000:00:1a.7: setting latency timer to 64
Aug  9 23:01:39 localhost kernel: [  213.562613] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
Aug  9 23:01:39 localhost kernel: [  213.562613] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 22 (level, low) -> IRQ 22
Aug  9 23:01:39 localhost kernel: [  213.562621] uhci_hcd 0000:00:1d.0: setting latency timer to 64
Aug  9 23:01:39 localhost kernel: [  213.562623] uhci_hcd 0000:00:1d.1: setting latency timer to 64
Aug  9 23:01:39 localhost kernel: [  213.562654] usb usb5: root hub lost power or was reset
Aug  9 23:01:39 localhost kernel: [  213.562657] usb usb6: root hub lost power or was reset
Aug  9 23:01:39 localhost kernel: [  213.562669] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Aug  9 23:01:39 localhost kernel: [  213.562673] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20
Aug  9 23:01:39 localhost kernel: [  213.562679] uhci_hcd 0000:00:1d.2: setting latency timer to 64
Aug  9 23:01:39 localhost kernel: [  213.562681] ehci_hcd 0000:00:1d.7: setting latency timer to 64
Aug  9 23:01:39 localhost kernel: [  213.562707] usb usb7: root hub lost power or was reset
Aug  9 23:01:39 localhost kernel: [  213.562710] pci 0000:00:1e.0: setting latency timer to 64
Aug  9 23:01:39 localhost kernel: [  213.563432] ahci 0000:00:1f.2: setting latency timer to 64
Aug  9 23:01:39 localhost kernel: [  213.563628] wl 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Aug  9 23:01:39 localhost kernel: [  213.563644] wl 0000:03:00.0: setting latency timer to 64
Aug  9 23:01:39 localhost kernel: [  213.563679] sdhci-pci 0000:05:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Aug  9 23:01:39 localhost kernel: [  213.563705] sdhci-pci 0000:05:00.0: setting latency timer to 64
Aug  9 23:01:39 localhost kernel: [  213.563741] jmb38x_ms 0000:05:00.3: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Aug  9 23:01:39 localhost kernel: [  213.563753] jmb38x_ms 0000:05:00.3: setting latency timer to 64
Aug  9 23:01:39 localhost kernel: [  213.566832] sd 0:0:0:0: [sda] Starting disk
Aug  9 23:01:39 localhost kernel: [  213.593445] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
Aug  9 23:01:39 localhost kernel: [  213.593461] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
Aug  9 23:01:39 localhost kernel: [  213.593470] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
Aug  9 23:01:39 localhost kernel: [  213.593474] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
Aug  9 23:01:39 localhost kernel: [  213.593486] HDA Intel 0000:00:1b.0: PCI INT B -> GSI 22 (level, low) -> IRQ 22
Aug  9 23:01:39 localhost kernel: [  213.593497] HDA Intel 0000:00:1b.0: setting latency timer to 64
Aug  9 23:01:39 localhost kernel: [  213.593557] HDA Intel 0000:00:1b.0: irq 48 for MSI/MSI-X
Aug  9 23:01:39 localhost kernel: [  213.623386] r8169 0000:04:00.0: wake-up capability disabled by ACPI
Aug  9 23:01:39 localhost kernel: [  213.623402] r8169 0000:04:00.0: PME# disabled
Aug  9 23:01:39 localhost kernel: [  213.883400] ata6: SATA link down (SStatus 0 SControl 300)
Aug  9 23:01:39 localhost kernel: [  213.903395] ata2: SATA link down (SStatus 0 SControl 300)
Aug  9 23:01:39 localhost kernel: [  214.056718] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Aug  9 23:01:39 localhost kernel: [  214.066701] usb 5-2: reset low speed USB device number 2 using uhci_hcd
Aug  9 23:01:39 localhost kernel: [  214.088396] ata5.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Aug  9 23:01:39 localhost kernel: [  214.109654] ata5.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
Aug  9 23:01:39 localhost kernel: [  214.130857] ata5.00: ACPI cmd ef/10:02:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
Aug  9 23:01:39 localhost kernel: [  214.130863] ata5.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Aug  9 23:01:39 localhost kernel: [  214.152193] ata5.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
Aug  9 23:01:39 localhost kernel: [  214.173416] ata5.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
Aug  9 23:01:39 localhost kernel: [  214.211504] ata5.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Aug  9 23:01:39 localhost kernel: [  214.211944] ata5.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
Aug  9 23:01:39 localhost kernel: [  214.212297] ata5.00: ACPI cmd ef/10:02:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
Aug  9 23:01:39 localhost kernel: [  214.212304] ata5.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Aug  9 23:01:39 localhost kernel: [  214.212682] ata5.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
Aug  9 23:01:39 localhost kernel: [  214.213033] ata5.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
Aug  9 23:01:39 localhost kernel: [  214.213040] ata5.00: configured for UDMA/100
Aug  9 23:01:39 localhost kernel: [  214.453439] usb 2-5: reset high speed USB device number 3 using ehci_hcd
Aug  9 23:01:39 localhost kernel: [  215.983441] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Aug  9 23:01:39 localhost kernel: [  215.984511] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Aug  9 23:01:39 localhost kernel: [  216.100653] ata1.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) succeeded
Aug  9 23:01:39 localhost kernel: [  216.100773] ata1.00: ACPI cmd ef/10:02:00:00:00:a0 (SET FEATURES) succeeded
Aug  9 23:01:39 localhost kernel: [  216.100776] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Aug  9 23:01:39 localhost kernel: [  216.100947] ata1.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) succeeded
Aug  9 23:01:39 localhost kernel: [  216.101120] ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) succeeded
Aug  9 23:01:39 localhost kernel: [  216.102634] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Aug  9 23:01:39 localhost kernel: [  216.102755] ata1.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) succeeded
Aug  9 23:01:39 localhost kernel: [  216.102761] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Aug  9 23:01:39 localhost kernel: [  216.102877] ata1.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) succeeded
Aug  9 23:01:39 localhost kernel: [  216.103049] ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) succeeded
Aug  9 23:01:39 localhost kernel: [  216.103528] ata1.00: configured for UDMA/100
Aug  9 23:01:39 localhost kernel: [  216.168183] PM: resume of devices complete after 2605.754 msecs
Aug  9 23:01:39 localhost kernel: [  216.168420] r8169 0000:04:00.0: PME# enabled
Aug  9 23:01:39 localhost kernel: [  216.210233] PM: Finishing wakeup.
Aug  9 23:01:39 localhost kernel: [  216.210235] Restarting tasks ... done.
Aug  9 23:01:39 localhost kernel: [  216.218506] video LNXVIDEO:01: Restoring backlight state
Aug  9 23:01:42 localhost kernel: [  218.297775] EXT4-fs (sda5): re-mounted. Opts: commit=0
Aug  9 23:01:42 localhost kernel: [  218.302291] EXT4-fs (sda6): re-mounted. Opts: commit=0
Aug  9 23:01:42 localhost kernel: [  218.416749] r8169 0000:04:00.0: PME# disabled
Aug  9 23:01:42 localhost kernel: [  218.420630] r8169 0000:04:00.0: eth0: link down
Aug  9 23:01:42 localhost kernel: [  218.420638] r8169 0000:04:00.0: eth0: link down
Aug  9 23:01:42 localhost kernel: [  218.420827] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug  9 23:01:42 localhost kernel: [  218.520368] r8169 0000:04:00.0: PME# enabled

Last edited by fengya (2011-08-09 15:11:43)

Offline

#7 2011-08-09 15:30:28

fengya
Member
Registered: 2011-04-29
Posts: 24

Re: network problem after sleep

i find the network card still work after first sleep
but can't work after another sleep

Offline

#8 2011-08-09 15:47:58

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: network problem after sleep

fengya wrote:

i find the network card still work after first sleep
but can't work after another sleep

But the system sees it anyway.  Have you tried to obtain an IP manually?

Offline

#9 2011-08-10 15:25:25

fengya
Member
Registered: 2011-04-29
Posts: 24

Re: network problem after sleep

I modprobe the r8169 again,then everything is ok

modprobe r8169 -r
modprobe r8169

but why?my god.

Offline

#10 2011-09-20 20:29:52

458italia
Member
Registered: 2011-02-04
Posts: 20

Re: network problem after sleep

fengya wrote:

I modprobe the r8169 again,then everything is ok

modprobe r8169 -r
modprobe r8169

but why?my god.

Well I've tried that on my laptop in question, but even that does not work :-/. I've tried to set an IP manually using a different router (normally I just use dhcp to acquire my address), but that hasn't worked either. My kernel log has the same messages as was previously posted in this thread as well. It's almost as if the card is unable to reset itself after waking from sleep.

Offline

#11 2011-09-21 11:30:41

Loose_Control
Member
From: Germany
Registered: 2011-01-11
Posts: 136

Re: network problem after sleep

try the r8168 driver https://aur.archlinux.org/packages.php?ID=27000 dont forget too blacklist r8169...
i also hat problems with r8169 after sleep...

Last edited by Loose_Control (2011-09-21 11:30:59)

Offline

Pages: 1

Board footer

Powered by FluxBB