From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Jan Beulich <JBeulich@suse.com>
Cc: arrfab@centos.org, agya naila <agya.naila@gmail.com>,
xen-devel@lists.xen.org
Subject: Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash
Date: Wed, 6 Feb 2013 13:29:10 +0200 [thread overview]
Message-ID: <20130206112910.GT8912@reaktio.net> (raw)
In-Reply-To: <51121B5002000078000BC573@nat28.tlf.novell.com>
On Wed, Feb 06, 2013 at 07:58:56AM +0000, Jan Beulich wrote:
> >>> On 05.02.13 at 21:08, Pasi Kärkkäinen<pasik@iki.fi> wrote:
> > Arrfab (CC'd) is actually seeing a similar problem on IBM HS20 blade 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 process,
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 the serial log,
only a crash/reboot without any errors.. No idea what could be causing that..
The same Dom0 kernel (pvops 3.4.28) boots OK on baremetal without Xen.
Do you have any Xen and/or dom0 kernel options to use to do further analysis?
-- Pasi
next prev parent reply other threads:[~2013-02-06 11:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 15:49 XEN 4.1 error Critical Interrupt - Front panel NMI agya naila
2013-02-05 16:30 ` Pasi Kärkkäinen
2013-02-05 20:00 ` agya naila
2013-02-05 20:08 ` IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash Pasi Kärkkäinen
2013-02-06 7:58 ` Jan Beulich
2013-02-06 11:29 ` Pasi Kärkkäinen [this message]
2013-02-06 11:45 ` Jan Beulich
2013-02-06 11:48 ` agya naila
2013-02-06 12:01 ` agya naila
2013-02-06 13:28 ` Pasi Kärkkäinen
2013-02-06 13:39 ` agya naila
2013-02-07 20:51 ` Fabian Arrotin
2013-02-08 14:08 ` agya naila
2013-02-08 14:13 ` Pasi Kärkkäinen
2013-09-08 14:35 Trenta sis
2013-09-08 14:41 ` Trenta sis
2013-09-09 19:15 ` Konrad Rzeszutek Wilk
2013-09-12 12:47 ` Trenta sis
2013-09-23 14:02 ` Konrad Rzeszutek Wilk
2013-09-29 10:47 ` Trenta sis
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=20130206112910.GT8912@reaktio.net \
--to=pasik@iki.fi \
--cc=JBeulich@suse.com \
--cc=agya.naila@gmail.com \
--cc=arrfab@centos.org \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.