Re: 2.6.21.5 june 30th to july 1st date hang?

Chris Friesen
2007-07-05T21:03:17Z

Thomas Gleixner wrote:

> It only happens with CONFIG_HIGHRES_TIMERS=y otherwise clock_was_set()
> is a NOP. So only the 2.6.21 kernel and i386 and ARM are affected.

Are you certain?

Vanilla 2.6.10 shows a clock_was_set() function. Does it just not call
the dangerous code or something?

Also, our modified 2.6.10 has the high res timers patch applied, but the
config option is turned off and we were still affected.

Chris