* 2.6.25-rc8-mm2 -- initcall acpi_init+0x0/0x216() returned with preemption imbalance
@ 2008-04-11 19:41 Miles Lane
2008-04-12 5:11 ` Andrew Morton
0 siblings, 1 reply; 2+ messages in thread
From: Miles Lane @ 2008-04-11 19:41 UTC (permalink / raw)
To: Andrew Morton, LKML, len.brown
Is this indicative of a kernel or hardware problem?
[ 0.279606] ACPI: Using IOAPIC for interrupt routing
[ 0.279789] initcall acpi_init+0x0/0x216() returned with preemption imbalance
[ 0.330789] ACPI: PCI Root Bridge [PCI0] (0000:00)
Thanks,
Miles
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: 2.6.25-rc8-mm2 -- initcall acpi_init+0x0/0x216() returned with preemption imbalance
2008-04-11 19:41 2.6.25-rc8-mm2 -- initcall acpi_init+0x0/0x216() returned with preemption imbalance Miles Lane
@ 2008-04-12 5:11 ` Andrew Morton
0 siblings, 0 replies; 2+ messages in thread
From: Andrew Morton @ 2008-04-12 5:11 UTC (permalink / raw)
To: Miles Lane; +Cc: LKML, len.brown, linux-acpi
On Fri, 11 Apr 2008 15:41:17 -0400 "Miles Lane" <miles.lane@gmail.com> wrote:
> Is this indicative of a kernel or hardware problem?
>
> [ 0.279606] ACPI: Using IOAPIC for interrupt routing
> [ 0.279789] initcall acpi_init+0x0/0x216() returned with preemption imbalance
> [ 0.330789] ACPI: PCI Root Bridge [PCI0] (0000:00)
>
That's a software bug. Something under acpi_init() has mismatched
preempt_disable/preempt_enable or mismatched spin_lock/spin_unlock, etc.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-04-12 5:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-04-11 19:41 2.6.25-rc8-mm2 -- initcall acpi_init+0x0/0x216() returned with preemption imbalance Miles Lane
2008-04-12 5:11 ` Andrew Morton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox