[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <468D5C72.4030200@nortel.com>
Date: Thu, 05 Jul 2007 15:02:42 -0600
From: "Chris Friesen" <cfriesen@...tel.com>
To: Thomas Gleixner <tglx@...utronix.de>
CC: Clemens Koller <clemens.koller@...gramm.de>,
Chris Wright <chrisw@...s-sol.org>,
Uli Luckas <u.luckas@...d.de>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.21.5 june 30th to july 1st date hang?
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists