On Thu, 2011-04-28 at 23:04 +0200, Thomas Gleixner wrote: > On Thu, 28 Apr 2011, Bruno PrÃmont wrote: > > Timer List Version: v0.6 > > HRTIMER_MAX_CLOCK_BASES: 3 > > now at 1150126155286 nsecs > > > > cpu: 0 > > clock 0: > > .base: c1559360 > > .index: 0 > > .resolution: 1 nsecs > > .get_time: ktime_get_real > > .offset: 1304021489280954699 nsecs > > active timers: > > #0: def_rt_bandwidth, sched_rt_period_timer, S:01, enqueue_task_rt, swapper/1 > > # expires at 1304028703000000000-1304028703000000000 nsecs [in 1304027552873844714 to 1304027552873844714 nsecs] > > Ok, that expiry time is obviously bogus as it does not account the offset: > > So in reality it's: expires in: 6063592890015ns > > Which is still completely wrong. The timer should expire at max a > second from now. But it's going to expire in 6063.592890015 seconds > from now, which is pretty much explaining the after 2hrs stuff got > going again. > > But the real interesting question is why he heck is that timer on > CLOCK_REALTIME ???? It is initalized for CLOCK_MONOTONIC. > > /me suspects hrtimer changes to be the real culprit. I'm not seeing anything on right off, but it does smell like e06383db9ec591696a06654257474b85bac1f8cb would be where such an issue would crop up. Bruno, could you try checking out e06383db9ec, confirming it still occurs (and then maybe seeing if it goes away at e06383db9ec^1)? I'll keep digging in the meantime. thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
