View previous topic :: View next topic |
Author |
Message |
Special K n00b
Joined: 24 Aug 2004 Posts: 20
|
Posted: Mon Dec 25, 2006 1:36 am Post subject: wierd eth0 errors. 100BaseT slow like modem |
|
|
since about two weeks my gentoo suffers from a very high error rate on eth0 and so caused low transfer rates. it seems to me theat it is not a continuous situation, but most of time.
I'm definitly
here is what ifconfig and ... are crying:
Note: eth0 is on bridge pan0 (for hanging incoming bnep? bluetooth clients in)
Code: |
# brctl show
bridge name bridge id STP enabled interfaces
pan0 8000.004063db13f3 yes eth0
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:40:63:EB:12:F6
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9612 errors:0 dropped:0 overruns:0 frame:0
TX packets:14690 errors:2035072 dropped:0 overruns:2035031 carrier:0
collisions:773 txqueuelen:1000
RX bytes:936814 (914.8 Kb) TX bytes:5753833 (5.4 Mb)
Interrupt:11 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:458 errors:0 dropped:0 overruns:0 frame:0
TX packets:458 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:152267 (148.6 Kb) TX bytes:152267 (148.6 Kb)
pan0 Link encap:Ethernet HWaddr 00:40:63:EB:12:F6
inet addr:172.16.0.20 Bcast:172.16.0.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9530 errors:0 dropped:0 overruns:0 frame:0
TX packets:10825 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:723438 (706.4 Kb) TX bytes:5818823 (5.5 Mb)
|
dmesg shows me strange behavior too:
Code: |
pan0: port 2(bnep0) entering learning state
pan0: topology change detected, propagating
pan0: port 2(bnep0) entering forwarding state
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 786d, resetting...
via-rhine: Reset not complete yet. Trying harder.
eth0: Promiscuous mode enabled.
eth0: link up, 100Mbps, half-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 786d, resetting...
via-rhine: Reset not complete yet. Trying harder.
eth0: Promiscuous mode enabled.
eth0: link up, 100Mbps, half-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 786d, resetting...
via-rhine: Reset not complete yet. Trying harder.
eth0: Promiscuous mode enabled.
|
_________________ Sam & Max 2 development has been resurrected.
http://www.telltalegames.com/samandmax |
|
Back to top |
|
|
moocha Watchman
Joined: 21 Oct 2003 Posts: 5722
|
Posted: Mon Dec 25, 2006 2:59 am Post subject: |
|
|
If you didn't recently recompile your kernel, then the obvious first thing to do is to swap out that card for a known good one and see if the problem persists (also try placing it in a different PCI slot, just in the unlikely case it's the slot or interference from a nearby card). Next obvious thing to do: Check the cabling and the connectors. It's almost certainly a hardware problem.
If you did change kernels, then revert to the known good one or fiddle with the via-rhine driver MMIO settings if you changed them from the defaults. _________________ Military Commissions Act of 2006: http://tinyurl.com/jrcto
"Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety."
-- attributed to Benjamin Franklin |
|
Back to top |
|
|
Special K n00b
Joined: 24 Aug 2004 Posts: 20
|
Posted: Wed Dec 27, 2006 1:08 am Post subject: |
|
|
ok, the problem is getting a shape, but an unlogical one.
Those TX-overflow-errors appear just after starting the system and last for some hours, then everything runs as usual and no new errors appear.
I tried another cable - nothing changes.
The wierd thing: I tried an usb-lan adapter (eth0 is a build in one and there are no pci slots free)
ifconfig does not list any errors:
Code: |
eth2 Link encap:Ethernet HWaddr 00:C0:26:10:6E:C4
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5134 errors:0 dropped:0 overruns:0 frame:0
TX packets:7005 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:600423 (586.3 Kb) TX bytes:8385239 (7.9 Mb)
|
Now it's getting crazy: on high traffic the RUNNING state disapears periodically and transmitting occours in short bulk blocks resulting in a likewise very low performance.
pan0: topology change detected, propagating
pan0: port 1(eth2) entering forwarding state
pan0: port 1(eth2) entering disabled state
pan0: port 1(eth2) entering listening state
pan0: port 1(eth2) entering learning state
pan0: topology change detected, propagating
pan0: port 1(eth2) entering forwarding state
pan0: port 1(eth2) entering disabled state
pan0: port 1(eth2) entering listening state
pan0: port 1(eth2) entering learning state
oh.. dmesg is flooded by thousands of those lines:
Since i haven't changed system related things like kernel and modules for upon one year, I would bet it's a hardware thing. On the other hand the behavior of (the new) eth2 is confusing me.
_________________ Sam & Max 2 development has been resurrected.
http://www.telltalegames.com/samandmax
Last edited by Special K on Wed Dec 27, 2006 1:12 am; edited 1 time in total |
|
Back to top |
|
|
Jimi... Tux's lil' helper
Joined: 06 Aug 2005 Posts: 136 Location: IoM
|
Posted: Wed Dec 27, 2006 1:11 am Post subject: |
|
|
What NIC is it?
What's the spec of your PC? _________________ Asus P5W DH Deluxe
Intel C2D E6600
ATI X1900XT
2GB G.Skill HZ |
|
Back to top |
|
|
Special K n00b
Joined: 24 Aug 2004 Posts: 20
|
Posted: Wed Dec 27, 2006 1:22 am Post subject: |
|
|
thanks for your fast reply. after your reply I have found something in dmesg (see above).
The usb-lan adaptor is an ADMtek (eth2)
The built in is a via-rhine. (eth0)
eth1 seems to be the TV-card
The PC is one of the Via-EPIA Fanless (600Mhz) with one haupauge pvr 150 as TV-card. (so now we have a vdr .. had a vdr?)
here are lspci and lsusb
Quote: |
# lsusb
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 07a6:8513 ADMtek, Inc.
Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
# lspci
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266]
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
0000:00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
0000:00:14.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
0000:01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics (rev 03)
|
_________________ Sam & Max 2 development has been resurrected.
http://www.telltalegames.com/samandmax |
|
Back to top |
|
|
opentaka l33t
Joined: 18 Feb 2005 Posts: 840 Location: Japan
|
Posted: Wed Dec 27, 2006 11:00 am Post subject: |
|
|
it looks like the hardware failure to me, but will you boot up with gentoo live(install) cd and see if the problem is still there? _________________ "Being defeated is often a temporary condition. Giving up is what makes it permanent" - Marilyn vos Savant
|
|
Back to top |
|
|
Special K n00b
Joined: 24 Aug 2004 Posts: 20
|
Posted: Thu Dec 28, 2006 1:58 am Post subject: |
|
|
I have booted up with livecd and here the problem had gone.
So if this was not just a random effect, it seems to be a software problem.
I will play around a little bit with kernel .config _________________ Sam & Max 2 development has been resurrected.
http://www.telltalegames.com/samandmax |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|