From: "Sérgio Monteiro Basto" <sergiomb@netcabo.pt>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Len Brown <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: [ACPI] Re: [BKPATCH] LAPIC fix for 2.6
Date: Sun, 10 Oct 2004 22:19:43 +0100 [thread overview]
Message-ID: <1097443183.26647.31.camel@darkstar> (raw)
In-Reply-To: <Pine.LNX.4.58L.0410102000160.4217@blysk.ds.pg.gda.pl>
On Sun, 2004-10-10 at 20:04, Maciej W. Rozycki wrote:
> On Sun, 10 Oct 2004, Linus Torvalds wrote:
>
> > > Hi Linus, please do a
> > >
> > > bk pull bk://linux-acpi.bkbits.net/26-latest-release
> >
> > Ok, this version of the patch suddenly looks like a real bug-fix in that
> > it now makes the command line options "lapic"/"nolapic" a lot more
> > logical.
>
> Hmm, any particular reason to keep the local APIC disabled by default?
> Most BIOS vendors keep it disabled just because it's easier to get stuff
> set up this way -- with the APIC enabled you need to do the same steps to
> program the 8259As as with the APIC disabled, plus program the APIC
> itself, which provides no gain to BIOS itself or to DOS, so why bother?
>
> Maciej
>
The problem is: trying enable some local apic's (for example on via
mother boards on my laptop), cause many problem, like hang on boot (with
ACPI), hang on Fn-F3 (video switch), power-off fails, etc. and no one
knows how resolved the problem.
So keep it disable if BIOS vendors say so, can be reasonable idea.
--
Sérgio M. B.
next prev parent reply other threads:[~2004-10-10 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 17:35 [BKPATCH] LAPIC fix for 2.6 Len Brown
2004-10-10 17:45 ` Linus Torvalds
2004-10-10 19:04 ` Maciej W. Rozycki
2004-10-10 21:19 ` Sérgio Monteiro Basto [this message]
2004-10-11 1:44 ` [ACPI] " Maciej W. Rozycki
2004-10-11 2:44 ` Linus Torvalds
2004-10-11 0:47 ` Linus Torvalds
2004-10-11 11:42 ` [ACPI] " Andi Kleen
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=1097443183.26647.31.camel@darkstar \
--to=sergiomb@netcabo.pt \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=torvalds@osdl.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 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.