On Wed, Jul 1, 2015 at 3:17 PM, Chris Adams <c...@cmadams.net> wrote:
> Once upon a time, Mike Hammett <na...@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
