From: "Jan Beulich" <JBeulich@novell.com>
To: Yang Z Zhang <yang.z.zhang@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Weidong Han <weidong.han@intel.com>
Subject: RE: kernel panic when enable x2apic
Date: Fri, 19 Nov 2010 10:17:21 +0000 [thread overview]
Message-ID: <4CE65CC102000078000234EC@vpn.id2.novell.com> (raw)
In-Reply-To: <749B9D3DBF0F054390025D9EAFF47F22301CB045@shsmsx501.ccr.corp.intel.com>
>>> On 18.11.10 at 05:53, "Zhang, Yang Z" <yang.z.zhang@intel.com> 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.
>> Wouldn't it be possible that you simple send the whole log?
Besides the above, I can only repeat this request of mine. I'm
afraid I can't be of much help here without being able to
reproduce the problem and without having much data to work
from.
Since no-one else complained so far - did you do a full rebuild
of Xen after you pulled in the changeset in question?
Jan
next prev parent reply other threads:[~2010-11-19 10:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 8:59 kernel panic when enable x2apic Zhang, Yang Z
2010-11-17 9:41 ` Jan Beulich
2010-11-17 13:16 ` Zhang, Yang Z
2010-11-17 16:23 ` Jan Beulich
2010-11-18 4:53 ` Zhang, Yang Z
2010-11-19 10:17 ` Jan Beulich [this message]
2010-11-19 10:40 ` Sander Eikelenboom
2010-11-19 11:08 ` Jan Beulich
2010-11-30 0:58 ` Zhang, Yang Z
2010-11-30 8:50 ` Weidong Han
2010-11-30 9:23 ` Keir Fraser
2010-11-30 11:40 ` Keir Fraser
2010-12-01 0:42 ` Weidong Han
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CE65CC102000078000234EC@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=weidong.han@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yang.z.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).