Your message dated Wed, 17 Feb 2010 18:55:48 +0100
with message-id <[email protected]>
and subject line Re: Bug#461487: linux-image-2.6-amd64: HZ is set to 250 (for
contextswitches) - please consider using 100Hz as 250Hz affects timekeeping
(with NTPd) badly
has caused the Debian Bug report #461487,
regarding linux-image-2.6-amd64: HZ is set to 250 (for contextswitches) -
please consider using 100Hz as 250Hz affects timekeeping (with NTPd) badly
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 [email protected]
immediately.)
--
461487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461487
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-2.6-amd64
Version: 2.6.22+11
Severity: normal
HZ is set to 250 (for contextswitches) - please consider using 100Hz as 250Hz
affects timekeeping (with NTPd) badly
see thread at:
http://groups.google.com/group/comp.protocols.time.ntp/browse_thread/thread/6c4645ac82c1c013
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.23pps-nodeb.pps-nodeb (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6-amd64 depends on:
ii linux-image-2.6.22-3-amd64 2.6.22-6 Linux 2.6.22 image on AMD64
linux-image-2.6-amd64 recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, Jan 06, 2009 at 04:18:48PM +0100, Folkert van Heusden wrote:
> > > > Package: linux-image-2.6-amd64
> > > > Version: 2.6.22+11
> > > > Severity: normal
> > > >
> > > > HZ is set to 250 (for contextswitches) - please consider using 100Hz as
> > > > 250Hz affects timekeeping (with NTPd) badly see thread at:
> > > > http://groups.google.com/group/comp.protocols.time.ntp/browse_thread/thread/6c4645ac82c1c013
> > >
> > > quite a lot happened since in the timer code,
> > > thanks to tickless kernels, test 2.6.24-rc8 trunk builds
> > > http://wiki.debian.org/DebianKernel
> >
> > Folkert, did you test NTPD with more recent kernels?
>
> Hi,
>
> Unfortunately I don't have the hardware (scope?) and such to verify
> this. I was reporting it as a 'bug' from what I read on the linux-pps
> mailinglist (which talks about the pulse-per-second infrastructure
> patch, which is for connecting an atomic clock or gps with pps
> signal).
I'm closing the bug. The warning on the PPS patch is quite old and since
the timekeeping code is nowadays the standard this is mostly definitely
fixed in the PPS patch meanwhile.
Cheers,
Moritz
--- End Message ---
