[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b93822910703210604w6bcc2e1dt4cac7f9f9295edf8@mail.gmail.com>
Date: Wed, 21 Mar 2007 14:04:19 +0100
From: "Stefan Prechtel" <stefan.prechtel@...glemail.com>
To: "Andi Kleen" <ak@...e.de>
Cc: tglx@...utronix.de,
"Grzegorz Chwesewicz" <grzegorz.chwesewicz@...lan.com>,
linux-kernel@...r.kernel.org, mingo@...e.hu,
"Len Brown" <lenb@...nel.org>, "john stultz" <johnstul@...ibm.com>
Subject: Re: BUG lapic: Can't boot on battery (2.6.21-rc{1,2,3,4})
2007/3/21, Andi Kleen <ak@...e.de>:
> On Wednesday 21 March 2007 12:14, Thomas Gleixner wrote:
> > On Wed, 2007-03-21 at 11:37 +0100, Andi Kleen wrote:
> > > > The BIOS/ACPI is broken and does only expose C1, which should not
> > > > switch off LAPIC. The BIOS is switching into deeper C-States behind the
> > > > kernels back somehow.
> > >
> > > Hmm, perhaps we can check AMD && (cstate >= 2 || has a battery) ?
> > > Should be doable by looking up the battery object in ACPI
> >
> > Which makes us rely on another ACPI feature. What guarantees that the
> > ACPI tables are correct for this one ?
>
> Nothing, but wrong C2 and wrong battery state together seems unlikely.
>
> -Andi
>
Hello
I uploaded the output of dmesg (kernel 2.6.21-rc4-git5) (battery / ac)
and dmidecode
I can boot on battery with nolapic_timer and the second core is online, too.
/proc/acpi/processor/C000/ shows the same as before but
/proc/interrupts has changed:
(battery)
CPU0 CPU1
0: 47131 0 local-APIC-edge-fasteoi timer
LOC: 0 46978
(ac)
CPU0 CPU1
0: 59137 0 local-APIC-edge-fasteoi timer
LOC: 0 58984
- Stefan Prechtel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists