xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Trenta sis <trenta.sis@gmail.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: Mon, 23 Sep 2013 10:02:51 -0400	[thread overview]
Message-ID: <20130923140251.GH3175@phenom.dumpdata.com> (raw)
In-Reply-To: <CANTbh__oP4scA-3JyeCHXGMG6VuRhbixdQ70djXpdkaLMWMxUA@mail.gmail.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.
> >

  reply	other threads:[~2013-09-23 14:02 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 [this message]
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=20130923140251.GH3175@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=agya.naila@gmail.com \
    --cc=arrfab@centos.org \
    --cc=trenta.sis@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).