Cc: Rafael J. Wysocki <rjw@...>, Jeff Chua <jeff.chua.linux@...>, <rusty@...>, <vatsa@...>, <zwane@...>, kernel list <linux-kernel@...>, Len Brown <lenb@...>
On Tue, 2007-09-04 at 09:27 +0200, Pavel Machek wrote:
Ok, I can reproduce it and I tracked down what happens:
When the CPU goes offline, the clock event source for this CPU (lapic)
is removed from the clock events framework. This also clears the
information that the CPU is using C-States which stop the local APIC
timer.
Now you put the CPU online again and the local APIC timer is used, but
the C-State information is not evaluated again in ACPI. This means that
the clock events code does not know that the APIC might stop. In the
worst case this will happen and make the CPU wait for timer interrupts
forever.
The problem only appears when you are on battery (c3/c4 available) or on
those broken machines, where C2 is in reality C3 (e.g. akpm's VAIO)
I have an yet untested fix, which preserves the broadcast state across
the offline state, but Len is looking into it as well, whether we can
just reevaluate the power states (and the broadcast flags) when a cpu
becomes online again. If Len can do that easily for 2.6.23, I'd prefer
that.
tglx
-
