From: "mobil@wodkahexe.de" <mobil@wodkahexe.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc4 No local APIC present or hardware disabled
Date: Thu, 14 Oct 2004 13:59:46 +0200 [thread overview]
Message-ID: <20041014135946.1de129f0.mobil@wodkahexe.de> (raw)
In-Reply-To: <Pine.LNX.4.58L.0410132311190.17462@blysk.ds.pg.gda.pl>
On Thu, 14 Oct 2004 00:59:13 +0100 (BST)
"Maciej W. Rozycki" <macro@linux-mips.org> wrote:
> On Tue, 12 Oct 2004, mobil@wodkahexe.de wrote:
>
> > after upgrading to 2.6.9-rc4 I'm getting the following message in
> > dmesg:
> >
> > No local APIC present or hardware disabled
> >
> > 2.6.9-rc3 and older kernels did not show this message. They showed:
> > Local APIC disabled by BIOS -- reenabling.
> > Found and enabled local APIC!
>
> As you've already been told, the local APIC is not being enabled by
> default anymore. I think this change may be unfortunate for users, so
> I've proposed the change to be applied for systems using ACPI and then
> verbosely, so that the reason for the APIC being kept disabled is
> clear. Unfortunately I have no system available for testing that uses
> ACPI, so I'm asking whether you could participate in testing of the
> following patch. With the patch applied, you should either get a
> warning or the local APIC running (e.g. if you disable ACPI by
> specifying "noacpi"). Does the patch work for you? For anyone else?
>
> Maciej
>
> patch-2.6.9-rc4-lapic-5
>
> <snip patch>
Hi,
i tested your patch, but it did not apply correctly to a clean 2.6.9-rc4
tree for me. (patch -Np1 -i ../patch-2.6.9-rc4-lapic-5)
I applyed it manually, and when rebooting, i get the following:
Local APIC won't be reenabled, ...
You can...
When booting with 'pci=noacpi':
Local APIC won't be reenabled, ...
You can...
When booting with 'acpi=off':
no output when running dmesg|grep -i apic
Regards, Sebastian
next prev parent reply other threads:[~2004-10-14 9:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 17:54 mobil
2004-10-12 16:11 ` Mikael Pettersson
2004-10-12 16:15 ` Prakash K. Cheemplavam
2004-10-13 23:59 ` Maciej W. Rozycki
2004-10-14 10:52 ` Mikael Pettersson
2004-10-14 22:27 ` Maciej W. Rozycki
2004-10-15 12:26 ` Alan Cox
2004-10-15 13:53 ` Mikael Pettersson
2004-10-24 15:44 ` Maciej W. Rozycki
2004-10-24 15:11 ` Alan Cox
2004-10-25 14:08 ` Mikael Pettersson
2004-10-14 11:59 ` mobil [this message]
2004-10-14 21:25 ` Maciej W. Rozycki
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=20041014135946.1de129f0.mobil@wodkahexe.de \
--to=mobil@wodkahexe.de \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.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
all inboxes | Powered by JetHome®