Dual Athlon problems (eepro transmit hang)

I worked as a consultant for a company that were using a dual Athlon 
system (I think it
it had a VIA chipset) for there products and we had problem with 
transmits timing out
which resulted in the same printouts that you see.

These timeouts always ocurred when loading the interface with high loads 
(> 30%). We did
not solve the problem but my theory is that there is someting wrong with 
the 32 Bit PCI
handling in that  specific chipset that did not work properly with a SMP 
set-up because
when using only 1 CPU it worked without any problems.
We did not see any problems when we used the 64bit PCI slots which also 
points on some
fault in the 32bit PCI handling.

/Anders
 

[email protected] wrote:

>Send eepro100 mailing list submissions to
>	[email protected]
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://www.scyld.com/mailman/listinfo/eepro100
>or, via email, send a message with subject or body 'help' to
>	[email protected]
>
>You can reach the person managing the list at
>	[email protected]
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of eepro100 digest..."
>
>
>Today's Topics:
>
>   1. eepro100 hang (Joe Radinger)
>
>--__--__--
>
>Message: 1
>From: Joe Radinger <[email protected]>
>To: [email protected]
>Date: Mon, 19 Jan 2004 17:00:12 +0100
>Subject: [eepro100] eepro100 hang
>
>hi
>i again have several hanging systems:
>messages state:
>
>Jan 19 09:59:00 lala kernel: NETDEV WATCHDOG: eth0: transmit timed out
>Jan 19 09:59:00 lala kernel: eth0: Transmit timed out: status f048  0c00
>at 24187347/24187407 command 000ca000.
>Jan 19 09:59:03 lala kernel: NETDEV WATCHDOG: eth0: transmit timed out
>Jan 19 09:59:03 lala kernel: eth0: Transmit timed out: status f048  0c00
>at 24187407/24187467 command 0001a000.
>Jan 19 09:59:07 lala kernel: NETDEV WATCHDOG: eth0: transmit timed out
>Jan 19 09:59:07 lala kernel: eth0: Transmit timed out: status f048  0c00
>at 24187467/24187527 command 0001a000.
>Jan 19 09:59:09 lala kernel: NETDEV WATCHDOG: eth3: transmit timed out
>Jan 19 09:59:09 lala kernel: eth3: Transmit timed out: status f048  0c00
>at 383329/383389 command 000ca000.
>Jan 19 09:59:11 lala kernel: NETDEV WATCHDOG: eth0: transmit timed out
>Jan 19 09:59:11 lala kernel: eth0: Transmit timed out: status f048  0c00
>at 24187527/24187587 command 0001a000.
>Jan 19 09:59:15 lala kernel: NETDEV WATCHDOG: eth0: transmit timed out
>Jan 19 09:59:15 lala kernel: eth0: Transmit timed out: status f048  0c00
>at 24187587/24187647 command 0001a000.
>
>
>eepro100 version: 
>eepro100.c:v1.09j-t 9/29/99 Donald Becker 
>Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
>
>
>has anybody some ideas?
>
>could this be related to sleep mode?
>
>sorry, but i have no fresh mii-diag output. the networking-team was
>faster and rebooted the systems before i had a chance to get the
>diagnostics :((
>
>
>
>--__--__--
>
>_______________________________________________
>eepro100 mailing list
>[email protected]
>http://www.scyld.com/mailman/listinfo/eepro100
>
>
>End of eepro100 Digest
>
>  
>