[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#499297: marked as done (linux-image-2.6-amd64: excessive time drifts (10sec/min) after kernel upgrade)

Your message dated Wed, 2 Sep 2009 19:34:43 +0200
with message-id <20090902173443.GA15524@inutil.org>
and subject line Re: Bug still present in latest versions
has caused the Debian Bug report #499297,
regarding linux-image-2.6-amd64: excessive time drifts (10sec/min) after kernel upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
499297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499297
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6-amd64
Version: 2.6.26+16
Severity: critical
Justification: breaks unrelated software


After upgrading two machines to the latest 2.6.26 kernel from sid, they exhibit extreme time drift (to the order of 10 seconds in a minute), resulting in clocks that are hours out-of-sync after only a day of uptime!
The drift is so bad that ntpd gives up trying to sync the clocks and rejects all sources (it is the same basically with or without ntpd).

The affected systems ran perfectly with the latest 2.6.25 (debian) kernel and the behaviour started only after rebooting with 2.6.26.
These are not production systems, however database activity is severely affected, and so are many other programs that depend on time like VPN software which refuses to establish connections.

I tried manually installing an older 2.6.25 kernel on one of them and the problem went away, so it is definitely something in the latest kernels (didn't try previous 2.6.26 versions).

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6-amd64 depends on:
ii  linux-image-2.6.26-1-amd64    2.6.26-5   Linux 2.6.26 image on AMD64

linux-image-2.6-amd64 recommends no packages.

linux-image-2.6-amd64 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 2.6.29-1

On Tue, Jul 28, 2009 at 08:26:00PM +0300, Mihnea-Costin Grigore wrote:
> 
> On Tue, 28 Jul 2009 01:21:57 +0200, Moritz Muehlenhoff <jmm@inutil.org>
> wrote:
> > Does this issue still appear with the final Lenny kernel?
> 
> Yes, I think so. I only have one machine to test this on at the moment, the
> laptop has since been upgraded to 2.6.29-1 from sid which does *not* have
> this problem.
> The Athlon 5200 though is running squeeze, as far as I can see the kernel
> versions are the same (2.6.26+17+lenny1) and the problem is still there, so
> I'd wager lenny has the same problem...

I'm marking 2.6.29 as the fixed version for unstable. If anyone manages to
isolate specific commits, which fixed this behaviour we can backport them
to Lenny.

Cheers,
        Moritz

--- End Message ---
Reply to: