public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: earny@net4u.de
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: 2.6.19-rc[1-4]: boot fail with (lapic && on_battery)
Date: Tue, 14 Nov 2006 01:59:59 -0500	[thread overview]
Message-ID: <200611140159.59926.len.brown@intel.com> (raw)
In-Reply-To: <200610312227.54617.list-lkml@net4u.de>

On Tuesday 31 October 2006 16:27, 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.

> Local APIC disabled by BIOS -- you can enable it with "lapic"

The BIOS is advising you here that it is a bad idea to enable the LAPIC on this system.
So why are you using the "lapic" boot parameter?

If you are running an CONFIG_SMP kernel with LAPIC enabled and deep C-states
(such as are available on Thinkpads when on battery mode), you will
run into the following bug:

http://bugzilla.kernel.org/show_bug.cgi?id=7376

As this is not new, the mystery is really why you see no problems in 2.6.18.
Perhaps you can forward the contents of /proc/interrupts for 2.6.18 with "lapic"
and we can see if the timer and the LOC are in sync or not when on battery?
/proc/acpi/processor/*/power will also tell us about the C-states --
dump it for both AC and battery mode.

thanks,
-Len

      parent reply	other threads:[~2006-11-14  6:57 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
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 [this message]

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=200611140159.59926.len.brown@intel.com \
    --to=len.brown@intel.com \
    --cc=earny@net4u.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox