From: Keith Owens <kaos@ocs.com.au>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problem with ServerWorks CNB20LE and lost interrupts
Date: Tue, 15 Jan 2002 08:04:50 +1100 [thread overview]
Message-ID: <31989.1011042290@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 14 Jan 2002 15:19:00 BST." <Pine.GSO.3.96.1020114150024.16706C-100000@delta.ds2.pg.gda.pl>
On Mon, 14 Jan 2002 15:19:00 +0100 (MET),
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl> wrote:
> The "noapic" option should probably get removed -- it was meant as a
>debugging aid (as many of the "no*" options) at the early days of I/O APIC
>support, I believe... Now the support is pretty stable.
Intel 440GX chipsets hang during SCSI probe with UP kernels unless you
use noapic. It works with SMP but many installers use UP kernels.
Removing noapic will break install on all 440GX machines, there are a
lot of them out there.
next prev parent reply other threads:[~2002-01-14 21:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 14:53 Problem with ServerWorks CNB20LE and lost interrupts Zwane Mwaikambo
2002-01-11 14:55 ` Zwane Mwaikambo
2002-01-11 17:32 ` Jim Studt
2002-01-13 9:39 ` Zwane Mwaikambo
2002-01-14 0:29 ` Jim Studt
2002-01-14 6:42 ` Zwane Mwaikambo
2002-01-14 9:10 ` Zwane Mwaikambo
2002-01-14 12:14 ` Maciej W. Rozycki
2002-01-14 13:44 ` Zwane Mwaikambo
2002-01-14 14:19 ` Maciej W. Rozycki
2002-01-14 14:23 ` Zwane Mwaikambo
2002-01-14 14:43 ` Alan Cox
2002-01-14 15:28 ` Maciej W. Rozycki
2002-01-14 15:31 ` Zwane Mwaikambo
2002-01-14 15:49 ` Maciej W. Rozycki
2002-01-14 16:14 ` Jim Studt
2002-01-14 21:04 ` Keith Owens [this message]
2002-01-15 11:44 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2002-01-11 9:22 Jim Studt
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=31989.1011042290@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
/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.