On Mon, Jul 22, 2013 at 11:58:47AM -0700, Stephen Boyd wrote: > On 07/22/13 11:45, Stephen Boyd wrote: > > Hmm. Is it too early to use hrtimers? Moving the hrtimer_start() into > > sched_clock_register() also causes the same crash. > > Yes that seems to be the problem. The vexpress board is setting up the > sched_clock in setup_arch() (via v2m_init_early) which runs before > hrtimers_init(). I've only tested this on boards that setup the timer in > the time_init() callback which runs after hrtimers_init(). Your patch > should be fine, although it would be nice if we didn't have callers > setting up the sched_clock so early. However, it _is_ the correct place to do it, as I've repeatedly stated. The reason for this is that the scheduler will have already read from sched_clock() by the time you get to timer_init() to seed its idea of the start time for PID0 - again, as I've explained multiple times. -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
