Re: [Xen-devel] 100% reliable Oops on xen 4.0.1

[Peter Moody <pmoody@xxxxxxxxxx>]

On Tue, Aug 14, 2012 at 9:09 AM, Jan Beulich <JBeulich@xxxxxxxx> wrote:

> From the above as well as based on you indicating that the
> traces are highly variable between instances, I'd suppose
> this is memory corruption of some sort, which can easily be
> hidden by all sorts of factors.
>
> Until you can find a pattern, I don't think there can be done
> much by anyone not having an affected system available for
> debugging.

So I have such a system :).

Are there any pointers or tips you can give me to help me track down
the root cause? I realize that's a broad question, and a perfectly
justifiable answer is "read the memory management chapter of
understanding linux device drivers" but at this point basically any
advice you can give me is appreciated (and will most likely get me
closer to the solution).

Cheers,
peter

> Jan
>



-- 
Peter Moody      Google    1.650.253.7306
Security Engineer  pgp:0xC3410038

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel