From: Matthias Kleine <kleine_matthias@gmx.de>
To: linux-smp@vger.kernel.org
Subject: Re: Why is "noapic" with some Dual P3 boards necessary?
Date: Tue, 29 Oct 2002 18:42:54 +0000 (UTC) [thread overview]
Message-ID: <200210301950.49150.kleine_matthias@gmx.de> (raw)
In-Reply-To: <200210291703.g9TH3Np26310@bach.leonora.org>
On Tuesday 29 October 2002 18:03, Vladimir G. Ivanovic wrote:
> It is not necessary to boot a CUV4X-DLS board with the "noapic" option.
>
> I have been running a CUV4X-DLS board (== CUV4X-D + LAN + SCSI) for over
> a year now with APIC. You must however fall back to MPS 1.1 from the
> default MPS 1.4. (It's a BIOS setting.)
>
> I suspect that a CUV4X-D board will have the same behavior.
Without noapic as kernel option
- my eth0 and ippp0 devices do not work
- my NVIDIA driver does not work
With noapic (no other changes) everything works quite
fine. I think you need a _very strong_ reason to convince
me that noapic is not necessary with the CUV4X-D.
--
______ ______
/_ _//_ _/
Ma / / / / hias
/_/ /_/
next prev parent reply other threads:[~2002-10-29 18:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 11:08 Why is "noapic" with some Dual P3 boards necessary? Matthias Kleine
2002-10-27 11:42 ` Alan Cox
2002-10-29 17:03 ` Vladimir G. Ivanovic
2002-10-29 18:42 ` Matthias Kleine [this message]
2002-10-29 18:50 ` Dr. Michael Weller
2002-10-30 19:20 ` Bill Davidsen
2002-10-30 22:11 ` Matthias Kleine
2002-10-30 23:48 ` Alan Cox
2002-10-31 2:54 ` vladimir
2002-10-31 3:27 ` Eff Norwood
2002-11-02 19:18 ` Vladimir G. Ivanovic
2002-10-31 20:29 ` Bill Davidsen
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=200210301950.49150.kleine_matthias@gmx.de \
--to=kleine_matthias@gmx.de \
--cc=linux-smp@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