From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Burns 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 Message-ID: <479E452D.80501@redhat.com> References: <479DE086.9020206@redhat.com> <089B0D75973E1241B941D0A9854F23FC0AA478CA@USEA-EXCH2.na.uis.unisys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <089B0D75973E1241B941D0A9854F23FC0AA478CA@USEA-EXCH2.na.uis.unisys.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Carb, Brian A" Cc: xen-devel@lists.xensource.com, Ian Pratt List-Id: xen-devel@lists.xenproject.org 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 > > 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