From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: CMCI exceptions happened and MCE entry state transition made Xen crashed. Date: Mon, 13 Dec 2010 09:53:19 +0000 Message-ID: References: <125662f.57a2.12cd968924a.Coremail.flyfan05@163.com> Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <125662f.57a2.12cd968924a.Coremail.flyfan05@163.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: flyfan05 , xen-devel List-Id: xen-devel@lists.xenproject.org Sounds like your system probably has a bad memory DIMM. If the MCE logic is causign problems you can turn it off with mce=3D0 Xen boot parameter. This will cause all these correctable errors to be ignored rather than logged; and uncorrectable errors will cause immediate hypervisor stop-and-crash rather than have dom0 attempt to fix up. K. On 12/12/2010 07:08, "flyfan05" wrote: > Hi all,=20 > Three days ago, the server reported lots of CMCI exceptions and Xen 3.4.2 > printed hundreds of "CMCI: send CMCI to DOM0 through virq" messages to th= e > console . From the console output, Then I can see that Dom0 try to read = the > MSR_CAP regs by #GP trap in order to log the MCA error. >=20 > I am not sure why so many CMCI happened , maybe there were some thing wro= ng > with the hardware. But unfortunately the server crashed at the end. The = Xen > BUG ON at > mctelem_append_processing() > -> MCTE_TRANSITION_STATE(tep, COMMITTED, PROCESSING) > -> BUG_ON(MCTE_STATE(tep) !=3D (MCTE_F_STATE_##old)); > The output of the console is like this: > (XEN) Xen bug on at mctelem.c : Line 437 >=20 > Why the state of the entry is not correct ? Some one change that unexpect= ed? > If any body even resolve this kind problems, Pls do me a favor. >=20 > --Van >=20 >=20 > =CD=F8=D2=D7163/126=D3=CA=CF=E4=B0=D9=B7=D6=B0=D9=BC=E6=C8=DDiphone ipad=D3=CA=BC=FE=CA=D5=B7=A2 > >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel