From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: RTL8139, IRQ sharing, etc.
Date: Thu, 7 Jun 2001 01:52:45 +0200 [thread overview]
Message-ID: <20010607015245.B11765@emma1.emma.line.org> (raw)
In-Reply-To: <20010529215647.A3955@greenhydrant.com> <3B147F80.31EC7520@mandrakesoft.com> <20010531104437.C10057@emma1.emma.line.org> <3B17D471.D636E208@mandrakesoft.com> <20010601203127.B17137@emma1.emma.line.org>
In-Reply-To: <20010601203127.B17137@emma1.emma.line.org>; from matthias.andree@stud.uni-dortmund.de on Fri, Jun 01, 2001 at 20:31:27 +0200
On Fri, 01 Jun 2001, Matthias Andree wrote:
> Not sure if it's related to IRQ sharing or another initialization issue.
Looks like IRQ sharing is still in the play.
Yesterday, I purchased a pair of used 3C905TXs, replaced the RTL 8139 by
the 3C905, and got complaints by the 3C905 about "eth0: Interrupt posted
but not delivered -- IRQ blocked by another device?" (Linux 2.2.19). The
other card on the same IRQ is a Brooktree 878.
I then swapped the Bt878 and the 3C900 (not 3C905!) and got no more
complaints, now, the Bt878 can keep its IRQ to itself, and the two 3Com
cards share the IRQ. Seems both NICs are fine. TV is also fine. Strange.
Might the BT 878 PCI AND the NVidia AGP card be the culprits?
Cheers,
Matthias
prev parent reply other threads:[~2001-06-06 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 4:56 2.4.5 still breaks dhcpcd with 8139too David Rees
2001-05-30 5:05 ` Jeff Garzik
2001-05-30 5:21 ` David Rees
2001-05-31 8:44 ` Matthias Andree
2001-06-01 17:44 ` Jeff Garzik
2001-06-01 18:31 ` Matthias Andree
2001-06-06 23:52 ` Matthias Andree [this message]
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=20010607015245.B11765@emma1.emma.line.org \
--to=matthias.andree@stud.uni-dortmund.de \
--cc=jgarzik@mandrakesoft.com \
--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 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®