Bug 10581 - via-rhine - no network after suspend to disk
via-rhine - no network after suspend to disk
Status: CLOSED OBSOLETE
Product: Drivers
Classification: Unclassified
Component: Network
All Linux
: P1 normal
Assigned To: Roger Luethi
:
Depends on:
Blocks: 7216
  Show dependency treegraph
 
Reported: 2008-05-01 00:18 UTC by Tomasz Chmielewski
Modified: 2012-05-21 15:16 UTC (History)
5 users (show)

See Also:
Kernel Version: 2.6.24.3
Tree: Mainline
Regression: No


Attachments

Description Tomasz Chmielewski 2008-05-01 00:18:20 UTC
I have a network card which uses via-rhine module. After I wake the machine up after it was suspended to disk, network doesn't work.

dmesg tells this:

NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status ffff, PHY status ffff, resetting...
via-rhine: Reset not complete yet. Trying harder.
eth0: link up, 100Mbps, full-duplex, lpa 0xFFFF
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status ffff, PHY status ffff, resetting...
via-rhine: Reset not complete yet. Trying harder.
eth0: link up, 100Mbps, full-duplex, lpa 0xFFFF
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status ffff, PHY status ffff, resetting...
via-rhine: Reset not complete yet. Trying harder.
eth0: link up, 100Mbps, full-duplex, lpa 0xFFFF
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status ffff, PHY status ffff, resetting...
via-rhine: Reset not complete yet. Trying harder.
eth0: link up, 100Mbps, full-duplex, lpa 0xFFFF
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status ffff, PHY status ffff, resetting...
via-rhine: Reset not complete yet. Trying harder.
eth0: link up, 100Mbps, full-duplex, lpa 0xFFFF


The only thing which helps is unloading via_rhine module and loading it again - after this, network works fine again.


00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
        Subsystem: ASRock Incorporation K7VT6 motherboard
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 32 (750ns min, 2000ns max), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 18
        Region 0: I/O ports at bc00 [size=256]
        Region 1: Memory at dfffbc00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Kernel driver in use: via-rhine
        Kernel modules: via-rhine
Comment 1 Tomasz Chmielewski 2008-05-01 03:23:30 UTC
Same problem with 2.6.25.
Comment 2 Tomasz Chmielewski 2008-05-02 15:07:23 UTC
There is a related thread concerning this bug:

http://marc.info/?t=120928218500001&r=1&w=4
Comment 3 Martin Jürgens 2008-10-28 07:58:45 UTC
probably also related to bug 11692
Comment 4 Rafael J. Wysocki 2011-01-16 21:52:34 UTC
Please try 2.6.37 and report back.

Note You need to log in before you can comment on or make changes to this bug.