* any known issues with leap seconds in 2.6.10?
@ 2007-07-03 15:54 Chris Friesen
2007-07-03 16:47 ` Florian Attenberger
0 siblings, 1 reply; 2+ messages in thread
From: Chris Friesen @ 2007-07-03 15:54 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: any known issues with leap seconds in 2.6.10?
2007-07-03 15:54 any known issues with leap seconds in 2.6.10? Chris Friesen
@ 2007-07-03 16:47 ` Florian Attenberger
0 siblings, 0 replies; 2+ messages in thread
From: Florian Attenberger @ 2007-07-03 16:47 UTC (permalink / raw)
To: Chris Friesen; +Cc: linux-kernel
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'
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-07-03 16:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox