From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk 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 Message-ID: <20130923140251.GH3175@phenom.dumpdata.com> References: <20130909191524.GA4215@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Trenta sis Cc: arrfab@centos.org, agya.naila@gmail.com, JBeulich@suse.com, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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 > > > 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. > >