All of lore.kernel.org
 help / color / mirror / Atom feed
From: agya naila <agya.naila@gmail.com>
To: Fabian Arrotin <arrfab@centos.org>
Cc: Jan Beulich <JBeulich@suse.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
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	[thread overview]
Message-ID: <CAN-nQwjgTee88x+m0yOdLrehox8=H17CfP_bANpSmPwNh83wUw@mail.gmail.com> (raw)
In-Reply-To: <511413E8.3090407@centos.org>


[-- Attachment #1.1: Type: text/plain, Size: 755 bytes --]

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
>

[-- Attachment #1.2: Type: text/html, Size: 1172 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

  reply	other threads:[~2013-02-08 14:08 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
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 [this message]
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='CAN-nQwjgTee88x+m0yOdLrehox8=H17CfP_bANpSmPwNh83wUw@mail.gmail.com' \
    --to=agya.naila@gmail.com \
    --cc=JBeulich@suse.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.