From mboxrd@z Thu Jan 1 00:00:00 1970 From: agya naila Subject: Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash Date: Wed, 6 Feb 2013 14:39:15 +0100 Message-ID: References: <20130205163021.GR8912@reaktio.net> <20130205200847.GS8912@reaktio.net> <51121B5002000078000BC573@nat28.tlf.novell.com> <20130206112910.GT8912@reaktio.net> <20130206132802.GU8912@reaktio.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5335752564451778481==" Return-path: In-Reply-To: <20130206132802.GU8912@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: arrfab@centos.org, Jan Beulich , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============5335752564451778481== Content-Type: multipart/alternative; boundary=047d7b5d4808cbb2ef04d50e7390 --047d7b5d4808cbb2ef04d50e7390 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I configure it by added nmi=3Dignore to my /boot/grub/grub.cfg ### BEGIN /etc/grub.d/20_linux_xen ### submenu "Xen 4.1-amd64" { menuentry 'Ubuntu GNU/Linux, with Xen 4.1-amd64 and Linux 3.2.0-29-generic' --class ubuntu --class gnu-linux --class gnu --c$ insmod part_msdos insmod ext2 set root=3D'(hd0,msdos1)' search --no-floppy --fs-uuid --set=3Droot 730a0f5f-4c35-4391-b760-0b6cf0cdd6a7 echo 'Loading Xen 4.1-amd64 ...' multiboot /boot/xen-4.1-amd64.gz placeholder noreboot dom0_mem=3D1024M nmi=3Dignore echo 'Loading Linux 3.2.0-29-generic ...' module /boot/vmlinuz-3.2.0-29-generic placeholder root=3DUUID=3D730a0f5f-4c35-4391-b760-0b6cf0cdd6a7 ro rootdelay=3D180 q$ echo 'Loading initial ramdisk ...' module /boot/initrd.img-3.2.0-29-generic } And its doent work Agya On Wed, Feb 6, 2013 at 2:28 PM, Pasi K=E4rkk=E4inen wrote: > On Wed, Feb 06, 2013 at 12:48:50PM +0100, agya naila wrote: > > Thank you Pasi to forward this email for me too, it seem not only me > > facing this problem. I found this guy also found similar problem, it= s > in > > french but we can translate it easily using > > google [1] > http://debian.2.n7.nabble.com/Probleme-XEN-4-0-1-et-SQUEEZE-64bits-reboot= -td1230690.html > > I found parameter nmi=3Dignore | dom0 | fatal > > nmi=3Dreaction : Enables you to specify how the hypervisor reacts to= a > non - > > maskable interrupt > > (NMI) resulting from a parity or I/O error. Possible values for > reaction > > are fatal (the hypervisor > > prints a diagnostic message and then hangs), dom0 (send a message to > > domain0 for logging > > purposes but continue), and ignore (ignore the error). If you do not > > specify this option, Xen > > uses the default value dom0 internally. > > But its still doesn't work on my machine. > > > > So you tried adding "nmi=3Dignore" for xen.gz in grub settings and it did= n't > help? > Did you try the other possible values? > > -- Pasi > > > Agya > > On Wed, Feb 6, 2013 at 12:29 PM, Pasi K=E4rkk=E4inen <[2]pasik@iki.f= i> > wrote: > > > > On Wed, Feb 06, 2013 at 07:58:56AM +0000, Jan Beulich wrote: > > > >>> On 05.02.13 at 21:08, Pasi K=E4rkk=E4inen<[3]pasik@iki.fi> w= rote: > > > > Arrfab (CC'd) is actually seeing a similar problem on IBM HS20 > blade > > with > > > > Xen 4.2.1 > > > > with Linux 3.4.28 dom0 kernel. > > > > > > > > Does this ring anyone's bells? > > > > > > > > > > > > serial console log of the crash > > > > > > Which doesn't even include the message in the subject afaics, so= I > > > don't even know what you're talking about. And the other, earlie= r > > > report has no useful information either. > > > > > > From an abstract perspective, a front panel NMI to me would mean > > > someone pressed an NMI button on the system's front panel. You > > > don't think Xen can do anything about this, do you? And even if > > > the NMI has another origin, it's still a hardware generated even= t > > > that Xen has no control over. > > > > > > > Arrfab said Xen crashes and reboots in the middle of the boot > process, > > and the blade chassis management logs the NMI error. The user is n= ot > > pressing (NMI) buttons. > > > > The serial log included is everything he gets. No error visible in > the > > serial log, > > only a crash/reboot without any errors.. No idea what could be > causing > > that.. > > > > The same Dom0 kernel (pvops 3.4.28) boots OK on baremetal without > Xen. > > > > Do you have any Xen and/or dom0 kernel options to use to do furthe= r > > analysis? > > -- Pasi > > > > References > > > > Visible links > > 1. > http://debian.2.n7.nabble.com/Probleme-XEN-4-0-1-et-SQUEEZE-64bits-reboot= -td1230690.html > > 2. mailto:pasik@iki.fi > > 3. mailto:pasik@iki.fi > --047d7b5d4808cbb2ef04d50e7390 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I configure it by added nmi=3Dignore to my=A0/boot/grub/grub.cfg

### BEGIN /etc/grub.d/20_linux_xen ###
submenu &quo= t;Xen 4.1-amd64" {
menuentry 'Ubuntu GNU/Linux, with Xen= 4.1-amd64 and Linux 3.2.0-29-generic' --class ubuntu --class gnu-linux= --class gnu --c$
=A0 =A0 =A0 =A0 insmod part_msdos
=A0 =A0 =A0 =A0 insmod ext= 2
=A0 =A0 =A0 =A0 set root=3D'(hd0,msdos1)'
=A0= =A0 =A0 =A0 search --no-floppy --fs-uuid --set=3Droot 730a0f5f-4c35-4391-b= 760-0b6cf0cdd6a7
=A0 =A0 =A0 =A0 echo =A0 =A0'Loading Xen 4.1= -amd64 ...'
=A0 =A0 =A0 =A0 multiboot =A0 =A0 =A0 /boot/xen-4.1-amd64.gz placehold= er noreboot dom0_mem=3D1024M nmi=3Dignore
=A0 =A0 =A0 =A0 echo = =A0 =A0'Loading Linux 3.2.0-29-generic ...'
=A0 =A0 =A0 = =A0 module =A0/boot/vmlinuz-3.2.0-29-generic placeholder root=3DUUID=3D730a= 0f5f-4c35-4391-b760-0b6cf0cdd6a7 ro rootdelay=3D180 q$
=A0 =A0 =A0 =A0 echo =A0 =A0'Loading initial ramdisk ...'
=A0 =A0 =A0 =A0 module =A0/boot/initrd.img-3.2.0-29-generic
}

And its doent work

Agya


On Wed, Feb 6, 2013 at 2:28 PM, Pasi K=E4rkk= =E4inen <pasik@iki.fi> wrote:
On Wed, Feb 06, 2013 at 12:48:50PM +0100, agya naila wrot= e:
> =A0 =A0Thank you Pasi to forward this email for me too, it seem not on= ly me
> =A0 =A0facing this problem. I found this guy also found similar proble= m, its in
> =A0 =A0french but we can translate it easily using
> =A0 =A0google [1]htt= p://debian.2.n7.nabble.com/Probleme-XEN-4-0-1-et-SQUEEZE-64bits-reboot-td12= 30690.html
> =A0 =A0I found parameter nmi=3Dignore | dom0 | fatal=
> =A0 =A0nmi=3Dreaction : Enables you to specify how the hypervisor reac= ts to a non -
> =A0 =A0maskable interrupt
> =A0 =A0(NMI) resulting from a parity or I/O error. Possible values for= reaction
> =A0 =A0are fatal (the hypervisor
> =A0 =A0prints a diagnostic message and then hangs), dom0 (send a messa= ge to
> =A0 =A0domain0 for logging
> =A0 =A0purposes but continue), and ignore (ignore the error). If you d= o not
> =A0 =A0specify this option, Xen
> =A0 =A0uses the default value dom0 internally.
> =A0 =A0But its still doesn't work on my machine.
>

So you tried adding "nmi=3Dignore" for xen.gz in grub setti= ngs and it didn't help?
Did you try the other possible values?

-- Pasi

> =A0 =A0Agya
> =A0 =A0On Wed, Feb 6, 2013 at 12:29 PM, Pasi K=E4rkk= =E4inen <[2]pasik@iki.fi> wrote:<= br> >
> =A0 =A0 =A0On Wed, Feb 06, 2013 at 07:58:56AM +0000, Jan Beulich wrote= :
> =A0 =A0 =A0> >>> On 05.02.13 = at 21:08, Pasi K=E4rkk=E4inen<[3]pasik@i= ki.fi> wrote:
> =A0 =A0 =A0> > Arrfab (CC'd) is actually seeing a similar pr= oblem on IBM HS20 blade
> =A0 =A0 =A0with
> =A0 =A0 =A0> > Xen 4.2.1
> =A0 =A0 =A0> > with Linux 3.4.28 dom0 kernel.
> =A0 =A0 =A0> >
> =A0 =A0 =A0> > Does this ring anyone's bells?
> =A0 =A0 =A0> >
> =A0 =A0 =A0> >
> =A0 =A0 =A0> > serial console log of the crash
> =A0 =A0 =A0>
> =A0 =A0 =A0> Which doesn't even include the message in the subj= ect afaics, so I
> =A0 =A0 =A0> don't even know what you're talking about. And= the other, earlier
> =A0 =A0 =A0> report has no useful information either.
> =A0 =A0 =A0>
> =A0 =A0 =A0> From an abstract perspective, a front panel NMI to me = would mean
> =A0 =A0 =A0> someone pressed an NMI button on the system's fron= t panel. You
> =A0 =A0 =A0> don't think Xen can do anything about this, do you= ? And even if
> =A0 =A0 =A0> the NMI has another origin, it's still a hardware = generated event
> =A0 =A0 =A0> that Xen has no control over.
> =A0 =A0 =A0>
>
> =A0 =A0 =A0Arrfab said Xen crashes and reboots in the middle of the bo= ot process,
> =A0 =A0 =A0and the blade chassis management logs the NMI error. The us= er is not
> =A0 =A0 =A0pressing (NMI) buttons.
>
> =A0 =A0 =A0The serial log included is everything he gets. No error vis= ible in the
> =A0 =A0 =A0serial log,
> =A0 =A0 =A0only a crash/reboot without any errors.. No idea what could= be causing
> =A0 =A0 =A0that..
>
> =A0 =A0 =A0The same Dom0 kernel (pvops 3.4.28) boots OK on baremetal w= ithout Xen.
>
> =A0 =A0 =A0Do you have any Xen and/or dom0 kernel options to use to do= further
> =A0 =A0 =A0analysis?
> =A0 =A0 =A0-- Pasi
>
> References
>
> =A0 =A0Visible links
> =A0 =A01. http://debian.2.= n7.nabble.com/Probleme-XEN-4-0-1-et-SQUEEZE-64bits-reboot-td1230690.html
> =A0 =A02. mailto:pasik@iki.fi
> =A0 =A03. mailto:pasik@iki.fi

--047d7b5d4808cbb2ef04d50e7390-- --===============5335752564451778481== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============5335752564451778481==--