public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Ralf Weidemann <weidemann@fh-dortmund•de>
To: linuxppc-dev@lists•linuxppc.org
Subject: 2.4.16-ben0: clock broken ?
Date: Wed, 28 Nov 2001 16:59:35 +0100	[thread overview]
Message-ID: <3C0509E7.938BB01D@fh-dortmund.de> (raw)


Hi all,

I get a clock shift of about a month in the latest 2.4.16-ben0.
Something broken ?

Ralf


[ralfw@tibook ralfw]$ uname -a
Linux tibook.sw2.fb4.fh 2.4.15-ben0 #1 Sun Nov 25 12:12:56 CET 2001 ppc unknown
[ralfw@tibook ralfw]$ date
Wed Nov 28 16:34:46 CET 2001
[ralfw@tibook ralfw]$ hwclock --show
Wed 28 Nov 2001 04:34:50 PM CET  -0.790044 seconds
[ralfw@tibook ralfw]$ hwclock -v
hwclock 2.4c/util-linux-2.11f


[ralfw@tibook ralfw]$ uname -a
Linux tibook.sw2.fb4.fh 2.4.16-ben0 #3 Wed Nov 28 16:20:49 CET 2001 ppc unknown
[ralfw@tibook ralfw]$ date
Fri Dec 28 16:39:25 CET 2001
[ralfw@tibook ralfw]$ hwclock --show
Fri 28 Dec 2001 04:39:36 PM CET  -0.827878 seconds
[ralfw@tibook ralfw]$ hwclock -v
hwclock 2.4c/util-linux-2.11f

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-11-28 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28 15:59 Ralf Weidemann [this message]
2001-12-28 16:08 ` 2.4.16-ben0: clock broken ? Dan Malek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C0509E7.938BB01D@fh-dortmund.de \
    --to=weidemann@fh-dortmund$(echo .)de \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox