All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trenta sis <trenta.sis@gmail.com>
To: xen-devel@lists.xen.org
Cc: arrfab@centos.org, JBeulich@suse.com, agya.naila@gmail.com
Subject: Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash
Date: Sun, 8 Sep 2013 16:35:29 +0200	[thread overview]
Message-ID: <CANTbh_-0bJ_0a=tDvm06Y_QhEHpYhdB6Z0UghTCRaOY5hq5Duw@mail.gmail.com> (raw)


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

Hello,

I have the same error, server is auto rebooted during every boot with
kernel XEN, HS20 with Debian Wheezy and XEN hang on and AMM managment show
same errors described in previous mails. With Debian wheezy wit non-xen
kernel boots correcte, it seems that problems is with xen kernel
Same Server HS20 with Debian Lenny+ XEN 3.2 or Debian Squeeze+XEN
4.0 working perfect

Upgraded to Debian testing and unstable with same results XEN 4.1 and 4.2.

If you need more information, you can ask.
How can be solved this bug?

Thanks






On Fri, Feb 08, 2013 at 03:08:08PM +0100, agya naila wrote:

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.

Thanks for the 'workaround' info.

We still should find out what exactly generates/causes that NMI with Xen..

-- Pasi

Agya

On Thu, Feb 7, 2013 at 9:51 PM, Fabian Arrotin <[1]arr...@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

References

Visible links 1. mailto:arr...@centos.org

[-- Attachment #1.2: Type: text/html, Size: 2033 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-09-08 14:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-08 14:35 Trenta sis [this message]
2013-09-08 14:41 ` IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash 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
2013-09-30 14:13           ` Is: 0xCF8 on extended config space instead of MCONF? Was:Re: " Konrad Rzeszutek Wilk
2013-09-30 15:40             ` Jan Beulich
2013-10-04 16:31             ` Trenta sis
2013-10-04 16:55               ` Konrad Rzeszutek Wilk
2014-09-05 11:58             ` Trenta sis
2014-09-05 14:30               ` Is: 0xCF8 on extended config space instead of MCONF? Jan Beulich
2014-09-08 12:53                 ` Trenta sis
2014-09-08 13:28                   ` Jan Beulich
2014-09-09  7:11                     ` Trenta sis
2014-09-09  8:53                       ` Ian Campbell
2014-09-09 14:00                         ` Trenta sis
2014-09-09 14:39                           ` Konrad Rzeszutek Wilk
2014-09-09 14:39                           ` Ian Campbell
2014-09-09 14:46                             ` Trenta sis
2014-09-09  9:15                       ` Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
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: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
2013-02-08 14:13                   ` Pasi Kärkkäinen

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='CANTbh_-0bJ_0a=tDvm06Y_QhEHpYhdB6Z0UghTCRaOY5hq5Duw@mail.gmail.com' \
    --to=trenta.sis@gmail.com \
    --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.