From: Bill Burns <bburns@redhat.com>
To: "Carb, Brian A" <Brian.Carb@unisys.com>
Cc: xen-devel@lists.xensource.com, Ian Pratt <Ian.Pratt@eu.citrix.com>
Subject: Re: Test results on Unisys ES7000 64x 256gb usingunstablec/s 16693 on 3.2.0 Release Candidate
Date: Mon, 28 Jan 2008 16:12:13 -0500 [thread overview]
Message-ID: <479E452D.80501@redhat.com> (raw)
In-Reply-To: <089B0D75973E1241B941D0A9854F23FC0AA478CA@USEA-EXCH2.na.uis.unisys.com>
Carb, Brian A wrote:
> My environment also produces a panic (unstable cs 16852 on x64
> SLES10sp1) when I boot with 64cpu and 256gb and dom0_mem not specified:
> traps.c:414:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0
> [ec=0000]
>
> with dom0_mem=4096, system boots fine.
>
>
> brian carb
> unisys corporation - malvern, pa
>
>
<snip>
This may be of use. When it fails, the dom0 reports:
Xen reported: 6799.922 MHz processor.
...
Calibrating delay using timer specific routine.. 17069.04 BogoMIPS (lpj=34138093)
When it works, dom0 reports the correct numbers:
Xen reported: 3399.952 MHz processor.
...
Calibrating delay using timer specific routine.. 8505.35 BogoMIPS (lpj=17010701)
Strange that the numbers are basically 2x the correct values.
Also have had it fail at a lower memory (96GB) with all
64 CPUs. When I was running a HV built for only 32 it worked
until I passed 112GB to dom0.
Bill
next prev parent reply other threads:[~2008-01-28 21:12 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 [this message]
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
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=479E452D.80501@redhat.com \
--to=bburns@redhat.com \
--cc=Brian.Carb@unisys.com \
--cc=Ian.Pratt@eu.citrix.com \
--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.