From: Bill Burns <bburns@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <Ian.Pratt@eu.citrix.com>,
xen-devel@lists.xensource.com, "Carb,
Brian A" <Brian.Carb@unisys.com>
Subject: Re: Large system boot problems
Date: Fri, 08 Feb 2008 10:10:26 -0500 [thread overview]
Message-ID: <47AC70E2.6090900@redhat.com> (raw)
In-Reply-To: <C3D211E7.1C1FC%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
> On 8/2/08 13:49, "Bill Burns" <bburns@redhat.com> wrote:
>
>> Looking for ideas or suggestions on how to solve this issue.
>> Ideally we'd be able to prevent the bogus calculation in the
>> first place.
>
> Could the bad value coming from calibration in init_pit_and_calibrate_tsc(),
> or perhaps it is somehow caused perhaps by not-frequent-enough softirq
> handling on CPU0 as it brings up all the secondary CPUs (and hence it is not
> going through local_time_calibration() during that period)?
>
The message from early_time_init (caller of
iinit_pit_and_calibrate_tsc, indicates that the
initial detection is ok:
(pmtimer case) (XEN) Detected 3400.114 MHz processor.
((pit case) (XEN) Detected 3400.165 MHz processor.
So I think it's the latter. The init of a large system
is staving off the soft irq so that the next calc fails.
Bill
(XEN) Detected 3400.114 MHz processor.
> -- Keir
>
>
next prev parent reply other threads:[~2008-02-08 15:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 2:15 Test results on Unisys ES7000 64x 256gb using unstable c/s 16693 on 3.2.0 Release Candidate Carb, Brian A
2008-01-15 13:50 ` Bill Burns
2008-01-15 14:44 ` Keir Fraser
2008-01-15 16:15 ` Bill Burns
2008-01-15 16:29 ` Keir Fraser
2008-01-16 15:45 ` Bill Burns
2008-01-17 14:10 ` Test results on Unisys ES7000 64x 256gb using unstablec/s " Ian Pratt
2008-01-18 13:03 ` Bill Burns
2008-01-24 17:23 ` Bill Burns
2008-01-25 13:06 ` Bill Burns
2008-01-28 14:02 ` Bill Burns
2008-01-28 14:08 ` Keir Fraser
2008-01-28 20:38 ` Test results on Unisys ES7000 64x 256gb usingunstablec/s " Carb, Brian A
2008-01-28 21:12 ` Bill Burns
2008-01-29 8:44 ` Test results on Unisys ES7000 64x 256gbusingunstablec/s " Jan Beulich
2008-01-30 16:20 ` Test results on Unisys ES7000 64x 256gb using unstablec/s " Bill Burns
2008-01-30 16:45 ` Keir Fraser
2008-01-31 18:12 ` Bill Burns
2008-02-01 8:36 ` Keir Fraser
2008-02-01 12:40 ` Bill Burns
2008-02-01 20:10 ` Bill Burns
2008-02-08 13:49 ` Large system boot problems Bill Burns
2008-02-08 14:04 ` Keir Fraser
2008-02-08 15:10 ` Bill Burns [this message]
2008-02-08 15:14 ` Keir Fraser
2008-02-08 15:22 ` Bill Burns
2008-02-08 15:45 ` Keir Fraser
2008-02-12 16:34 ` Bill Burns
2008-02-12 16:54 ` Keir Fraser
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=47AC70E2.6090900@redhat.com \
--to=bburns@redhat.com \
--cc=Brian.Carb@unisys.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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.