From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash Date: Wed, 6 Feb 2013 15:28:02 +0200 Message-ID: <20130206132802.GU8912@reaktio.net> References: <20130205163021.GR8912@reaktio.net> <20130205200847.GS8912@reaktio.net> <51121B5002000078000BC573@nat28.tlf.novell.com> <20130206112910.GT8912@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: agya naila Cc: arrfab@centos.org, Jan Beulich , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Wed, Feb 06, 2013 at 12:48:50PM +0100, agya naila wrote: > Thank you Pasi to forward this email for me too, it seem not only me > facing this problem. I found this guy also found similar problem, its = in > french but we can translate it easily using > google [1]http://debian.2.n7.nabble.com/Probleme-XEN-4-0-1-et-SQUEEZE-= 64bits-reboot-td1230690.html > I found parameter nmi=3Dignore | dom0 | fatal > nmi=3Dreaction : Enables you to specify how the hypervisor reacts to a= non - > maskable interrupt > (NMI) resulting from a parity or I/O error. Possible values for reacti= on > are fatal (the hypervisor > prints a diagnostic message and then hangs), dom0 (send a message to > domain0 for logging > purposes but continue), and ignore (ignore the error). If you do not > specify this option, Xen > uses the default value dom0 internally. > But its still doesn't work on my machine. > So you tried adding "nmi=3Dignore" for xen.gz in grub settings and it didn'= t help? = Did you try the other possible values? = -- Pasi > Agya > On Wed, Feb 6, 2013 at 12:29 PM, Pasi K=E4rkk=E4inen <[2]pasik@iki.fi>= wrote: > = > On Wed, Feb 06, 2013 at 07:58:56AM +0000, Jan Beulich wrote: > > >>> On 05.02.13 at 21:08, Pasi K=E4rkk=E4inen<[3]pasik@iki.fi> wro= te: > > > Arrfab (CC'd) is actually seeing a similar problem on IBM HS20 b= lade > with > > > Xen 4.2.1 > > > with Linux 3.4.28 dom0 kernel. > > > > > > Does this ring anyone's bells? > > > > > > > > > serial console log of the crash > > > > Which doesn't even include the message in the subject afaics, so I > > don't even know what you're talking about. And the other, earlier > > report has no useful information either. > > > > From an abstract perspective, a front panel NMI to me would mean > > someone pressed an NMI button on the system's front panel. You > > don't think Xen can do anything about this, do you? And even if > > the NMI has another origin, it's still a hardware generated event > > that Xen has no control over. > > > = > Arrfab said Xen crashes and reboots in the middle of the boot proces= s, > and the blade chassis management logs the NMI error. The user is not > pressing (NMI) buttons. > = > The serial log included is everything he gets. No error visible in t= he > serial log, > only a crash/reboot without any errors.. No idea what could be causi= ng > that.. > = > The same Dom0 kernel (pvops 3.4.28) boots OK on baremetal without Xe= n. > = > Do you have any Xen and/or dom0 kernel options to use to do further > analysis? > -- Pasi > = > References > = > Visible links > 1. http://debian.2.n7.nabble.com/Probleme-XEN-4-0-1-et-SQUEEZE-64bits-= reboot-td1230690.html > 2. mailto:pasik@iki.fi > 3. mailto:pasik@iki.fi