Re: Transmit timeout with E1000

[Erik Mouw <erik@harddisk-recovery.com>]

On Wed, Jan 11, 2006 at 02:22:08PM +0100, Erik Mouw wrote:
> On Wed, Jan 11, 2006 at 01:59:46PM +0100, Erik Mouw wrote:
> > On Tue, Jan 10, 2006 at 09:46:29AM -0800, Jesse Brandeburg wrote:
> > > sorry to hear you're having a problem, and cool, thanks for the test,
> > > we'll have to try it here.  We've classically had problems reproducing the
> > > athlon based hangs.
> > 
> > Athlon based or Athlon-on-VIA-KT400 based? We have an E1000 dual
> > interface server adapter on a dual Athlon with AMD 762 chipset running
> > fine, and also the same kind of adapter on a dual Athlon64 with
> > AMD-8111 chipset running fine.
> 
> FWIW: I just found out that we have a desktop with similar hardware
> that doesn't have TX timeouts.
> 
> Same mainboard (Asrock K7VT4APro), same AMD Athlon XP 2000+ CPU (though
> it appears to be underclocked at 1250 MHz instead of 1666 MHz, probably
> a jumper problem), different E1000 adapter (8086:1076 vs. 8086:107c),
> different kernel version (2.4.24 vs. 2.6.15).

I just lowered the CPU speed of my own workstation to 1250 MHz, but
that doesn't make a difference.

Here's an easy way to reproduce the problem:

  rsh otherhost dd if=/dev/zero > /dev/null

That usually triggers a transmit timeout in less than 30 seconds.

Data transfers the other direction (rsh otherhost dd of=/dev/null <
/dev/zero) don't trigger the problem.

The system only recovers after the Netdev watchdog found out that the
transmit timed out. However, the e1000 register dump starts about 4 to
5 seconds earlier: a possible workaround would be to trigger the
timeout code path as soon as the register dump starts.


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click