Re: [XenPPC] [PATCH/RFC] Schedule idle domain on secondary processors

[Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>]

> > Most common cause of this is hanging the U3/U4.  Do you have a  
> > hardware
> > debugger to see where this happens?
> It's been my experience that RISCWatch isn't very helpful in these
> situations (e.g. can't stop the processor). When the northbridge goes,
> JTAG becomes unhappy.
Works fine for me, don't know what the difference is -- different
debugger?  The CPU JTAG chain is not connected to the U4 in any
way, fwiw.

What happens is, the API (EI, whatever -- the CPU bus) becomes
unusable after the bad I/O to U4; the CPU waits forever for the
bad load/store to finish.


Segher


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