public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ernst Herzberg <earny@net4u.de>
To: Len Brown <lenb@kernel.org>
Cc: Adrian Bunk <bunk@stusta.de>, Hugh Dickins <hugh@veritas.com>,
	"Michael S. Tsirkin" <mst@mellanox.co.il>,
	Pavel Machek <pavel@suse.cz>, Linus Torvalds <torvalds@osdl.org>,
	Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org, linux-pm@osdl.org,
	Martin Lorenz <martin@lorenz.eu.org>
Subject: Re: 2.6.19-rc <-> ThinkPads
Date: Wed, 1 Nov 2006 06:11:27 +0100	[thread overview]
Message-ID: <200611010611.30445.earny@net4u.de> (raw)
In-Reply-To: <200610312215.44454.len.brown@intel.com>

On Wednesday 01 November 2006 04:15, Len Brown wrote:
> The BIOS disables the LAPIC for a reason.
> A couple of years ago Linux made the mistake of enabling the LAPIC
> that the BIOS disabled, and all hell broke loose.
> We fixed that bug about a year ago, but left "lapic"
> to force it on for those where forcing it to be enabled actually
> works (eg. some folks want the NMI profiling on their IOAPIC-less  laptop)
>
> But if you force the lapic to be enabled, you are running the system
> in a mode not supported by the manufacturer and you are on your own.
>
> I don't see an indication that this is a bug.
> If it used to work and it is important to you,
>  then run the old software where it used to work --
> because chances are good that it worked by accident.

Maybe. But why does it boot with AC connected and lapic enabled, bot not if AC 
is disconnected and lapic enabled? If have no problem to run this laptop 
without lapic, i don't relly need it. But i wondering that this happens only 
if the machine runs (by accident:) on battery.

still bisecting, will report the result.

<earny>

  reply	other threads:[~2006-11-01  5:11 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061029231358.GI27968@stusta.de>
2006-10-30 13:56 ` 2.6.19-rc3: known unfixed regressions (v3) Michael S. Tsirkin
2006-10-30 15:27   ` Martin Lorenz
2006-10-30 16:17   ` Jun'ichi Nomura
2006-10-30 16:32     ` Michael S. Tsirkin
2006-10-30 17:20       ` Jun'ichi Nomura
2006-10-30 17:54         ` Michael S. Tsirkin
2006-10-30 16:44     ` Linus Torvalds
2006-10-30 17:34       ` Jun'ichi Nomura
2006-10-30 18:16         ` Linus Torvalds
2006-10-30 18:35           ` Adrian Bunk
2006-10-30 19:00             ` Michael S. Tsirkin
2006-10-30 19:06             ` Hugh Dickins
2006-10-31 12:47             ` Martin Lorenz
2006-10-30 18:58           ` Michael S. Tsirkin
2006-10-31 21:15           ` Michael S. Tsirkin
2006-11-01  3:01   ` 2.6.19-rc <-> ThinkPads Adrian Bunk
2006-11-01  3:15     ` Len Brown
2006-11-01  5:11       ` Ernst Herzberg [this message]
2006-11-01  5:26         ` Linus Torvalds
2006-11-01  5:54           ` Michael S. Tsirkin
2006-11-01  6:16             ` Linus Torvalds
2006-11-01 17:25               ` Andi Kleen
2006-11-01 18:12                 ` Michael S. Tsirkin
2006-11-01 18:25                 ` Linus Torvalds
2006-11-01 19:33                   ` Michael S. Tsirkin
2006-11-01 19:44                     ` Linus Torvalds
2006-11-01 19:34                   ` Andi Kleen
2006-11-01 19:52                     ` Linus Torvalds
2006-11-01 21:15                       ` Andi Kleen
2006-11-01 22:35               ` Bill Davidsen
2006-11-01  6:18             ` Michael S. Tsirkin
2006-11-01  9:33               ` Pavel Machek
2006-11-01 12:02                 ` Michael S. Tsirkin
2006-11-01 17:17               ` Andi Kleen
2006-11-01 13:50           ` Stefan Seyfried
2006-11-01 16:36     ` Hugh Dickins
2006-11-04  3:49     ` 2.6.19-rc <-> ThinkPads, summary Adrian Bunk
2006-11-04 13:51       ` Hugh Dickins
2006-11-04 14:04       ` Russell King
2006-11-05  6:23         ` Adrian Bunk
2006-11-17  1:53       ` 2.6.19-rc <-> ThinkPads, (related Ubuntu bug report) Mark Stosberg

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=200611010611.30445.earny@net4u.de \
    --to=earny@net4u.de \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=hugh@veritas.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@osdl.org \
    --cc=martin@lorenz.eu.org \
    --cc=mst@mellanox.co.il \
    --cc=pavel@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox