Op 3 aug. 2012, om 09:21 heeft Koen Kooi <[email protected]> het volgende geschreven:
> > Op 3 aug. 2012, om 09:16 heeft Daniel Mack <[email protected]> het volgende > geschreven: > >> On 30.03.2012 15:27, Santosh Shilimkar wrote: >>> For coupled cpuidle to work when both cpus are active, it needs a global >>> timer >>> that can handle events for both cpus. This timer is used as the broadcast >>> clock-event when the per-cpu timer hardware stop in low power states. >>> Set the cpumask of clockevent_gpt to all cpus, set the rating correctly, and >>> set the irq to allow the clockevent core to determine the affinity of the >>> timer. >> >> These patches made it to mainline now, shortly befor 3.6-rc1, and it >> breaks boot on my AM33xx board. >> >> Once I revert 1/3, the board boots again but crashes with the Ooops >> below. With the entire series reverted, everything works again as >> expected. Any idea? >> >> The upstream commit ids are >> >> 11d6ec2e "ARM: OMAP: timer: allow gp timer clock-event to be used on >> both cpus" >> 5b4d5bcc "ARM: OMAP4: CPUidle: add synchronization for coupled idle states" >> b93d70ae "ARM: OMAP4: CPUidle: Open broadcast clock-event device." > > I've had boot problems with cpuidle enabled as well, what happens if you > disable it? Is the revert still needed in that case? To answer my own question: No, the reverts aren't needed if you disable cpuidle.-- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
