[181751] in North American Network Operators' Group
Re: REMINDER: LEAP SECOND
daemon@ATHENA.MIT.EDU (Mike Hammett)
Wed Jul 1 15:42:16 2015
X-Original-To: nanog@nanog.org
Date: Wed, 1 Jul 2015 14:38:59 -0500 (CDT)
From: Mike Hammett <nanog@ics-il.net>
To: Nanog <nanog@nanog.org>
In-Reply-To: <CAGFn2k0h_NHHa9K=W55_92j4NgAmriJdKNQusz8V_brNqqgnyQ@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org
http://forum.mikrotik.com/viewtopic.php?f=2&t=98138#p488731
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "Rubens Kuhl" <rubensk@gmail.com>
To: "Nanog" <nanog@nanog.org>
Sent: Wednesday, July 1, 2015 1:20:30 PM
Subject: Re: REMINDER: LEAP SECOND
On Wed, Jul 1, 2015 at 3:17 PM, Chris Adams <cma@cmadams.net> wrote:
> 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).
>
3.3 was listed as buggy in this regard as well.
Rubens
