From: Thomas Gleixner <tglx@linutronix.de>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Clemens Koller <clemens.koller@anagramm.de>,
Chris Wright <chrisw@sous-sol.org>, Uli Luckas <u.luckas@road.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.21.5 june 30th to july 1st date hang?
Date: Thu, 05 Jul 2007 22:10:16 +0200 [thread overview]
Message-ID: <1183666216.3289.41.camel@chaos> (raw)
In-Reply-To: <468D2EF1.7050908@nortel.com>
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
next prev parent reply other threads:[~2007-07-05 20:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 12:44 2.6.21.5 june 30th to july 1st date hang? Fortier,Vincent [Montreal]
2007-07-03 12:55 ` Fortier,Vincent [Montreal]
2007-07-03 13:05 ` Clemens Koller
2007-07-03 14:51 ` Fortier,Vincent [Montreal]
2007-07-03 13:56 ` Uli Luckas
2007-07-03 13:59 ` Florian Attenberger
2007-07-03 14:20 ` Arne Georg Gleditsch
2007-07-03 15:02 ` Florian Attenberger
2007-07-03 15:26 ` Arne Georg Gleditsch
2007-07-03 15:36 ` Fortier,Vincent [Montreal]
2007-07-03 17:19 ` Dave Jones
2007-07-03 19:28 ` Chris Friesen
2007-07-03 21:02 ` Chris Friesen
2007-07-03 21:02 ` Chuck Ebbert
2007-07-04 1:06 ` Fortier,Vincent [Montreal]
2007-07-04 8:56 ` Uli Luckas
2007-07-04 16:53 ` Chris Wright
2007-07-05 14:13 ` Clemens Koller
2007-07-05 17:48 ` Chris Friesen
2007-07-05 18:34 ` Clemens Koller
2007-07-05 20:10 ` Thomas Gleixner [this message]
2007-07-05 21:02 ` Chris Friesen
2007-07-05 21:17 ` Thomas Gleixner
2007-07-05 22:28 ` Ernie Petrides
2007-07-05 22:49 ` Chris Friesen
2007-07-05 23:12 ` Ernie Petrides
2007-07-05 23:45 ` Chris Friesen
2007-07-06 5:16 ` Thomas Gleixner
2007-07-06 5:17 ` Thomas Gleixner
2007-07-06 15:47 ` Chris Friesen
2007-07-06 20:03 ` Ernie Petrides
2007-07-03 15:59 ` Chris Friesen
2007-07-03 16:00 ` Fortier,Vincent [Montreal]
2007-07-03 16:03 ` Chris Friesen
2007-07-03 17:28 ` Chris Friesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1183666216.3289.41.camel@chaos \
--to=tglx@linutronix.de \
--cc=cfriesen@nortel.com \
--cc=chrisw@sous-sol.org \
--cc=clemens.koller@anagramm.de \
--cc=linux-kernel@vger.kernel.org \
--cc=u.luckas@road.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox