From: Stephen Hemminger <shemminger@osdl.org>
To: "Nick Warne" <nick@ukfsn.org>
Cc: linux-kernel@vger.kernel.org, "Jeff Garzik" <jgarzik@pobox.com>,
"Frédéric L. W. Meunier" <1@pervalidus.net>
Subject: Re: 2.6.3 RT8139too NIC problems [NOT resolved]
Date: Thu, 26 Feb 2004 09:53:58 -0800 [thread overview]
Message-ID: <20040226095358.2bb53915@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <403A6011.5674.103225D9@localhost>
The current 2.6.3 driver uses NAPI, and maybe that is related to your troubles.
What exactly is the hardware config (lspci output)?
There are debug messages produced, something like:
eth0: Tx queue start entry 0 dirty entry 13
do you see these in dmesg output? or change your syslog.conf to capture
debug kernel messages to a different file.
Also, rebuild with RTL8139_DEBUG defined to pick up more info.
Seems like interrupts are getting disabled somehow.
next prev parent reply other threads:[~2004-02-26 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 20:18 Nick Warne
2004-02-26 17:53 ` Stephen Hemminger [this message]
2004-02-26 18:07 ` Nick Warne
[not found] <403E34F8.31130.1F29EF00@localhost>
[not found] ` <20040226101330.20190d34@dell_ss3.pdx.osdl.net>
2004-02-26 18:30 ` 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=20040226095358.2bb53915@dell_ss3.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=1@pervalidus.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@ukfsn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®