Home / server / Questions / 197120
Accepted
Bourne
Asked: 2010-11-02 15:12:44 +0800 CST

Does this dmesg output indicate a failed network card on Red Hat Enterprise?

  • 772

Having an issue with a network card on a server today. If I restart the service via "service network restart" the card never comes back, the command prompt just hangs. I suspect it's a bad network card but wanted to run the output of dmesg by someone that might have come across these errors before. The output contains many lines like the one below.

NETDEV WATCHDOG: eth2: transmit timed out
eth2: tx_timeout: tx_done_idx=98 free_idx=89 cmdsts=8000005a
eth2: after: tx_done_idx=98 free_idx=89 cmdsts=8000005a
eth2: ns83820_tx_watch: 98 89 119
eth2: tx_timeout: tx_done_idx=98 free_idx=89 cmdsts=8000005a
eth2: after: tx_done_idx=98 free_idx=89 cmdsts=8000005a
eth2: ns83820_tx_watch: 98 89 119
eth2: tx_timeout: tx_done_idx=98 free_idx=89 cmdsts=8000005a
eth2: after: tx_done_idx=98 free_idx=89 cmdsts=8000005a
eth2: ns83820_tx_watch: 98 89 119

Any input would be appreciated. Thank you.

Edit:

lspci -vv output:

02:05.0 Ethernet controller: National Semiconductor Corporation DP83820 10/100/1000 Ethernet Controller
    Subsystem: National Semiconductor Corporation DP83820 10/100/1000 Ethernet Controller
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
    Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
    Latency: 64 (2750ns min, 13000ns max), Cache Line Size 10
    Interrupt: pin A routed to IRQ 209
    Region 0: I/O ports at 2400 [size=256]
    Region 1: Memory at fe040000 (32-bit, non-prefetchable) [size=4K]
    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-
dmesg

2 Answers

  1. Best Answer

    If network card works before you use "service network restart" command then try to change network configuration without restarting network using "ifconfig", "route", etc. commands and see what happens.

    If you are able to change network configuration without causing problems then it is some kind of card problem or card/OS compatibility issue. During "service network restart" OS may power off the NIC and try to power it on back again. May be this operation is failing.

    You can also avoid using "service network restart" completely on this machine and always work with "ifconfig", "route", "ip" commands etc. to get things done in case they work.

    • 1

  2. Try #lspci -vv and find your device in the output.

    • 0