mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christian Koch" <linkernel@ckoch.net>
To: <linux-kernel@vger.kernel.org>
Subject: date, time problem on ulrasparc III processors
Date: Mon, 29 Sep 2003 19:02:50 +0200	[thread overview]
Message-ID: <002401c386ab$8447bf50$8501a8c0@munich.secaron.de> (raw)

Hello,

I have a strange problem on Ultrasparc III Cu processor system. There are 2
CPUs in this SUN 280R. I have tried different kernels (2.4.21, 2.4.22)

The problem is, if I request date and time of the system I get different
answers. It seams, that there is a syncing problem between the hardware and
the system clock.

# hwclock --set --date="9/24/03 10:56:00"
# hwclock
Wed Sep 24 10:56:03 2003 -0.232462 seconds
# hwclock
Wed Sep 24 10:56:06 2003 -17180.423522 seconds
# hwclock
Wed Sep 24 10:56:09 2003 -0.637757 seconds

# date
Thu Sep 25 06:05:13 CEST 2003
# date
Thu Sep 25 01:18:53 CEST 2003
# hwclock
Wed Sep 24 10:57:52 2003 -17180.702994 seconds

In the system there are two equal cpu's. cpuinfo shows two different
CpuBogo's.

# cat /proc/cpuinfo
cpu : TI UltraSparc III+ (Cheetah+)
fpu : UltraSparc III+ integrated FPU
promlib : Version 3 Revision 5
prom : 4.5.21
type : sun4u
ncpus probed : 2
ncpus active : 2
Cpu0Bogo : 1599.07
Cpu0ClkTck : 0000000047868c00
Cpu1Bogo : 1.63
Cpu1ClkTck : 0000000047868c00
MMU Type : Cheetah+
State:
CPU0: online
CPU1: online

I think the date, time problem can be a bug in the RTC-module.

Christian


             reply	other threads:[~2003-09-29 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 17:02 Christian Koch [this message]
2003-09-30  6:39 ` David S. Miller

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='002401c386ab$8447bf50$8501a8c0@munich.secaron.de' \
    --to=linkernel@ckoch.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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

all inboxes | Powered by JetHome®