From: Florian Attenberger <valdyn@gmail.com>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: any known issues with leap seconds in 2.6.10?
Date: Tue, 3 Jul 2007 18:47:10 +0200 [thread overview]
Message-ID: <20070703164710.GA18585@master.home> (raw)
In-Reply-To: <468A7145.7030606@nortel.com>
On Tue, Jul 03, 2007 at 11:54:45AM -0400, Chris Friesen wrote:
>
> I'm just wondering if anyone knows of issues with leap second handling in
> 2.6.10. We just had a field incident where a couple of quad-x86 machines
> went down at just before midnight (UTC) on June 30th...which is when leap
> seconds would normally be applied.
>
> From our logs it looks like something went crazy while holding the xtime
> lock.
>
> If anyone knows of issues with that code I'd love to hear about it.
>
> Thanks,
>
> Chris
look at the thread '2.6.21.5 june 30th to july 1st date hang'
prev parent reply other threads:[~2007-07-03 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 15:54 any known issues with leap seconds in 2.6.10? Chris Friesen
2007-07-03 16:47 ` Florian Attenberger [this message]
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=20070703164710.GA18585@master.home \
--to=valdyn@gmail.com \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.