From: Mikael Pettersson <mikpe@csd.uu.se>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Mikael Pettersson <mikpe@csd.uu.se>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH][2.5-AC] Forced enable/disable local APIC
Date: Fri, 8 Nov 2002 14:22:59 +0100 [thread overview]
Message-ID: <15819.47795.543312.435264@kim.it.uu.se> (raw)
In-Reply-To: <Pine.LNX.4.44.0211080804280.27141-100000@montezuma.mastecende.com>
Zwane Mwaikambo writes:
> On Fri, 8 Nov 2002, Maciej W. Rozycki wrote:
>
> > Well, the "lapic" option should override the DMI setting, not the
> > APICBASE availability check. Anyway, I don't insist on this that much --
> > while I think consistency is good, none of the "*apic" options are
> > actually a necessity for me. If one needs the option, one may still cook
> > an appropriate patch oneself.
>
> I think the nolapic is definitely needed because i've come across a number
> of bug reports where the simplest solution would be to just disable the
> local apic.
People with broken boxes should send their DMI data to me so I can add
their boxes to the local APIC blacklist in dmi_scan.c. "nolapic" is
simply a workaround for the absence of this DMI data.
Notice how silent the Inspiron 8k users are now that the DMI black
list is implemented...
/Mikael
next prev parent reply other threads:[~2002-11-08 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 2:39 Zwane Mwaikambo
2002-11-06 12:26 ` Maciej W. Rozycki
2002-11-07 16:14 ` Mikael Pettersson
2002-11-07 16:25 ` Maciej W. Rozycki
2002-11-07 16:41 ` Zwane Mwaikambo
2002-11-07 16:50 ` Mikael Pettersson
2002-11-07 21:40 ` Zwane Mwaikambo
2002-11-08 12:21 ` Maciej W. Rozycki
2002-11-08 13:05 ` Zwane Mwaikambo
2002-11-08 13:22 ` Mikael Pettersson [this message]
2003-05-31 3:28 ` Brian J. Murrell
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=15819.47795.543312.435264@kim.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=zwane@holomorphy.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
all inboxes | Powered by JetHome®