From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Burns Subject: Re: Test results on Unisys ES7000 64x 256gb using unstable c/s 16693 on 3.2.0 Release Candidate Date: Wed, 16 Jan 2008 10:45:21 -0500 Message-ID: <478E2691.6060307@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com, "Carb, Brian A" List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > > > On 15/1/08 16:15, "Bill Burns" wrote: > >>> Have you tried 3.2.0 release candidates? >>> >>> I doubt any other developers are going to run into this as we're not >>> overwhelmed with 128GB+ systems. >>> >>> -- Keir >>> >>> >> No, I have not tried on 3.2.0. Will see if I can at some >> point... > > Also, do you have any more info to share on what actually goes wrong when > dom0 has 'too much' memory? > The dom0 kernel spits out messages like the following starting around the init of cpu1 time, and periodically thereafter. Timer ISR/0: Time went backwards: delta=-50206266948 delta_cpu=13733052 shadow=8186343367 off=13649733458 processed=72042343367 cpu_processed=21822343367 Eventually just hanging (or making such slow progress to be effectively hung). Bill > Thanks, > Keir > >