All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trenta sis <trenta.sis@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: arrfab@centos.org, agya.naila@gmail.com, JBeulich@suse.com,
	xen-devel@lists.xen.org
Subject: Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash
Date: Sun, 29 Sep 2013 12:47:58 +0200	[thread overview]
Message-ID: <CANTbh__mET2ZCrkKXt6suti-xES5QXDM3qGSvcz8+L_RyaBY+g@mail.gmail.com> (raw)
In-Reply-To: <20130923140251.GH3175@phenom.dumpdata.com>


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

Hello,

In Bladecenter webfrontend appears:

  27 I Blade_09 09/08/13 13:25:17 0x806f0013 <javascript:;> Chassis, (NMI
State) diagnostic interrupt 28 E Blade_09 09/08/13 13:25:12
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 29 I Blade_09 09/08/13
13:09:14 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 30 I Blade_09 09/08/13 13:09:03 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 31 E Blade_09 09/08/13 13:08:58
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 32 I Blade_09 09/08/13
12:46:26 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 33 I Blade_09 09/08/13 12:46:15 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 34 E Blade_09 09/08/13 12:46:11
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 35 I Blade_09 09/08/13
12:34:13 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 36 I Blade_09 09/08/13 12:34:03 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 37 E Blade_09 09/08/13 12:33:58
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 38 I Blade_09 09/08/13
12:27:25 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 39 I Blade_09 09/08/13 12:27:14 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 40 E Blade_09 09/08/13 12:27:10
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 41 I Blade_09 09/08/13
12:20:45 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 42 I Blade_09 09/08/13 12:20:34 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 43 E Blade_09 09/08/13 12:20:30
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 44 I Blade_09 09/08/13
12:18:20 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 45 I Blade_09 09/08/13 12:18:10 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 46 E Blade_09 09/08/13 12:18:05
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 47 I Blade_09 09/08/13
12:15:47 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 48 I Blade_09 09/08/13 12:15:37 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 49 E Blade_09 09/08/13 12:15:32
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020
27 I Blade_09 09/08/13 13:25:17 0x806f0013 Chassis, (NMI State) diagnostic
interrupt
28 E Blade_09 09/08/13 13:25:12 0x10000002 SMI Hdlr: 00151743 HI Fatal
Error, HI_FERR/NERR Value= 0020
29 I Blade_09 09/08/13 13:09:14 0x806f0013 Recovery Chassis, (NMI State)
diagnostic interrupt
30 I Blade_09 09/08/13 13:09:03 0x806f0013 Chassis, (NMI State) diagnostic
interrupt
31 E Blade_09 09/08/13 13:08:58 0x10000002 SMI Hdlr: 00151743 HI Fatal
Error, HI_FERR/NERR Value= 0020
32 I Blade_09 09/08/13 12:46:26 0x806f0013 Recovery Chassis, (NMI State)
diagnostic interrupt
33 I Blade_09 09/08/13 12:46:15 0x806f0013 Chassis, (NMI State) diagnostic
interrupt
34 E Blade_09 09/08/13 12:46:11 0x10000002 SMI Hdlr: 00151743 HI Fatal
Error, HI_FERR/NERR Value= 0020
35 I Blade_09 09/08/13 12:34:13 0x806f0013 Recovery Chassis, (NMI State)
diagnostic interrupt
36 I Blade_09 09/08/13 12:34:03 0x806f0013 Chassis, (NMI State) diagnostic
interrupt
37 E Blade_09 09/08/13 12:33:58 0x10000002 SMI Hdlr: 00151743 HI Fatal
Error, HI_FERR/NERR Value= 0020
38 I Blade_09 09/08/13 12:27:25 0x806f0013 Recovery Chassis, (NMI State)
diagnostic interrupt
39 I Blade_09 09/08/13 12:27:14 0x806f0013 Chassis, (NMI State) diagnostic
interrupt
40 E Blade_09 09/08/13 12:27:10 0x10000002 SMI Hdlr: 00151743 HI Fatal
Error, HI_FERR/NERR Value= 0020
41 I Blade_09 09/08/13 12:20:45 0x806f0013 Recovery Chassis, (NMI State)
diagnostic interrupt
42 I Blade_09 09/08/13 12:20:34 0x806f0013 Chassis, (NMI State) diagnostic
interrupt
43 E Blade_09 09/08/13 12:20:30 0x10000002 SMI Hdlr: 00151743 HI Fatal
Error, HI_FERR/NERR Value= 0020
44 I Blade_09 09/08/13 12:18:20 0x806f0013 Recovery Chassis, (NMI State)
diagnostic interrupt
45 I Blade_09 09/08/13 12:18:10 0x806f0013 Chassis, (NMI State) diagnostic
interrupt
46 E Blade_09 09/08/13 12:18:05 0x10000002 SMI Hdlr: 00151743 HI Fatal
Error, HI_FERR/NERR Value= 0020
47 I Blade_09 09/08/13 12:15:47 0x806f0013 Recovery Chassis, (NMI State)
diagnostic interrupt
48 I Blade_09 09/08/13 12:15:37 0x806f0013 Chassis, (NMI State) diagnostic
interrupt
49 E Blade_09 09/08/13 12:15:32 0x10000002 SMI Hdlr: 00151743 HI Fatal
Error, HI_FERR/NERR Value= 0020
Thanks


  27 I Blade_09 09/08/13 13:25:17 0x806f0013 <javascript:;> Chassis, (NMI
State) diagnostic interrupt 28 E Blade_09 09/08/13 13:25:12
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 29 I Blade_09 09/08/13
13:09:14 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 30 I Blade_09 09/08/13 13:09:03 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 31 E Blade_09 09/08/13 13:08:58
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 32 I Blade_09 09/08/13
12:46:26 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 33 I Blade_09 09/08/13 12:46:15 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 34 E Blade_09 09/08/13 12:46:11
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 35 I Blade_09 09/08/13
12:34:13 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 36 I Blade_09 09/08/13 12:34:03 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 37 E Blade_09 09/08/13 12:33:58
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 38 I Blade_09 09/08/13
12:27:25 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 39 I Blade_09 09/08/13 12:27:14 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 40 E Blade_09 09/08/13 12:27:10
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 41 I Blade_09 09/08/13
12:20:45 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 42 I Blade_09 09/08/13 12:20:34 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 43 E Blade_09 09/08/13 12:20:30
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 44 I Blade_09 09/08/13
12:18:20 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 45 I Blade_09 09/08/13 12:18:10 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 46 E Blade_09 09/08/13 12:18:05
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020 47 I Blade_09 09/08/13
12:15:47 0x806f0013 <javascript:;> Recovery Chassis, (NMI State) diagnostic
interrupt 48 I Blade_09 09/08/13 12:15:37 0x806f0013 <javascript:;> Chassis,
(NMI State) diagnostic interrupt 49 E Blade_09 09/08/13 12:15:32
0x10000002<javascript:;> SMI
Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020

2013/9/23 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

> On Thu, Sep 12, 2013 at 02:47:39PM +0200, Trenta sis wrote:
> > Hello,
> >
> > We need this server and we have made a downgrade to Debian Squeeze.
> > I hope in a few day to have another HS20 to make some additional test,
> I'll
> > try to get all information that you asked and send
> > Sorry, one question what is  PCI SERR ? Where?
>
> If you log in the BladeCenter webfrontend you should see logs of
> each blade. Some of them are 'User XYZ logged in'. But in some cases
> the are more serious ones - such an NMI or PCI SERR. If you could
> copy-n-paste
> them it could help in figuring which PCI device is responsible for causing
> the NMI.
>
> >
> > Thanks for all
> >
> > 2013/9/9 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> >
> > > On Sun, Sep 08, 2013 at 04:41:02PM +0200, Trenta sis wrote:
> > > >  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?
> > >
> > > Did you the workaround help?
> > >
> > > And in regards to finding out exactly what causes it - well there are
> > > logs in the BMC that can point to it the PCI device? Did you check
> those?
> > > Do they save if there is any device that has PCI SERR on them?
> > >
> > > Thanks.
> > >
>

[-- Attachment #1.2: Type: text/html, Size: 16191 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-29 10:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-08 14:35 IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash 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 [this message]
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__mET2ZCrkKXt6suti-xES5QXDM3qGSvcz8+L_RyaBY+g@mail.gmail.com \
    --to=trenta.sis@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=agya.naila@gmail.com \
    --cc=arrfab@centos.org \
    --cc=konrad.wilk@oracle.com \
    --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.