LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 10-09-2005, 09:19 AM   #1
Ogi
Member
 
Registered: Jun 2004
Location: Belgrade
Distribution: Anything with a bash prompt :P
Posts: 74

Rep: Reputation: 15
3com Transmit error


Hi all, I keep getting the following error on my server:

Oct 9 14:02:45 Sun eth0: Transmit error, Tx status register 82.
Oct 9 14:02:45 Sun Probably a duplex mismatch. See Documentation/networking/vortex.txt
Oct 9 14:02:45 Sun Flags; bus-master 1, dirty 935237(5) current 935237(5)
Oct 9 14:02:45 Sun Transmit list 00000000 vs. ef2cb520.
Oct 9 14:02:45 Sun 0: @ef2cb200 length 80000522 status 00010522
Oct 9 14:02:45 Sun 1: @ef2cb2a0 length 80000072 status 00010072
Oct 9 14:02:45 Sun 2: @ef2cb340 length 8000024e status 0001024e
Oct 9 14:02:45 Sun 3: @ef2cb3e0 length 8000024e status 0001024e
Oct 9 14:02:45 Sun 4: @ef2cb480 length 8000024e status 8001024e
Oct 9 14:02:45 Sun 5: @ef2cb520 length 800005ea status 000105ea
Oct 9 14:02:45 Sun 6: @ef2cb5c0 length 800005ea status 000105ea
Oct 9 14:02:45 Sun 7: @ef2cb660 length 800005ea status 000105ea
Oct 9 14:02:45 Sun 8: @ef2cb700 length 800005ea status 000105ea
Oct 9 14:02:45 Sun 9: @ef2cb7a0 length 800005ea status 000105ea
Oct 9 14:02:45 Sun 10: @ef2cb840 length 800005ea status 000105ea
Oct 9 14:02:45 Sun 11: @ef2cb8e0 length 800005ea status 000105ea
Oct 9 14:02:45 Sun 12: @ef2cb980 length 800005ea status 000105ea
Oct 9 14:02:45 Sun 13: @ef2cba20 length 80000249 status 00010249
Oct 9 14:02:45 Sun 14: @ef2cbac0 length 800005ea status 000105ea
Oct 9 14:02:45 Sun 15: @ef2cbb60 length 800005ea status 000105ea


it keeps repeating until it fills up my hd with error messages, and network throughput is about 100kbs (when its a 10mbit network).

I read the documentation, recompiled the 3c59x as a module and forced operation to 10baseT but it still has a problem, I tried changing the ethernet cable, still the same problem.

Can anyone tell me what can cause this error (i.e. will i need to buy a new hub/cable/network card) or is it a config problem.

If its of any consequence, the ethernet card is in a bridge with a wireless PCI card (running hostap as an access point)
 
Old 10-09-2005, 11:38 AM   #2
MensaWater
LQ Guru
 
Registered: May 2005
Location: Atlanta Georgia USA
Distribution: Redhat (RHEL), CentOS, Fedora, CoreOS, Debian, FreeBSD, HP-UX, Solaris, SCO
Posts: 7,831
Blog Entries: 15

Rep: Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669
It probably isn't operating in the mode you think. Recently I ran into this on 3Com cards and found mii-tool would query them and supposedly set them but never saw any changes whether I did it with that tool or with modifications to module.conf.

Ultimately we went to the router and told it to do autonegotiate to see what the card would say it was doing (speed/duplex) and once we found that we hard code the router setup to match what the card was doing.

The message is complaining about duplex so if your router is set to full try switching it to half or vice-versa.
 
Old 10-09-2005, 02:57 PM   #3
Ogi
Member
 
Registered: Jun 2004
Location: Belgrade
Distribution: Anything with a bash prompt :P
Posts: 74

Original Poster
Rep: Reputation: 15
I had a look at my hub, its an unmanaged 10mbit hub (8 port). I Tried a known-working hub (again unmanaged 10mbit) But still the same problem.

Am I right in thinking that the hub is 10mbit/s half-duplex. Is there any way of finding out in what duplex mode the 3com card is in?


My network looks like this:

------- |---------|
| NET | === | Server | ====[ HUB ]============[ HUB ]=============[ HUB ]
------- |---------| || || ||
[NODES 1-3] [NODE 4] [NODES 5-8]

All hubs are unmanaged hubs (not switches) and as such are limited to 10mbit.

Could it be a cable. As I have a mixed (star/bus) topology is it possible that the ethernet cable running between the hubs is to blame.

Last edited by Ogi; 10-09-2005 at 02:58 PM.
 
Old 10-09-2005, 03:04 PM   #4
Ogi
Member
 
Registered: Jun 2004
Location: Belgrade
Distribution: Anything with a bash prompt :P
Posts: 74

Original Poster
Rep: Reputation: 15
OK I installed mii-diag and ran it:

mii-tool:

eth0: link ok
registers for MII PHY 24:
1000 780d 0040 6176 05e1 0021 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
1000 0000 0000 0000 0000 0000 0200 0000
0030 0004 0f00 ff40 0020 0000 0000 000b
product info: vendor 00:10:18, model 23 rev 6
basic mode: autonegotiation enabled
basic status: link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
link partner: 10baseT-HD



mii-diag -v :

mii-diag.c:v2.09 9/06/2003 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Using the default interface 'eth0'.
Using the new SIOCGMIIPHY value on PHY 24 (BMCR 0x1000).
Basic mode control register 0x1000: Auto-negotiation enabled.
You have link beat, and everything is working OK.
This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
Able to perform Auto-negotiation, negotiation not complete.
Your link partner is generating 10baseT link beat (no autonegotiation).
End of basic transceiver information.

libmii.c:v2.10 4/22/2003 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
MII PHY #24 transceiver registers:
1000 780d 0040 6176 05e1 0021 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
1000 0000 0000 0000 0000 0000 0300 0000
0030 0004 0f00 ff40 0020 0000 0000 000b.
Basic mode control register 0x1000: Auto-negotiation enabled.
Basic mode status register 0x780d ... 780d.
Link status: established.
Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
Able to perform Auto-negotiation, negotiation not complete.
Vendor ID is 00:10:18:--:--:--, model 23 rev. 6.
No specific information is known about this transceiver type.
I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT
Advertising no additional info pages.
IEEE 802.3 CSMA/CD protocol.
Link partner capability is 0021: 10baseT.
Negotiation did not complete.


Whats this about "Negotiation did not complete" - It tells the the ethernets partner is not capable of autonegotiation, does this mean i should set it manually, and if so, to what?
 
Old 10-09-2005, 03:13 PM   #5
Ogi
Member
 
Registered: Jun 2004
Location: Belgrade
Distribution: Anything with a bash prompt :P
Posts: 74

Original Poster
Rep: Reputation: 15
Bingo! :


Quote:
mii-tool -F 10baseT-FD
Seems that setting the link to 10mbit/s full duplex fixes the problem even though it detects the link as half-duplex. I presume this is just to do with hubs, and their lack of being able to auto-negotiate links.

The final settings:


Quote:
eth0: 10 Mbit, full duplex, link ok
product info: vendor 00:10:18, model 23 rev 6
basic mode: 10 Mbit, full duplex
basic status: link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
link partner: 10baseT-HD
Note the difference between the link partner, and the 3coms new setting.

Is there any way to set this so that the setting is kept after a server restart?
 
Old 10-09-2005, 04:35 PM   #6
Ogi
Member
 
Registered: Jun 2004
Location: Belgrade
Distribution: Anything with a bash prompt :P
Posts: 74

Original Poster
Rep: Reputation: 15
I think I celebrated too soon, the above does indeed remove the Tx-Error, but the result is even worse performance then previously, with a network throughput of about 80kbs (its so slow i cannot even steam a 128kbs MP3 from my server, forget about anything else).

I am running out of ideas, can anyone shed some light on the problem?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
3COM error serkanfahri Linux - Networking 1 06-14-2005 12:05 PM
3Com Error serkanfahri Linux - Hardware 0 06-12-2005 07:30 PM
3com 3c940 error c31c Linux - Hardware 4 12-11-2004 01:25 PM
sendmail transmit timed out error -destination host unreachable KTCommander04 Linux - Networking 2 12-23-2003 10:59 AM
eth0: Transmit timed out GuPH Linux - Networking 4 12-16-2003 09:16 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 09:34 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration