Hi.

I'm using a Dual-DualCore-Opteron System on a Tyan S2895 mainboard 
(Thunder K8WE, see 
http://www.tyan.com/products/html/thunderk8we_spec.html for specifications).

It has two Gigabit Ethernet ports.
One is connected to the Chipset connected to CPU1 (Nvidia nForce 
Professional 2200), the other to the Chipset connected to CPU2 (Nvidia 
nForce Professional 2050); there's also a 3rd chipset, AMD 8131 but that 
should be unimportant here.


When you look at the kern.log you see that I've some problems with the 
Networkcard (NETDEV WATCHDOG: eth?: transmit timed out). So I'm writing 
to you, as I'm using the forcedeth driver :-) .

Ok here some description:
I'm using a 3 Mbit down / 512 Kbit up ADSL connection via PPPoE (the 
experimental one) (see my kernel config).
The problem always occurs on the eth interface that is connected to my 
ADSL-modem, and then internet fails, and it takes long time until I can 
reconnect it (even when doing poff/pon or so)
btw: I'm using Debian sid, everything in the neweset versions, the 
newest kernel (2.6.13.4), too.
Ok,.. when doing "normal" internet work, like downloading big files, or 
www browsing or chatting, et cetera ... everything just works fine...

BUT (!!) ;-) .... when I'm starting mldonkey it doesn't take long until 
I get the errors I noticed in my kern.log. The NETDEV WATCHDOG messages 
are repeating until I stop mldonkey.

Now one could say, that this is a mldonkey problem but I don't think so:
1) There are no bugreports that tell about the same problem.
2) mldonkey is running (of course) as non-root and should not be able to 
crash networt inferfaces and internet.
3) With my old computer (using Realtek bulk network card) with the same 
mldonkey version and the sam mldonkey-config, everything just worked fine.

Ok,.. I have no idea, but perhaps the reason is the number of 
connections (TCP/IP) that mldonkey establishes.

Any idea? Would be great if you could help. If you need further 
material, simply ask :-)


Best wishes,
Christoph Anton Mitterer.

btw: Please CC me, as I haven't subscribed to the list (... yet).