From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: earny@net4u.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc[1-4]: boot fail with (lapic && on_battery)
Date: Wed, 01 Nov 2006 00:27:07 +0000 [thread overview]
Message-ID: <1162340827.2962.13.camel@localhost.portugal> (raw)
In-Reply-To: <200610312227.54617.list-lkml@net4u.de>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
On Tue, 2006-10-31 at 22:27 +0100, Ernst Herzberg wrote:
> With 2.6.18.x everything works fine.
>
> But 2.16.19-rc does not boot if the laptop runs on battery _and_ lapic
> is
> defined as boot parameter.
>
> The kernel loads and starts, for a fraction of a second some messages
> appears,
> then the screen goes blank and nothing more happens.
>
> I'm unable to read the last message, screen blanking is to fast, but
> the
> 'picture' looks like that he stops near the messages where at the
> normal
> boot demsg "Local APIC disabled by BIOS -- you can enable it with
> "lapic""
> appears.
Hi,
If you don't enable lapic, you will see cat /proc/interrupts with
XT-PIC.
if you try enable lapic, somehow IRQ routing should change
and if /proc/interrupts still the same, with IRQs on XT-PIC.
I think, lapic still not enable and you just get problems.
Unless you know that lapic works, you should try it enable because it a
trap that just give you a problem.
Some years ago (2002/3) was a very common bug kernel try enable
automatically lapic (when BIOS don't) and computer hangs .
--
Sérgio M.B.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
next prev parent reply other threads:[~2006-11-01 0:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 21:27 2.6.19-rc[1-4]: boot fail with (lapic && on_battery) Ernst Herzberg
2006-11-01 0:27 ` Sergio Monteiro Basto [this message]
2006-11-01 1:14 ` Sergio Monteiro Basto
2006-11-01 1:04 ` Adrian Bunk
2006-11-01 2:05 ` Ernst Herzberg
2006-11-01 2:34 ` Adrian Bunk
2006-11-01 8:14 ` Ernst Herzberg
2006-11-14 6:59 ` Len Brown
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=1162340827.2962.13.camel@localhost.portugal \
--to=sergio@sergiomb.no-ip.org \
--cc=earny@net4u.de \
--cc=linux-kernel@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 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.