From mboxrd@z Thu Jan  1 00:00:00 1970
From: agya naila <agya.naila@gmail.com>
Subject: Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front
 panel NMI crash
Date: Fri, 8 Feb 2013 15:08:08 +0100
Message-ID: <CAN-nQwjgTee88x+m0yOdLrehox8=H17CfP_bANpSmPwNh83wUw@mail.gmail.com>
References: <20130206132802.GU8912@reaktio.net>
	<CAN-nQwhs9Vt+ttDeALYZEgFSQ_UH=08y0zfQ9aRBU4RydF+zTQ@mail.gmail.com>
	<511413E8.3090407@centos.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2233391311851892454=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <511413E8.3090407@centos.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Fabian Arrotin <arrfab@centos.org>
Cc: Jan Beulich <JBeulich@suse.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

--===============2233391311851892454==
Content-Type: multipart/alternative; boundary=047d7bf19890c1396004d53716ee

--047d7bf19890c1396004d53716ee
Content-Type: text/plain; charset=ISO-8859-1

Hello all,

Today Xen finally running on IBM blade server machine, try to add nmi=dom0
and find the Base Board Management Controller on bios configuration and
disabled the 'reboot system on nmi' attribute. This step won't eliminate
the nmi problem since I still found NMI error interrupt on my blade server
log but xen would ignored and keep running. If any other found better
solution would be great.

Agya

On Thu, Feb 7, 2013 at 9:51 PM, Fabian Arrotin <arrfab@centos.org> wrote:

> On 02/06/2013 02:39 PM, agya naila wrote:
> > I configure it by added nmi=ignore to my /boot/grub/grub.cfg
> >
>
> Just to add that I also tried the nmi=ignore parameter for Xen, and it
> stills hard reboot/resets automatically during the kernel dom0 boot
>
> Fabian
>

--047d7bf19890c1396004d53716ee
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello all,<div><br></div><div>Today Xen finally running on IBM blade server=
 machine, try to add nmi=3Ddom0 and find the Base Board Management Controll=
er on bios configuration and disabled the &#39;reboot system on nmi&#39; at=
tribute. This step won&#39;t eliminate the nmi problem since I still found =
NMI error interrupt on my blade server log but xen would ignored and keep r=
unning. If any other found better solution would be great.</div>
<div><br></div><div>Agya<br><br><div class=3D"gmail_quote">On Thu, Feb 7, 2=
013 at 9:51 PM, Fabian Arrotin <span dir=3D"ltr">&lt;<a href=3D"mailto:arrf=
ab@centos.org" target=3D"_blank">arrfab@centos.org</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
<div class=3D"im">On 02/06/2013 02:39 PM, agya naila wrote:<br>
&gt; I configure it by added nmi=3Dignore to my /boot/grub/grub.cfg<br>
&gt;<br>
<br>
</div>Just to add that I also tried the nmi=3Dignore parameter for Xen, and=
 it<br>
stills hard reboot/resets automatically during the kernel dom0 boot<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Fabian<br>
</font></span></blockquote></div><br></div>

--047d7bf19890c1396004d53716ee--


--===============2233391311851892454==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============2233391311851892454==--