"Nick Warne" <nick@ukfsn.org> writes:

> > Thanks. Umm.. strange, already NAPI reverted.
> > Does these patches change the behavior?
> > 
> > debug + revert01 + revert02 + revert03
> 
> **BINGO**
> 
> Excellent.  patch03 has stopped the timeouts.  I have just tested.  I 
> moved (via ftp) a 30MB file from network -> eth0, and at the same 
> time downloaded a 30MB file (via httpd) from the Internet -> eth1.
> 
> I was getting 10Mbs internal, and 30Kbs external (as expected).  NO 
> TIMEOUTS :) :)
> 
> Before, just the internal FTP timed out in 5 seconds.
> 
> dmesg is basically very quiet:
> 
> http://www.linicks.net/8139too_debug/bingo.txt
> 
> > after
> > 
> > debug + revert01 + revert02 + revert03 + revert04
> 
> I haven't applied patch04.
> 
> I will continue to run the debug kernel.

Ok, thanks for debugging. Looks like this problem is not 8139too.
And same problem should happen with the old driver (probably, it appear
with "max_interrupt_work=1").

Umm... I guess this problem is miss config of Edge/Level-Trigger or
something.  Sorry, I don't know detail.


Jeff, I think CONFIG_8139TOO_NAPI is useful for now.
What do you think of these? Any idea?

8139too-config-napi.patch      - add CONFIG_8139TOO_NAPI
                                 (dirty #ifdef, the cleanup may be needed)
8139too-useful-txtimeout.patch - more debug info for rtl8139_tx_timeout()

Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>