From: "Nick Warne" <nick@ukfsn.org>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.3 - 8139too timeout debug info
Date: Sun, 29 Feb 2004 13:05:19 -0000 [thread overview]
Message-ID: <4041E38F.31264.2D8C0D2E@localhost> (raw)
In-Reply-To: <87vflqt61a.fsf@devron.myhome.or.jp>
> 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.
Thank you :)
Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
next prev parent reply other threads:[~2004-02-29 13:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4041BAA6.28283.2CEC419B@localhost>
[not found] ` <87fzcut9ua.fsf@devron.myhome.or.jp>
2004-02-29 11:57 ` 2.6.3 - 8139too timeout debug info Nick Warne
2004-02-29 12:38 ` OGAWA Hirofumi
2004-02-29 13:05 ` Nick Warne [this message]
2004-02-29 18:28 ` OGAWA Hirofumi
2004-03-01 18:29 ` Nick Warne
2004-03-22 21:17 ` Jeff Garzik
2004-03-22 22:51 ` OGAWA Hirofumi
2004-03-31 19:42 ` Christian Gut
2004-04-01 3:56 ` OGAWA Hirofumi
2004-04-04 17:02 ` OGAWA Hirofumi
2004-03-23 21:07 Nick Warne
-- strict thread matches above, loose matches on Subject: below --
2004-02-27 17:31 Nick Warne
2004-02-27 17:40 ` Matt H.
2004-02-27 17:50 ` Nick Warne
2004-02-28 17:41 ` OGAWA Hirofumi
2004-02-28 18:47 ` Nick Warne
2004-02-29 7:58 ` OGAWA Hirofumi
2004-02-29 8:09 ` OGAWA Hirofumi
2004-02-29 11:09 ` Nick Warne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4041E38F.31264.2D8C0D2E@localhost \
--to=nick@ukfsn.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.