Your message dated Sat, 26 Jan 2002 14:48:48 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#51376: hwclock goes berserk!
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 27 Nov 1999 10:42:27 +0000
Received: (qmail 444 invoked from network); 27 Nov 1999 10:42:26 -0000
Received: from mta3.snfc21.pbi.net (206.13.28.141)
by master.debian.org with SMTP; 27 Nov 1999 10:42:26 -0000
Received: from kanji.com ([63.193.151.193])
by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8)
with ESMTP id <[EMAIL PROTECTED]> for [EMAIL PROTECTED];
Sat, 27 Nov 1999 02:42:21 -0800 (PST)
Date: Sat, 27 Nov 1999 10:42:22 +0000
From: Michael Babcock <[EMAIL PROTECTED]>
Subject: hwclock goes berserk!
Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Message-id: <[EMAIL PROTECTED]>
MIME-version: 1.0
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.10 i586)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
Package: util-linux
Version: 2.10-4
hwclock just returns crazy, random looking values on one of our
machines. Is this a hardware or software problem? Consider:
beavis:~# date
Sat Nov 27 02:37:21 PST 1999
beavis:~# hwclock --utc --systohc
beavis:~# hwclock --utc; date
Tue Dec 21 16:03:00 1999 -0.009666 seconds
Sat Nov 27 02:37:29 PST 1999
beavis:~# hwclock --utc; date
Sat Dec 2 02:13:10 2000 -0.306338 seconds
Sat Nov 27 02:37:33 PST 1999
beavis:~# while true; do hwclock --utc; done
Sat Jan 2 16:26:00 2010 -0.533297 seconds
Mon Nov 21 02:13:50 2011 -0.985445 seconds
Sun Nov 24 16:25:02 2019 -0.985337 seconds
Wed Jan 3 02:15:54 2018 -0.985479 seconds
Tue Nov 5 02:04:04 2019 -0.985354 seconds
Fri Nov 4 02:15:04 2011 -0.985470 seconds
Sun Oct 7 03:02:17 1990 -0.985305 seconds
Wed Sep 30 03:35:58 1998 -0.985446 seconds
Tue Dec 4 02:34:58 2018 -0.985375 seconds
Sun Nov 7 02:00:00 1999 -0.985405 seconds
Mon Nov 1 02:00:01 1999 -0.985396 seconds
Wed Dec 20 02:38:02 2000 -0.985411 seconds
Wed Sep 29 17:00:01 1999 -0.985444 seconds
Sun Nov 4 16:08:04 2001 -0.984917 seconds
---------------------------------------
Received: (at 51376-done) by bugs.debian.org; 26 Jan 2002 21:48:48 +0000
>From [EMAIL PROTECTED] Sat Jan 26 15:48:48 2002
Return-path: <[EMAIL PROTECTED]>
Received: from jones.cwx.net (mix.fc.hp.com) [216.17.176.67]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16Uagq-0002BY-00; Sat, 26 Jan 2002 15:48:48 -0600
Received: from security.hp.com (localhost [127.0.0.1])
by mix.fc.hp.com (Postfix) with ESMTP
id 306A31FA0AB; Sat, 26 Jan 2002 14:48:48 -0700 (MST)
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#51376: hwclock goes berserk!
Date: Sat, 26 Jan 2002 14:48:48 -0700
From: LaMont Jones <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
This certainly appears to either (1) have been fixed sometime in the past
2+ years, or (2) be a hardware problem.
Closing the bug.
lamont
