From: "Nick Warne" <nick@ukfsn.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3 RT8139too NIC problems [NOT resolved]
Date: Thu, 26 Feb 2004 18:30:10 -0000 [thread overview]
Message-ID: <403E3B32.1845.1F424323@localhost> (raw)
In-Reply-To: <20040226101330.20190d34@dell_ss3.pdx.osdl.net>
> yes, that is the pre-NAPI driver. You seem to be the only one having
> problems with the NAPI driver, so please help getting it fixed.
>
OK, please what do I need to do? I did build with debug, but dmesg
gets filled up so fast I have lost the logs. Also, when I do use the
new 8139too.c driver, the box (my gateway) is unusable for any type
of network traffic load.
So I will need to do it in one hit to grab the info and switch back
again.
Thanks for reply - I want to help and reolve this too...
Nick
--
"When you're chewing on life's gristle,
Don't grumble,
Give a whistle
And this'll help things turn out for the best."
next parent reply other threads:[~2004-02-26 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <403E34F8.31130.1F29EF00@localhost>
[not found] ` <20040226101330.20190d34@dell_ss3.pdx.osdl.net>
2004-02-26 18:30 ` Nick Warne [this message]
2004-02-23 20:18 2.6.3 RT8139too NIC problems [NOT resolved] Nick Warne
2004-02-26 17:53 ` Stephen Hemminger
2004-02-26 18:07 ` 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=403E3B32.1845.1F424323@localhost \
--to=nick@ukfsn.org \
--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.