[181741] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: REMINDER: LEAP SECOND

daemon@ATHENA.MIT.EDU (Mike Hammett)
Wed Jul 1 14:20:23 2015

X-Original-To: nanog@nanog.org
Date: Wed, 1 Jul 2015 13:19:31 -0500 (CDT)
From: Mike Hammett <nanog@ics-il.net>
To: nanog@nanog.org
In-Reply-To: <20150701181706.GB21302@cmadams.net>
Errors-To: nanog-bounces@nanog.org

The only v6 ones that are sure to have had the problem are based on tilera chips and one of two NTP packages available. *shrugs* 




----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 



Midwest Internet Exchange 
http://www.midwest-ix.com 


----- Original Message -----

From: "Chris Adams" <cma@cmadams.net> 
To: nanog@nanog.org 
Sent: Wednesday, July 1, 2015 1:17:06 PM 
Subject: Re: REMINDER: LEAP SECOND 

Once upon a time, Mike Hammett <nanog@ics-il.net> said: 
> v5 is 2.4, v6 3.3.5 

Don't know why a 3.3.5 kernel would have deadlocked; don't think there 
are any known issues that would cause that, unless there are Mikrotik 
specific patches that caused the problem. 

I believe the bug from the 2008 leap second was present in kernels in 
2.4 up through 2.6.26 (although Red Hat at least patched it in their 
older version long-term support kernels). 

-- 
Chris Adams <cma@cmadams.net> 


home help back first fref pref prev next nref lref last post