RE: [Xen-ia64-devel] RE: Updating to xen-unstable... resultsinXenfreeze

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

Ignore that last message.  Pilot error. (I was in the wrong
directory... love that hg error message though :-) 

> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Magenheimer, Dan (HP Labs Fort Collins)
> Sent: Tuesday, August 02, 2005 8:44 AM
> To: Yang, Fred
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-ia64-devel] RE: Updating to xen-unstable... 
> resultsinXenfreeze
> 
> I seem to be having some hg problems.  I successfully
> pulled the -Intel tree but hg update seems to get stuck.
> I finally had to interrupt it after 10 minutes because
> I am working at home and need to leave for work.
> I'll try again later, but anybody else seen this problem
> and know how to fix it?
> 
> Dan
> 
> ====
> 
> [djm@kirby xen]$ hg pull
> http://xenbits.xensource.com/ext/xen-ia64-unstable-Intel.hg
> pulling from 
> http://xenbits.xensource.com/ext/xen-ia64-unstable-Intel.hg
> searching for changes
> adding changesets
> adding manifests
> adding file revisions
> modified 300 files, added 15 changesets and 378 new revisions
> (run 'hg update' to get a working copy)
> [djm@kirby xen]$ hg update
> [... freezes here for >10 minutes!]
> 
> ps -l shows.
> 
> 0 D djm      24318 24166 32  85   0    - 13748 io_sch 08:29 pts/2
> 00:02:43 /usr/local/bin/python /usr/local/bin/hg update
> 
> and top shows it using between 5% and 16% of cpu. 
> 
> > -----Original Message-----
> > From: Yang, Fred [mailto:fred.yang@xxxxxxxxx] 
> > Sent: Tuesday, August 02, 2005 7:04 AM
> > To: Magenheimer, Dan (HP Labs Fort Collins); 
> > xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: RE: [Xen-ia64-devel] RE: Updating to xen-unstable... 
> > results inXenfreeze
> > 
> > Magenheimer, Dan (HP Labs Fort Collins) wrote:
> > > xen-ia64-unstable tip now is merged with xen-unstable.
> > > I would appreciate
> > Dan,
> > Can you pull xen-unstable-ia64-Intel.hg into 
> Xen-unstale-ia64.hg?  We
> > have also push VT-I stuff based on Rev#5946 last night.  They 
> > are mainly
> > VT-I specific and does interfere with Xenlinux support.
> > We do modified files: 
> > xen/arch/ia64/patch/linux-2.6.11/irq_ia64.c  as a
> > separate patch on Rev#5952.
> > Thanks,
> > -Fred
> > 
> > > some testing as soon as possible, as I'd like to ask
> > > Keir to pull before the end of the day, before more
> > > changes are made to xen-unstable.
> > > 
> > > Note that a recent xenlinux (cset 18, 4 days ago) is
> > > required.
> > > 
> > > Thanks,
> > > Dan
> > > 
> > >> -----Original Message-----
> > >> From: Magenheimer, Dan (HP Labs Fort Collins)
> > >> Sent: Monday, August 01, 2005 12:07 PM
> > >> To: Chapman, Matthew (HP Labs Fort Collins)
> > >> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > >> Subject: RE: [Xen-ia64-devel] RE: Updating to xen-unstable...
> > >> results in Xenfreeze 
> > >> 
> > >> I found and checked in a workaround.  Tip seems to
> > >> work now.
> > >> 
> > >> I want to add Arun's patch to allow compiling on gcc3.4
> > >> and merge up to the xen-unstable changes over the
> > >> weekend, then would like to get some final testing
> > >> (including CONFIG_VTI) and ask Keir to pull in the
> > >> latest xen-ia64-unstable into xen-unstable.
> > >> 
> > >> Dan
> > >> 
> > >>> -----Original Message-----
> > >>> From: Chapman, Matthew (HP Labs Fort Collins)
> > >>> Sent: Friday, July 29, 2005 6:31 PM
> > >>> To: Magenheimer, Dan (HP Labs Fort Collins)
> > >>> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > >>> Subject: Re: [Xen-ia64-devel] RE: Updating to xen-unstable...
> > >>> results in Xenfreeze 
> > >>> 
> > >>> Dan,
> > >>> 
> > >>> 5730 works okay for me.
> > >>> 
> > >>> The problem seems to be cset 5812...  which adds a call to
> > >>> do_softirq in scrub_heap_pages.
> > >>> 
> > >>> Matt
> > >>> 
> > >>> 
> > >>> On Fri, Jul 29, 2005 at 04:53:32PM -0700, Magenheimer, Dan
> > >>> (HP Labs Fort Collins) wrote:
> > >>>> It appears the problem arises on xen-unstable somewhere between
> > >>>> cset 5705 and 5730. 
> > >>>> 
> > >>>>> -----Original Message-----
> > >>>>> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > >>>>> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf
> > >>>>> Of Magenheimer, Dan (HP Labs Fort Collins)
> > >>>>> Sent: Friday, July 29, 2005 5:44 PM
> > >>>>> To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > >>>>> Subject: [Xen-ia64-devel] RE: Updating to 
> > xen-unstable... results
> > >>>>> in Xenfreeze 
> > >>>>> 
> > >>>>> 
> > >>>>> 
> > >>>>>> -----Original Message-----
> > >>>>>> From: Magenheimer, Dan (HP Labs Fort Collins)
> > >>>>>> Sent: Friday, July 29, 2005 4:29 PM
> > >>>>>> To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > >>>>>> Subject: Updating to xen-unstable... results in Xen freeze
> > >>>>>> 
> > >>>>>> I just updated xen-ia64-unstable to merge in the
> > >>>>>> xen-unstable tip.  Both xen-unstable** and xen-ia64-unstable
> > >>>>>> worked fine separately, but when combined, Xen freezes
> > >>>>>> in scrub_heap_pages while calling do_softirq.  Some
> > >>>>>> subtle interaction between recent changesets in the 
> two trees,
> > >>>>>> maybe? 
> > >>>>>> 
> > >>>>>> So, tip of xen-ia64-unstable.hg is now broken.  Anybody
> > >>>>>> (with a hardware debugger) want to try to reproduce this
> > >>>>>> and look into it further?
> > >>>>>> 
> > >>>>>> Dan
> > >>>>>> 
> > >>>>>> Note: xen-unstable required some minor syntactic cleanup
> > >>>>>> to handle an new extra unused argument to 
> alloc_domheap_pages.
> > >>>>> 
> > >>>>> I spent another hour trying to isolate this without much luck
> > >>>>> and need to leave now.  It appears that my successful run
> > >>>>> of xen-unstable tip was mistaken though (must have tried
> > >>>>> the wrong bits :-(... so it could be any change in 
> xen-unstable
> > >>>>> in the last two weeks that is causing the problem.
> > >>>>> 
> > >>>>> Binary version searching with hg seems to be untrustworthy...
> > >>>>> sometimes I am not getting the version I thought I 
> was getting.
> > >>>>> 
> > >>>>> Dan
> > >>>>> 
> > >>>>> _______________________________________________
> > >>>>> Xen-ia64-devel mailing list
> > >>>>> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > >>>>> http://lists.xensource.com/xen-ia64-devel
> > >>>>> 
> > >>>> 
> > >>>> _______________________________________________
> > >>>> Xen-ia64-devel mailing list
> > >>>> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > >>>> http://lists.xensource.com/xen-ia64-devel
> > >>> 
> > >> 
> > > 
> > > _______________________________________________
> > > Xen-ia64-devel mailing list
> > > Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-ia64-devel
> > 
> > 
> 
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
> 

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel