From: Richard Henderson <rth@twiddle.net>
To: Michael Cree <cree@waikato.ac.nz>
Cc: linux-kernel@vger.kernel.org, ink@jurassic.park.msu.ru,
mattst88@gmail.com, linux-alpha@vger.kernel.org
Subject: Re: [RFC PATCH 00/10] Alpha support for QEMU
Date: Thu, 18 Jul 2013 06:38:14 -0700 [thread overview]
Message-ID: <51E7EFC6.6070003@twiddle.net> (raw)
In-Reply-To: <20130718011435.GA20007@stolen.phys.waikato.ac.nz>
On 07/17/2013 06:14 PM, Michael Cree wrote:
> Tested the patch series applied against 3.10.1 on a 3-CPU ES45. System came
> up fine but I noticed date was wrong and had been reset back to the start
> of the epoch (Jan 1 1970). Appears it is not reading hardware clock
> correctly on boot.
Please scan the dmesg for the "Using epoch 2000 for rtc year 13" line,
and compare vs a similar message on the previous kernel.
> I manually set the clock to the correct time but noticed it is running slow,
> indeed in a period of 60s the system clock incremented by 21s (+/-1s) so
> would appear clock is running slow by a factor given by the number of CPUs.
That's curious. I wonder if somehow I botched the smp changes, and I'm
not getting the timer interrupt either (1) enabled or (2) registered on
the secondary cpus...
Perhaps /proc/interrupts will confirm or deny this?
r~
next prev parent reply other threads:[~2013-07-18 13:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 17:34 [RFC PATCH 00/10] Alpha support for QEMU Richard Henderson
2013-07-16 17:34 ` [RFC PATCH 01/10] alpha: Don't if-out dp264_device_interrupt Richard Henderson
2013-07-16 17:34 ` [RFC PATCH 02/10] alpha: Notice if we're being run under QEMU Richard Henderson
2013-07-16 17:34 ` [RFC PATCH 03/10] alpha: Force the user-visible HZ to a constant 1024 Richard Henderson
2013-07-16 17:34 ` [RFC PATCH 04/10] alpha: Allow HZ to be configured Richard Henderson
2013-07-16 17:34 ` [RFC PATCH 05/10] alpha: Primitive support for CPU power down Richard Henderson
2013-07-17 5:17 ` Matt Turner
2013-07-17 13:16 ` Richard Henderson
2013-07-16 17:34 ` [RFC PATCH 06/10] alpha: Reorganize rtc handling Richard Henderson
2013-07-16 17:34 ` [RFC PATCH 07/10] alpha: Add an rtc driver for the qemu wallclock PALcall Richard Henderson
2013-07-16 17:34 ` [RFC PATCH 08/10] alpha: Always enable the rpcc clocksource for single processor Richard Henderson
2013-07-16 17:34 ` [RFC PATCH 09/10] alpha: Switch to GENERIC_CLOCKEVENTS Richard Henderson
2013-07-16 17:34 ` [RFC PATCH 10/10] alpha: Use qemu+cserve provided high-res clock and alarm Richard Henderson
2013-07-18 1:14 ` [RFC PATCH 00/10] Alpha support for QEMU Michael Cree
2013-07-18 13:38 ` Richard Henderson [this message]
2013-07-18 21:28 ` Michael Cree
2013-07-18 22:04 ` Richard Henderson
2013-07-19 10:03 ` Michael Cree
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=51E7EFC6.6070003@twiddle.net \
--to=rth@twiddle.net \
--cc=cree@waikato.ac.nz \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.