Messages in this thread | | | Subject | Re: 2.6.21.5 june 30th to july 1st date hang? | From | Thomas Gleixner <> | Date | Thu, 05 Jul 2007 22:10:16 +0200 |
| |
On Thu, 2007-07-05 at 11:48 -0600, Chris Friesen wrote: > Clemens Koller wrote: > > > Okay, we all survived Y2K and this little glitch. Puh! ;-) > > Can you please explain in which configuration this problem got triggered. > > As far as I can tell many kernel versions contained the source code bug. > (I'd like some more information on exactly what the problem was if > anyone cares to share..the proposed patch didn't give much in the way of > specifics.)
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.
tglx
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |