From: Jeff Garzik <jgarzik@pobox.com>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Vergoz Michael <mvergoz@sysdoor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 8139too.c patch for kernel 2.4.19
Date: Mon, 18 Nov 2002 10:55:52 -0500 [thread overview]
Message-ID: <3DD90D88.9020205@pobox.com> (raw)
In-Reply-To: <028901c28ead$10dfbd20$76405b51@romain>
Andreas Steinmetz wrote:
> Jeff,
> just as a hint: I do have a SiS based UP test system around that
> misbehaves with IO-APIC enabled.
> See
> http://www.msi.com.tw/program/products/slim_pc/slm/pro_slm_detail.php?UID=134&MODEL=MS-6232
>
> for more system details.
> From the back of my head: with IO-APIC enabled and 3 RTL8139 (one on
> board, the other two PCI) the NICs get assigned IRQs 17 and 18 but don't
> seem to receive any interrupt at all. Without IO-APIC all three NICs
> share IRQ 11 and do work. Further details on request (very low priority
> problem for me). Oh, nearly forgot: kernel is 2.4.20rc1.
That's not going to be fixed by Michael's patch... Any IOAPIC-related
problems cannot be fixed at the driver level, but must be fixed by a
BIOS update (or possibly an IOAPIC code fix). Sometimes vendors do not
bother do even wire the IOAPIC when it is a uniprocessor board :(
Jeff
next prev parent reply other threads:[~2002-11-18 15:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 2:49 8139too.c patch for kernel 2.4.19 Vergoz Michael
2002-11-18 7:34 ` Jeff Garzik
2002-11-18 8:50 ` Vergoz Michael
2002-11-18 17:04 ` Ducrot Bruno
2002-11-18 9:05 ` Jeff Garzik
2002-11-18 11:17 ` Andreas Steinmetz
2002-11-18 15:55 ` Jeff Garzik [this message]
2002-11-18 16:12 ` Andreas Steinmetz
2002-11-18 16:47 ` Jeff Garzik
2002-11-18 17:25 ` Jeff Garzik
2002-11-18 17:51 ` Vergoz Michael
2002-11-18 18:14 ` Jeff Garzik
2002-11-18 20:04 ` Vergoz Michael
2002-11-18 21:15 ` Jeff Garzik
2002-11-18 21:34 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-11-18 17:15 Manfred Spraul
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=3DD90D88.9020205@pobox.com \
--to=jgarzik@pobox.com \
--cc=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mvergoz@sysdoor.com \
/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