RE: [Xen-devel] RE: kernel panic when enable x2apic

["Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx>]

hi Jan, weidong is looking into this issue. It is interesting is that, he can 
reproduce this issue in an older changeset in his box. So I am not sure whether 
there has another issue in my box. We will let you know ASAP when we get 
result. 

best regards
yang


> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@xxxxxxxxxx]
> Sent: Friday, November 19, 2010 7:09 PM
> To: Sander Eikelenboom
> Cc: Han, Weidong; Zhang, Yang Z; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] RE: kernel panic when enable x2apic
> 
> >>> On 19.11.10 at 11:40, Sander Eikelenboom <linux@xxxxxxxxxxxxxx> wrote:
> > Hello Jan,
> >
> > Friday, November 19, 2010, 11:17:21 AM, you wrote:
> >
> >>>>> On 18.11.10 at 05:53, "Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx>
> wrote:
> >>> From this output, it shows the cpupool_id = 7f034000, I don't know why it
> >>> was 7f034000. I think the first cpupool_id should be 0?Am I right?
> >
> >> Yes, it ought to be zero.
> >
> >>> Also the fail with write mtrr MSR, the value also is very strange:
> >>> ffff83007f0f7670, it totally different with the SDM says.
> >>> (XEN) MTRR: CPU 0: Writing MSR 200 to ffff83007f0f7670 failed
> >
> >> Yes, I had indicated so in an earlier reply.
> >
> >>> So, I am think that maybe the heap is broken?
> >
> >> General memory corruption is more likely. The question is when it
> >> starts.
> >
> > General memory corruption could also be hardware related (bad dimm) ?
> 
> In general, yes, but this wouldn't normally lead to patterns that look
> like valid (albeit misplaced) addresses, I would think.
> 
> Jan


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