Bug#311358: marked as done (strange system time behaviour)
Your message dated Sat, 5 Jan 2008 22:16:35 +0100
with message-id <20080105211635.GV17624@stro.at>
and subject line strange system time behaviour
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: presumably kernel
we experience a strange behaviour of the system time which sometimes seems
to be stopped, but a closer inspection by issuing the date command
repeatedly reveals that the time actually is jumping back and ahead by just
a couple of seconds. this happens currently once every couple of days on
three machines (all Fujitsu-Siemens RX-100 Servers) running Debian Sarge
with different kernel versions (2.6.7-1-386 and 2.6.8-1-686). all machines
are updated regularily once a week.
we found some older bug report which is already closed where such a
behaviour was connected to systems which once had been upgraded from stable
to testing, and which might be true for the two 2.6.8-kernels (i'm sorry
that i cannot give more details, but i cannot remember definitely how those
systems had been set up), but the machine running the 2.6.7-kernel was set
up as sarge (testing) from the very start.
with best regards
Peter Walter
______________________________________
Systemadministration ThinPrint GmbH
Alt-Moabit 91 10559 Berlin
Tel. +49 30 39493205
Fax +49 30 39493199
eMail: peter.walter@thinprint.com
--- End Message ---
--- Begin Message ---
- To: 311358-done@bugs.debian.org
- Subject: Re: strange system time behaviour
- From: maximilian attems <max@stro.at>
- Date: Sat, 5 Jan 2008 22:16:35 +0100
- Message-id: <20080105211635.GV17624@stro.at>
Version: 2.6.23-1
timer subsystem got significantly rewritten for no-hz kernels,
and thus it is most likely that this bug no longer applies.
closing
--
maks
--- End Message ---
Reply to: