* Re: [gentoo-user] Network timeout, eth0 stopped
2005-09-04 19:01 [gentoo-user] Network timeout, eth0 stopped waltdnes
@ 2005-09-04 20:19 ` YoYo Siska
0 siblings, 0 replies; 2+ messages in thread
From: YoYo Siska @ 2005-09-04 20:19 UTC (permalink / raw
To: gentoo-user
waltdnes@waltdnes.org wrote:
> Approx a week ago, I got a new computer, AMD64 on a K8 Triton Gigabyte
> Triton Nforce 4 motherboard. Today, ethernet stopped functioning. I
> couldn't even get it to work with the Gentoo minimal install CD. It was
> running OK the past week with...
> "<*> Reverse Engineered nForce Ethernet support (EXPERIMENTAL)" built
> into the kernel (would be forcedeth as a module). I looks like it has
> died on me. My old backup machine, hooked up to the same 4-port
> ADSL-modem/router connects to the net just fine. I swapped the ethernet
> cables to check if it was a bad router port or cable. The old machine
> works, the new one doesn't. "m3000" is the machine's hostname. The
> following message shows up in my logs (and on tty12) when I try to
> access a web site...
>
> NETDEV WATCHDOG: eth0: transmit timed out
> Sep 4 11:47:31 m3000 nv_stop_tx: TransmitterStatus remained busy<7>eth0: tx_timeout: dead entries!
hi,
I've got an AMD64 assus nfore 4 mobo with on board eth, and I started to
have the same problem some time ago. Was just wondering wether it is
just a driver problem or should take it back to shop...
The thing is, that when I power the computer off completely (take it off
ac completely, so the motherboard gets shut down completely) and then
boot it again, it seems to work again... I wasn't able to find any
reason for it to fail, sometimes it failed 2-3 times a day, then it ran
on for about a week...
I'm running the same driver (forcedeth), logs show the same messages,
nothing interesting before them...
I've got win installed on the machine and even rebooting to them didn't
help (tought, that the win driver could somehow reset the card back ;),
only the hard power-down. I do not use the win instalation much (at
least it is newer booted for longer than 2-3 hours...) so I can't say if
it happens in win too...
lspci -vv
0000:00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (250ns min, 5000ns max)
Interrupt: pin A routed to IRQ 177
Region 0: Memory at d0000000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at b000 [size=8]
Capabilities: [44] 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-
yoyo
>
> lspci -vv shows the following...
>
> 0000:00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a2)
> Subsystem: Giga-byte Technology: Unknown device e000
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0 (250ns min, 5000ns max)
> Interrupt: pin A routed to IRQ 11
> Region 0: Memory at ea104000 (32-bit, non-prefetchable) [size=4K]
> Region 1: I/O ports at e000 [size=8]
> Capabilities: [44] 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-
>
>
> It's Sunday afternoon, and tomorrow's a holiday. Any last-minute ideas
> or tweaks before I take it back to the shop on Tuesday?
>
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 2+ messages in thread