XEN 4.1 error Critical Interrupt - Front panel NMI

XEN 4.1 error Critical Interrupt - Front panel NMI

[agya naila]

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

Hello Everyone,

I am quite new on XEN. I tried to installed XEN on my server and I know
this server series IBM Xeon 3,4 Ghz didn't have Intel VTx support so I am
pllaning to use paravirtualization.
I configure the server with Ubuntu Desktop  12.0464 bit as dom0 with XEN
4.1 64 hypervisor. The configuration using repositories exactly by this
tutorial https://help.ubuntu.com/community/XenProposed :

Installing Xen

Install a 64-bit hypervisor

sudo apt-get install xen-hypervisor-amd64

Modify GRUB to default to booting Xen:

sudo sed -i 's/GRUB_DEFAULT=.*\+/GRUB_DEFAULT="Xen 4.1-amd64"/'
/etc/default/grubsudo update-grub

Set the default toolstack to xm (aka xend):

sudo sed -i 's/TOOLSTACK=.*\+/TOOLSTACK="xm"/' /etc/default/xen

Now reboot:

sudo reboot



But when rebooting the Dom0 failed to start, enclosed was the error message
when Xen booting and after that Dom0 will restarting over and over.
On Blade server system  log I got error message :
(Bestak_septaher) SMI Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value=
0020
(Bestak_septaher) Critical Interrupt - Front panel NMI

Please Suggest, thank you very much for any one help.

Best Regards,

Agya

[-- Attachment #1.2: Type: text/html, Size: 9480 bytes --]

[-- Attachment #2: eror.jpg --]
[-- Type: image/jpeg, Size: 199162 bytes --]

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: XEN 4.1 error Critical Interrupt - Front panel NMI

[Pasi Kärkkäinen]

On Tue, Feb 05, 2013 at 04:49:47PM +0100, agya naila wrote:
>    Hello Everyone,
>    I am quite new on XEN. I tried to installed XEN on my server and I know
>    this server series IBM Xeon 3,4 Ghz didn't have Intel VTx support so I am
>    pllaning to use paravirtualization.
>    I configure the server with Ubuntu Desktop  12.0464 bit as dom0 with XEN
>    4.1 64 hypervisor. The configuration using repositories exactly by this
>    tutorial [1]https://help.ubuntu.com/community/XenProposed :
>

- What exact Xen version are you using? 
- What exact Linux dom0 kernel are you using? 
- Please paste your grub settings for the Xen entry.
- Did you capture the error/crash logs from the Serial console? (SOL provided by the blade management).


-- Pasi

 
>                                  Installing Xen
> 
>    Install a 64-bit hypervisor
> 
>  sudo apt-get install xen-hypervisor-amd64
> 
>    Modify GRUB to default to booting Xen:
> 
>  sudo sed -i 's/GRUB_DEFAULT=.*\+/GRUB_DEFAULT="Xen 4.1-amd64"/' /etc/default/grub
>  sudo update-grub
> 
>    Set the default toolstack to xm (aka xend):
> 
>  sudo sed -i 's/TOOLSTACK=.*\+/TOOLSTACK="xm"/' /etc/default/xen
> 
>    Now reboot:
> 
>  sudo reboot
> 
>    But when rebooting the Dom0 failed to start, enclosed was the error
>    message when Xen booting and after that Dom0 will restarting over and
>    over.
>    On Blade server system  log I got error message :
>    (Bestak_septaher) SMI Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value=
>    0020
>    (Bestak_septaher) Critical Interrupt - Front panel NMI
>    Please Suggest, thank you very much for any one help.
>    Best Regards,
>    Agya
> 
> References
> 
>    Visible links
>    1. https://help.ubuntu.com/community/XenProposed


> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Re: XEN 4.1 error Critical Interrupt - Front panel NMI

[agya naila]

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

Hello Passi,

Thank you for your email, below is my answer :


> - What exact Xen version are you using?
>
I Used xen-hypervisor-4.1-amd64 version

- What exact Linux dom0 kernel are you using?
>
I used ubuntu-12.04.1-desktop-amd64


> - Please paste your grub settings for the Xen entry.
>
Here it is my grub
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
GRUB_CMDLINE_LINUX="rootdelay=180"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to
Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

# Disable OS prober to prevent virtual machines on logical volumes from
appearing in the boot menu.
GRUB_DISABLE_OS_PROBER=true

# Xen boot parameters for all Xen boots
#GRUB_CMDLINE_XEN=""
GRUB_CMDLINE_XEN="dom0_max_vcpus=2"
GRUB_CMDLINE_XEN="nmi=reaction"
GRUB_CMDLINE_XEN="noht"
GRUB_CMDLINE_XEN="noreboot"


# Xen boot parameters for non-recovery Xen boots (in addition to
GRUB_CMDLINE_X$

GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=2048M"



> - Did you capture the error/crash logs from the Serial console? (SOL
> provided by the blade management).
>
> I have enclosed the screen capture of the error when the XEN booting on my
previous email. From the console I got message :
 (Blade12) SMI Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value=  0020
 (Blade12) Critical Interrupt - Front panel NMI

I hope you could helped me :)

Thank You,

Agya


> -- Pasi
>
>
> >                                  Installing Xen
> >
> >    Install a 64-bit hypervisor
> >
> >  sudo apt-get install xen-hypervisor-amd64
> >
> >    Modify GRUB to default to booting Xen:
> >
> >  sudo sed -i 's/GRUB_DEFAULT=.*\+/GRUB_DEFAULT="Xen 4.1-amd64"/'
> /etc/default/grub
> >  sudo update-grub
> >
> >    Set the default toolstack to xm (aka xend):
> >
> >  sudo sed -i 's/TOOLSTACK=.*\+/TOOLSTACK="xm"/' /etc/default/xen
> >
> >    Now reboot:
> >
> >  sudo reboot
> >
> >    But when rebooting the Dom0 failed to start, enclosed was the error
> >    message when Xen booting and after that Dom0 will restarting over and
> >    over.
> >    On Blade server system  log I got error message :
> >    (Bestak_septaher) SMI Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR
> Value=
> >    0020
> >    (Bestak_septaher) Critical Interrupt - Front panel NMI
> >    Please Suggest, thank you very much for any one help.
> >    Best Regards,
> >    Agya
> >
> > References
> >
> >    Visible links
> >    1. https://help.ubuntu.com/community/XenProposed
>
>
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
>
>

[-- Attachment #1.2: Type: text/html, Size: 5463 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[Pasi Kärkkäinen]

On Tue, Feb 05, 2013 at 06:30:21PM +0200, Pasi Kärkkäinen wrote:
> On Tue, Feb 05, 2013 at 04:49:47PM +0100, agya naila wrote:
> >    Hello Everyone,
> >    I am quite new on XEN. I tried to installed XEN on my server and I know
> >    this server series IBM Xeon 3,4 Ghz didn't have Intel VTx support so I am
> >    pllaning to use paravirtualization.
> >    I configure the server with Ubuntu Desktop  12.0464 bit as dom0 with XEN
> >    4.1 64 hypervisor. The configuration using repositories exactly by this
> >    tutorial [1]https://help.ubuntu.com/community/XenProposed :
> >
> 
> - What exact Xen version are you using? 
> - What exact Linux dom0 kernel are you using? 
> - Please paste your grub settings for the Xen entry.
> - Did you capture the error/crash logs from the Serial console? (SOL provided by the blade management).
> 
> 

<snip>

> > 
> >    Now reboot:
> > 
> >  sudo reboot
> > 
> >    But when rebooting the Dom0 failed to start, enclosed was the error
> >    message when Xen booting and after that Dom0 will restarting over and
> >    over.
> >    On Blade server system  log I got error message :
> >    (Bestak_septaher) SMI Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value=
> >    0020
> >    (Bestak_septaher) Critical Interrupt - Front panel NMI
> >    Please Suggest, thank you very much for any one help.
>

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 (also available on: http://pastebin.centos.org/1204/):


(XEN) Xen version 4.2.1 (mockbuild@(none)) (gcc (GCC) 4.4.6 20120305 (Red Hat 4.4.6-4)) Thu Jan 31 20:36:24 UTC 2013
(XEN) Latest ChangeSet: unavailable
(XEN) Console output is synchronous.
(XEN) Bootloader: GNU GRUB 0.97
(XEN) Command line: dom0_mem=256M,max:256M loglvl=all guest_loglvl=all com2=19200,8n1 console=com2,vga lapic=debug apic_verbosity=debug apic=debug iommu=off sync_console
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 2 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 2 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009d400 (usable)
(XEN)  000000000009d400 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000d7fb0580 (usable)
(XEN)  00000000d7fb0580 - 00000000d7fd0000 (ACPI data)
(XEN)  00000000d7fd0000 - 00000000d8000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000128000000 (usable)
(XEN) ACPI: RSDP 000FDFE0, 0014 (r0 IBM   )
(XEN) ACPI: RSDT D7FCFF80, 0030 (r1 IBM    SERBLADE     1000 IBM  45444F43)
(XEN) ACPI: FACP D7FCFEC0, 0084 (r2 IBM    SERBLADE     1000 IBM  45444F43)
(XEN) ACPI: DSDT D7FBE4A8, 1F2A (r1 IBM    SERBLADE     1000 INTL  2002025)
(XEN) ACPI: FACS D7FCFD80, 0040
(XEN) ACPI: APIC D7FCFE00, 00A8 (r1 IBM    SERBLADE     1000 IBM  45444F43)
(XEN) ACPI: MCFG D7FCFDC0, 003C (r1 IBM    SERBLADE     1000 IBM  45444F43)
(XEN) System RAM: 4095MB (4193588kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-0000000128000000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 0009d540
(XEN) DMI 2.3 present.
(XEN) APIC boot state is 'xapic'
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x588
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[584,0], pm1x_evt[580,0]
(XEN) ACPI:                  wakeup_vec[d7fcfd8c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
(XEN) Processor #6 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
(XEN) Processor #7 15:4 APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
(XEN) ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 14, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x0d] address[0xfec10000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 13, version 32, address 0xfec10000, GSI 24-47
(XEN) ACPI: IOAPIC (id[0x0c] address[0xfec81000] gsi_base[48])
(XEN) IOAPIC[2]: apic_id 12, version 32, address 0xfec81000, GSI 48-71
(XEN) ACPI: IOAPIC (id[0x0b] address[0xfec81400] gsi_base[72])
(XEN) IOAPIC[3]: apic_id 11, version 32, address 0xfec81400, GSI 72-95
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ11 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 4 I/O APICs
(XEN) Table is not found!
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 4 CPUs (0 hotplug CPUs)
(XEN) mapped APIC to ffff82c3ffdfe000 (fee00000)
(XEN) mapped IOAPIC to ffff82c3ffdfd000 (fec00000)
(XEN) mapped IOAPIC to ffff82c3ffdfc000 (fec10000)
(XEN) mapped IOAPIC to ffff82c3ffdfb000 (fec81000)
(XEN) mapped IOAPIC to ffff82c3ffdfa000 (fec81400)
(XEN) IRQ limits: 96 GSI, 688 MSI/MSI-X
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3200.224 MHz processor.
(XEN) Initing memory sharing.
(XEN) traps.c:3156: GPF (0000): ffff82c48019e43d -> ffff82c4802164d0
(XEN) mce_intel.c:1239: MCA Capability: BCAST 0 SER 0 CMCI 0 firstbank 0 extended MCE MSR 18
(XEN) Intel machine check reporting enabled
(XEN) PCI: Found Intel Corporation E7520 Memory Controller Hub with MMCONFIG support.
(XEN) PCI: Using MCFG for segment 0000 bus 00-ff
(XEN) I/O virtualisation disabled
(XEN) Getting VERSION: 50014
(XEN) Getting VERSION: 50014
(XEN) Getting ID: 0
(XEN) Getting LVT0: 700
(XEN) Getting LVT1: 400
(XEN) enabled ExtINT on CPU#0
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) init IO_APIC IRQs
(XEN)  IO-APIC (apicid-pin) 14-0, 14-16, 14-17, 14-18, 14-19, 14-20, 14-21, 14-22, 14-23, 13-0, 13-1, 13-2, 13-3, 13-4, 13-5, 13-6, 13-7, 13-8, 13-9, 13-10, 13-11, 13-12, 13-13, 13-14, 13-15, 13-16, 13-17, 13-18, 13-19, 13-20, 13-21, 13-22, 13-23, 12-0, 12-1, 12-2, 12-3, 12-4, 12-5, 12-6, 12-7, 12-8, 12-9, 12-10, 12-11, 12-12, 12-13, 12-14, 12-15, 12-16, 12-17, 12-18, 12-19, 12-20, 12-21, 12-22, 12-23, 11-0, 11-1, 11-2, 11-3, 11-4, 11-5, 11-6, 11-7, 11-8, 11-9, 11-10, 11-11, 11-12, 11-13, 11-14, 11-15, 11-16, 11-17, 11-18, 11-19, 11-20, 11-21, 11-22, 11-23 not connected.
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) number of MP IRQ sources: 15.
(XEN) number of IO-APIC #14 registers: 24.
(XEN) number of IO-APIC #13 registers: 24.
(XEN) number of IO-APIC #12 registers: 24.
(XEN) number of IO-APIC #11 registers: 24.
(XEN) testing the IO APIC.......................
(XEN) IO APIC #14......
(XEN) .... register #00: 0E000000
(XEN) .......    : physical APIC id: 0E
(XEN) .......    : Delivery Type: 0
(XEN) .......    : LTS          : 0
(XEN) .... register #01: 00178020
(XEN) .......     : max redirection entries: 0017
(XEN) .......     : PRQ implemented: 1
(XEN) .......     : IO APIC version: 0020
(XEN) .... register #03: 00000001
(XEN) .......     : Boot DT    : 1
(XEN) .... IRQ redirection table:
(XEN)  NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:  
(XEN)  00 000 00  1    0    0   0   0    0    0    00
(XEN)  01 001 01  0    0    0   0   0    1    1    28
(XEN)  02 001 01  0    0    0   0   0    1    1    F0
(XEN)  03 001 01  0    0    0   0   0    1    1    F1
(XEN)  04 001 01  0    0    0   0   0    1    1    30
(XEN)  05 001 01  0    0    0   0   0    1    1    38
(XEN)  06 001 01  0    0    0   0   0    1    1    40
(XEN)  07 001 01  0    0    0   0   0    1    1    48
(XEN)  08 001 01  0    0    0   0   0    1    1    50
(XEN)  09 001 01  0    0    0   0   0    1    1    58
(XEN)  0a 001 01  0    0    0   0   0    1    1    60
(XEN)  0b 001 01  1    1    0   0   0    1    1    68
(XEN)  0c 001 01  0    0    0   0   0    1    1    70
(XEN)  0d 001 01  0    0    0   0   0    1    1    78
(XEN)  0e 001 01  0    0    0   0   0    1    1    88
(XEN)  0f 001 01  0    0    0   0   0    1    1    90
(XEN)  10 000 00  1    0    0   0   0    0    0    00
(XEN)  11 000 00  1    0    0   0   0    0    0    00
(XEN)  12 000 00  1    0    0   0   0    0    0    00
(XEN)  13 000 00  1    0    0   0   0    0    0    00
(XEN)  14 000 00  1    0    0   0   0    0    0    00
(XEN)  15 000 00  1    0    0   0   0    0    0    00
(XEN)  16 000 00  1    0    0   0   0    0    0    00
(XEN)  17 000 00  1    0    0   0   0    0    0    00
(XEN) IO APIC #13......
(XEN) .... register #00: 0D000000
(XEN) .......    : physical APIC id: 0D
(XEN) .......    : Delivery Type: 0
(XEN) .......    : LTS          : 0
(XEN) .... register #01: 00178020
(XEN) .......     : max redirection entries: 0017
(XEN) .......     : PRQ implemented: 1
(XEN) .......     : IO APIC version: 0020
(XEN) .... register #03: 00000001
(XEN) .......     : Boot DT    : 1
(XEN) .... IRQ redirection table:
(XEN)  NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:  
(XEN)  00 000 00  1    0    0   0   0    0    0    00
(XEN)  01 000 00  1    0    0   0   0    0    0    00
(XEN)  02 000 00  1    0    0   0   0    0    0    00
(XEN)  03 000 00  1    0    0   0   0    0    0    00
(XEN)  04 000 00  1    0    0   0   0    0    0    00
(XEN)  05 000 00  1    0    0   0   0    0    0    00
(XEN)  06 000 00  1    0    0   0   0    0    0    00
(XEN)  07 000 00  1    0    0   0   0    0    0    00
(XEN)  08 000 00  1    0    0   0   0    0    0    00
(XEN)  09 000 00  1    0    0   0   0    0    0    00
(XEN)  0a 000 00  1    0    0   0   0    0    0    00
(XEN)  0b 000 00  1    0    0   0   0    0    0    00
(XEN)  0c 000 00  1    0    0   0   0    0    0    00
(XEN)  0d 000 00  1    0    0   0   0    0    0    00
(XEN)  0e 000 00  1    0    0   0   0    0    0    00
(XEN)  0f 000 00  1    0    0   0   0    0    0    00
(XEN)  10 000 00  1    0    0   0   0    0    0    00
(XEN)  11 000 00  1    0    0   0   0    0    0    00
(XEN)  12 000 00  1    0    0   0   0    0    0    00
(XEN)  13 000 00  1    0    0   0   0    0    0    00
(XEN)  14 000 00  1    0    0   0   0    0    0    00
(XEN)  15 000 00  1    0    0   0   0    0    0    00
(XEN)  16 000 00  1    0    0   0   0    0    0    00
(XEN)  17 000 00  1    0    0   0   0    0    0    00
(XEN) IO APIC #12......
(XEN) .... register #00: 0C000000
(XEN) .......    : physical APIC id: 0C
(XEN) .......    : Delivery Type: 0
(XEN) .......    : LTS          : 0
(XEN) .... register #01: 00178020
(XEN) .......     : max redirection entries: 0017
(XEN) .......     : PRQ implemented: 1
(XEN) .......     : IO APIC version: 0020
(XEN) .... register #02: 0C000000
(XEN) .......     : arbitration: 0C
(XEN) .... register #03: 00000001
(XEN) .......     : Boot DT    : 1
(XEN) .... IRQ redirection table:
(XEN)  NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:  
(XEN)  00 000 00  1    0    0   0   0    0    0    00
(XEN)  01 000 00  1    0    0   0   0    0    0    00
(XEN)  02 000 00  1    0    0   0   0    0    0    00
(XEN)  03 000 00  1    0    0   0   0    0    0    00
(XEN)  04 000 00  1    0    0   0   0    0    0    00
(XEN)  05 000 00  1    0    0   0   0    0    0    00
(XEN)  06 000 00  1    0    0   0   0    0    0    00
(XEN)  07 000 00  1    0    0   0   0    0    0    00
(XEN)  08 000 00  1    0    0   0   0    0    0    00
(XEN)  09 000 00  1    0    0   0   0    0    0    00
(XEN)  0a 000 00  1    0    0   0   0    0    0    00
(XEN)  0b 000 00  1    0    0   0   0    0    0    00
(XEN)  0c 000 00  1    0    0   0   0    0    0    00
(XEN)  0d 000 00  1    0    0   0   0    0    0    00
(XEN)  0e 000 00  1    0    0   0   0    0    0    00
(XEN)  0f 000 00  1    0    0   0   0    0    0    00
(XEN)  10 000 00  1    0    0   0   0    0    0 0   0    0    0    00
(XEN)  14 000 00  1    0    0   0   0    0    0    00
(XEN)  15 000 00  1    0    0   0   0    0    0    00
(XEN)  16 000 00  1    0    0   0   0    0    0    00
(XEN)  17 000 00  1    0    0   0   0    0    0    00
(XEN) IO APIC #11......
(XEN) .... register #00: 0B000000
(XEN) .......    : physical APIC id: 0B
(XEN) .......    : Delivery Type: 0
(XEN) .......    : LTS          : 0
(XEN) .... register #01: 00178020
(XEN) .......     : max redirection entries: 0017
(XEN) .......     : PRQ implemented: 1
(XEN) .......     : IO APIC version: 0020
(XEN) .... register #02: 0B000000
(XEN) .......     : arbitration: 0B
(XEN) .... register #03: 00000001
(XEN) .......     : Boot DT    : 1
(XEN) .... IRQ redirection table:
(XEN)  NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:  
(XEN)  00 000 00  1    0    0   0   0    0    0    00
(XEN)  01 000 00  1    0    0   0   0    0    0    00
(XEN)  02 000 00  1    0    0   0   0    0    0    00
(XEN)  03 000 00  1    0    0   0   0    0    0    00
(XEN)  04 000 00  1    0    0   0   0    0    0    00
(XEN)  05 000 00  1    0    0   0   0    0    0    00
(XEN)  06 000 00  1    0    0   0   0    0    0    00
(XEN)  07 000 00  1    0    0   0   0    0    0    00
(XEN)  08 000 00  1    0    0   0   0    0    0    00
(XEN)  09 000 00  1    0    0   0   0    0    0    00
(XEN)  0a 000 00  1    0    0   0   0    0    0    00
(XEN)  0b 000 00  1    0    0   0   0    0    0    00
(XEN)  0c 000 00  1    0    0   0   0    0    0    00
(XEN)  0d 000 00  1    0    0   0   0    0    0    00
(XEN)  0e 000 00  1    0    0   0   0    0    0    00
(XEN)  0f 000 00  1    0    0   0   0    0    0    00
(XEN)  10 000 00  1    0    0   0   0    0    0    00
(XEN)  11 000 00  1    0    0   0   0    0    0    00
(XEN)  12 000 00  1    0    0   0   0    0    0    00
(XEN)  13 000 00  1    0    0   0   0    0    0    00
(XEN)  14 000 00  1    0    0   0   0    0    0    00
(XEN)  15 000 00  1    0    0   0   0    0    0    00
(XEN)  16 000 00  1    0    0   0   0    0    0    00
(XEN)  17 000 00  1    0    0   0   0    0    0    00
(XEN) Using vector-based indexing
(XEN) IRQ to pin mappings:
(XEN) IRQ240 -> 0:2
(XEN) IRQ40 -> 0:1
(XEN) IRQ241 -> 0:3
(XEN) IRQ48 -> 0:4
(XEN) IRQ56 -> 0:5
(XEN) IRQ64 -> 0:6
(XEN) IRQ72 -> 0:7
(XEN) IRQ80 -> 0:8
(XEN) IRQ88 -> 0:9
(XEN) IRQ96 -> 0:10
(XEN) IRQ104 -> 0:11
(XEN) IRQ112 -> 0:12
(XEN) IRQ120 -> 0:13
(XEN) IRQ136 -> 0:14
(XEN) IRQ144 -> 0:15
(XEN) .................................... done.
(XEN) Using local APIC timer interrupts.
(XEN) calibrating APIC timer ...
(XEN) ..... CPU clock speed is 3200.1563 MHz.
(XEN) ..... host bus clock speed is 200.0096 MHz.
(XEN) ..... bus_scale = 0x0000CCD7
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) Allocated console ring of 32 KiB.
(XEN) masked ExtINT on CPU#1
(XEN) masked ExtINT on CPU#2
(XEN) masked ExtINT on CPU#3
(XEN) Brought up 4 CPUs
(XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'.
(XEN) ACPI sleep)  Init. ramdisk: ffffffff82b1b000->ffffffff859e5c00
(XEN)  Phys-Mach map: ffffffff859e6000->ffffffff85a66000
(XEN)  Start info:    ffffffff85a66000->ffffffff85a664b4
(XEN)  Page tables:   ffffffff85a67000->ffffffff85a98000
(XEN)  Boot stack:    ffffffff85a98000->ffffffff85a99000
(XEN)  TOTAL:         ffffffff80000000->ffffffff85c00000
(XEN)  ENTRY ADDRESS: ffffffff81b1c200
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Scrubbing Free RAM: ......................................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) **********************************************
(XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) ******* This option is intended to aid debugging of Xen by ensuring
(XEN) ******* that all output is synchronously delivered on the serial line.
(XEN) ******* However it can introduce SIGNIFICANT latencies and affect
(XEN) ******* timekeeping. It is NOT recommended for production use!
(XEN) **********************************************
(XEN) 3... 2... 1...
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 252kB init memory.
mapping kernel into physical memory
about to get started...
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 3.4.28-6.el6.centos.alt.x86_64 (mockbuild@bn3.alt.bsys.dev.centos.org) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Thu Jan 31 22:39:42 UTC 2013
Command line: ro root=/dev/mapper/c6kvm--vg-lv_root rd_NO_LUKS rd_LVM_LV=c6kvm-vg/lv_root LANG=en_US.UTF-8 crashkernel=auto rd_NO_MD SYSFONT=latarcyrheb-sun16 rd_LVM_LV=c6kvm-vg/lv_swap  KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM earlyprintk=xen console=hvc0 nomodeset initcall_debug debug loglevel=10
Freeing 9d-100 pfn range: 99 pages freed
Released 99 pages of unused memory
Set 164019 page(s) to 1-1 mapping
Populating 10000-10063 pfn range: 99 pages added
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 000000000009d000 (usable)
 Xen: 000000000009d400 - 0000000000100000 (reserved)
 Xen: 0000000000100000 - 0000000010063000 (usable)
 Xen: 0000000010063000 - 00000000d7fb0580 (unusable)
 Xen: 00000000d7fb0580 - 00000000d7fd0000 (ACPI data)
 Xen: 00000000d7fd0000 - 00000000d8000000 (reserved)
 Xen: 00000000e0000000 - 00000000f0000000 (reserved)
 Xen: 00000000fec00000 - 0000000100000000 (reserved)
 Xen: 0000000100000000 - 0000000128000000 (unusable)
bootconsole [xenboot0] enabled
Notice: NX (Execute Disable) protection missing in CPU!
SMBIOS 2.3 present.
DMI: IBM IBM BladeCenter HS20 -[8843E6G]-/Server Blade, BIOS -[BWE132AUS-1.13]- 12/19/2008
e820 update range: 000000M    SERBLADE 00001000 INTL 02002025)
ACPI: FACS 00000000d7fcfd80 00040
ACPI: APIC 00000000d7fcfe00 000A8 (v01 IBM    SERBLADE 00001000 IBM  45444F43)
ACPI: MCFG 00000000d7fcfdc0 0003C (v01 IBM    SERBLADE 00001000 IBM  45444F43)
ACPI: Local APIC address 0xfee00000
NUMA turned off
Faking a node at 0000000000000000-0000000010063000
Initmem setup node 0 0000000000000000-0000000010063000
  NODE_DATA [000000001003d000 - 0000000010062fff]
Zone PFN ranges:
  DMA      0x00000010 -> 0x00001000
  DMA32    0x00001000 -> 0x00100000
  Normal   empty
Movable zone start PFN for each node
Early memory PFN ranges
    0: 0x00000010 -> 0x0000009d
    0: 0x00000100 -> 0x00010063
On node 0 totalpages: 65520
  DMA zone: 56 pages used for memmap
  DMA zone: 5 pages reserved
  DMA zone: 3920 pages, LIFO batch:0
  DMA32 zone: 842 pages used for memmap
  DMA32 zone: 60697 pages, LIFO batch:15
ACPI: PM-Timer IO Port: 0x588
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 14, version 253, address 0xfec00000, GSI 0-253
ACPI: IOAPIC (id[0x0d] address[0xfec10000] gsi_base[24])
IOAPIC[1]: apic_id 13, version 253, address 0xfec10000, GSI 24-277
ACPI: IOAPIC (id[0x0c] address[0xfec81000] gsi_base[48])
IOAPIC[2]: apic_id 12, version 253, address 0xfec81000, GSI 48-301
ACPI: IOAPIC (id[0x0b] address[0xfec81400] gsi_base[72])
IOAPIC[3]: apic_id 11, version 253, address 0xfec81400, GSI 72-325
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ11 used by override.
Using ACPI (MADT) for SMP configuration information
SMP: Allowing 4 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 342
PM: Registered nosave memory: 000000000009d000 - 000000000009e000
PM: Registered nosave memory: 000000000009e000 - 0000000000100000
Allocating PCI resources starting at f0000000 (gap: f0000000:ec00000)
Booting paravirtualized kernel on Xen
Xen version: 4.2.1 (preserve-AD)
setup_percpu: NR_CPUS:4096 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1
PERCPU: Embedded 28 pages/cpu @ffff88000fe00000 s82432 r8192 d24064 u524288
pcpu-alloc: s82432 r8192 d24064 u524288 alloc=1*2097152
pcpu-alloc: [0] 0 1 2 3
Built 1 zonelists in Node order, mobility grouping on.  Total pages: 64617
Policy zone: DMA32
Kernel command line: ro root=/dev/mapper/c6kvm--vg-lv_root rd_NO_LUKS rd_LVM_LV=c6kvm-vg/lv_root LANG=en_US.UTF-8 crashkernel=auto rd_NO_MD SYSFONT=latarcyrheb-sun16 rd_LVM_LV=c6kvm-vg/lv_swap  KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM earlyprintk=xen console=hvc0 nomodeset initcall_debug debug loglevel=10
PID hash table entries: 1024 (order: 1, 8192 bytes)
Placing 64MB software IO TLB between ffff88000b200000 - ffff88000f200000
software IO TLB at phys 0xb200000 - 0xf200000
Memory: 125496k/262540k available (5643k kernel code, 460k absent, 136584k reserved, 5643k data, 1464k init)
Hierarchical RCU implementation.
NR_IRQS:262400 nr_irqs:1024 16
xen: sci override: global_irq=11 trigger=0 polarity=0
xen: registering gsi 11 triggering 0 polarity 0
xen: --> pirq=11 -> irq=11 (gsi=11)
(XEN) IOAPIC[0]: Set PCI routing entry (14-11 -> 0x68 -> IRQ 11 Mode:1 Active:0)
xen: acpi sci 11
xen: --> pirq=1 -> irq=1 (gsi=1)
xen: --> pirq=2 -> irq=2 (gsi=2)
xen: --> pirq=3 -> irq=3 (gsi=3)
xen: --> pirq=4 -> irq=4 (gsi=4)
xen: --> pirq=5 -> irq=5 (gsi=5)
xen: --> pirq=6 -> irq=6 (gsi=6)
xen: --> pirq=7 -> irq=7 (gsi=7)
xen: --> pirq=8 -> irq=8 (gsi=8)
xen: --> pirq=9 -> irq=9 (gsi=9)
xen: --> pirq=10 -> irq=10 (gsi=10)
xen: --> pirq=12 -> irq=12 (gsi=12)
xen: --> pirq=13 -> irq=13 (gsi=13)
xen: --> pirq=14 -> irq=14 (gsi=14)
xen: --> pirq=15 ->nit_flags_sys_enter+0x0/0x12 returned 0 after 0 usecs
calling  init_hw_perf_events+0x0/0x44f @ 1
Performance Events: unsupported Netburst CPU model 4 no PMU driver, software events only.
initcall init_hw_perf_events+0x0/0x44f returned 0 after 2929 usecs
calling  register_trigger_all_cpu_backtrace+0x0/0x1f @ 1
initcall register_trigger_all_cpu_backtrace+0x0/0x1f returned 0 after 0 usecs
calling  spawn_ksoftirqd+0x0/0x57 @ 1
initcall spawn_ksoftirqd+0x0/0x57 returned 0 after 0 usecs
calling  init_workqueues+0x0/0x2f5 @ 1
initcall init_workqueues+0x0/0x2f5 returned 0 after 0 usecs
calling  migration_init+0x0/0x71 @ 1
initcall migration_init+0x0/0x71 returned 0 after 0 usecs
calling  cpu_stop_init+0x0/0xb6 @ 1
initcall cpu_stop_init+0x0/0xb6 returned 0 after 0 usecs
calling  rcu_scheduler_really_started+0x0/0x12 @ 1
initcall rcu_scheduler_really_started+0x0/0x12 returned 0 after 0 usecs
calling  relay_init+0x0/0x14 @ 1
initcall relay_init+0x0/0x14 returned 0 after 0 usecs
calling  tracer_alloc_buffers+0x0/0x235 @ 1
initcall tracer_alloc_buffers+0x0/0x235 returned 0 after 0 usecs
calling  init_trace_printk+0x0/0x12 @ 1
initcall init_trace_printk+0x0/0x12 returned 0 after 0 usecs
NMI watchdog: disabled (cpu0): hardware events not enabled
installing Xen timer for CPU 1
NMI watchdog: disabled (cpu1): hardware events not enabled
installing Xen timer for CPU 2
NMI watchdog: disabled (cpu2): hardware events not enabled
installing Xen timer for CPU 3
NMI watchdog: disabled (cpu3): hardware events not enabled
Brought up 4 CPUs
devtmpfs: initialized
calling  ipc_ns_init+0x0/0x14 @ 1
initcall ipc_ns_init+0x0/0x14 returned 0 after 0 usecs
calling  initea returned 0 after 0 usecs
calling  e820_mark_nvs_memory+0x0/0x41 @ 1
initcall e820_mark_nvs_memory+0x0/0x41 returned 0 after 0 usecs
calling  cpufreq_tsc+0x0/0x37 @ 1
initcall cpufreq_tsc+0x0/0x37 returned 0 after 0 usecs
calling  pci_reboot_init+0x0/0x1d @ 1
initcall pci_reboot_init+0x0/0x1d returned 0 after 0 usecs
calling  init_lapic_sysfs+0x0/0x20 @ 1
initcall init_lapic_sysfs+0x0/0x20 returned 0 after 0 usecs
calling  init_smp_flush+0x0/0x38 @ 1
initcall init_smp_flush+0x0/0x38 returned 0 after 0 usecs
calling  cpu_hotplug_pm_sync_init+0x0/0x2f @ 1
initcall cpu_hotplug_pm_sync_init+0x0/0x2f returned 0 after 0 usecs
calling  alloc_frozen_cpus+0x0/0x1e @ 1
initcall alloc_frozen_cpus+0x0/0x1e returned 0 after 0 usecs
calling  ksysfs_init+0x0/0x94 @ 1
initcall ksysfs_init+0x0/0x94 returned 0 after 0 usecs
calling  pm_init+0x0/0x66 @ 1
initcall pm_init+0x0/0x66 returned 0 after 0 usecs
calling  pm_disk_init+0x0/0x19 @ 1
initcall pm_disk_init+0x0/0x19 returned 0 after 0 usecs
calling  swsusp_header_init+0x0/0x40 @ 1
initcall swsusp_header_init+0x0/0x40 returned 0 after 0 usecs
calling  init_jiffies_clocksource+0x0/0x12 @ 1
initcall init_jiffies_clocksource+0x0/0x12 returned 0 after 0 usecs
calling  init_ftrace_syscalls+0x0/0x77 @ 1
initcall init_ftrace_syscalls+0x0/0x77 returned 0 after 976 usecs
calling  init_zero_pfn+0x0/0x35 @ 1
initcall init_zero_pfn+0x0/0x35 returned 0 after 0 usecs
calling  memory_failure_init+0x0/0xa8 @ 1
initcall memory_failure_init+0x0/0xa8 returned 0 after 0 usecs
calling  fsnotify_init+0x0/0x26 @ 1
initcall fsnotify_init+0x0/0x26 returned 0 after 0 usecs
calling  filelock_init+0x0/0x2a @ 1
initcall filelock_init+0x0/0x2a returned 0 after 0 usecs
calling  init_misc_binfmt+0x0/0x31 @ 1
initcall init_misc_binfmt+0x0/0x31 returned 0 after 0 usecs
calling  init_script_binfmt+0x0/0x16 @ 1
initcall init_script_binfmt+0x0/0x16 returned 0 after 0 usecs
calling  init_elf_binfmt+0x0/0x16 @ 1
initcall init_elf_binfmt+0x0/0x16 returned 0 after 0 usecs
calling  init_compat_elf_binfmt+0x0/0x16 @ 1
initcall init_compat_elf_binfmt+0x0/0x16 returned 0 after 0 usecs
calling  debugfs_init+0x0/0x5c @ 1
initcall debugfs_init+0x0/0x5c returned 0 after 0 usecs
calling  securityfs_init+0x0/0x53 @ 1
initcall securityfs_init+0x0/0x53 returned 0 after 0 usecs
calling  random32_init+0x0/0xdb @ 1
initcall random32_init+0x0/0xdb returned 0 after 0 usecs
calling  sfi_sysfs_init+0x0/0xdb @ 1
i usecs
calling  dma_bus_init+0x0/0x19 @ 1
initcall dma_bus_init+0x0/0x19 returned 0 after 0 usecs
calling  dma_channel_table_init+0x0/0x119 @ 1
initcall dma_channel_table_init+0x0/0x119 returned 0 after 0 usecs
calling  setup_vcpu_hotplug_event+0x0/0x22 @ 1
initcall setup_vcpu_hotplug_event+0x0/0x22 returned 0 after 0 usecs
calling  register_xen_pci_notifier+0x0/0x33 @ 1
initcall register_xen_pci_notifier+0x0/0x33 returned 0 after 0 usecs
calling  dmi_id_init+0x0/0xbe @ 1
initcall dmi_id_init+0x0/0xbe returned 0 after 0 usecs
calling  pci_arch_init+0x0/0x69 @ 1
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: Intel Corporation E7520 Memory Controller Hub with MMCONFIG support
PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
PCI: Using configuration type 1 for base access
initcall pci_arch_init+0x0/0x69 returned 0 after 76160 usecs
calling  topology_init+0x0/0xa1 @ 1
initcall topology_init+0x0/0xa1 returned 0 after 0 usecs
calling  mtrr_init_finialize+0x0/0x36 @ 1
initcall mtrr_init_finialize+0x0/0x36 returned 0 after 0 usecs
calling  init_vdso+0x0/0x135 @ 1
initcall init_vdso+0x0/0x135 returned 0 after 0 usecs
calling  sysenter_setup+0x0/0xbc @ 1
initcall sysenter_setup+0x0/0xbc returned 0 after 0 usecs
calling  param_sysfs_init+0x0/0x150 @ 1
initcall param_sysfs_init+0x0/0x150 returned 0 after 976 usecs
calling  pm_sysrq_init+0x0/0x20 @ 1
initcall pm_sysrq_init+0x0/0x20 returned 0 after 0 usecs
calling  default_bdi_init+0x0/0xaa @ 1
initcall default_bdi_init+0x0/0xaa returned 0 after 0 usecs
calling  init_bio+0x0/0x10c @ 1
bio: create slab <bio-0> at 0
initcall init_bio+0x0/0x10c returned 0 after 976 usecs
calling  fsnotify_notification_init+0x0/0x8b @ 1
initcall fsnotify_notification_init+0x0/0x8b returned 0 after 0 usecs
calling  cryptomgr_init+0x0/0x12 @ 1
initcall cryptomgr_init+0x0/0x12 returned 0 after 0 usecs
calling  blk_settings_init+0x0/0x2c @ 1
initcall blk_settings_init+0x0/0x2c returned 0 after 0 usecs
calling  blk_ioc_init+0x0/0x2a @ 1
initcall blk_ioc_init+0x0/0x2a returned 0 after 0 usecs
calling  blk_softirq_init+0x0/0x70 @ 1
initcall blk_softirq_init+0x0/0x70 returned 0 after 0 usecs
calling  blk_iopoll_setup+0x0/0x70 @ 1
initbridge window [mem 0xda4000000-0xde3ffffff]
pci_root PNP0A08:00: host bridge window [mem 0xd24000000-0xd63ffffff]
pci_root PNP0A08:00: host bridge window [mem 0xca4000000-0xce3ffffff]
pci_root PNP0A08:00: host bridge window [mem 0xc24000000-0xc63ffffff]
pci_root PNP0A08:00: host bridge window [mem 0xba4000000-0xbe3ffffff]
pci_root PNP0A08:00: host bridge window [mem 0xb24000000-0xb63ffffff]
pci_root PNP0A08:00: host bridge window [mem 0xaa4000000-0xae3ffffff]
pci_root PNP0A08:00: host bridge window [mem 0xa24000000-0xa63ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x9a4000000-0x9e3ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x924000000-0x963ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x8a4000000-0x8e3ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x824000000-0x863ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x7a4000000-0x7e3ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x724000000-0x763ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x6a4000000-0x6e3ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x624000000-0x663ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x5a4000000-0x5e3ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x524000000-0x563ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x4a4000000-0x4e3ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x424000000-0x463ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x3a4000000-0x3e3ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x324000000-0x363ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x2a4000000-0x2e3ffffff]
pci_root PNP0A08:00: host bridge window [mem 0x224000000-0x263ffffff]
pci_root PNP0A08:00: host bridge window [mem 0xd8000000-0xffffffff]
pci_root PNP0A08:00: host bridge window [mem 0x000c8000-0x000dffff]
pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bfffffff]
pci_bus 0000:00: root bus resource [mem 0x9a4000000-0x9e3ffffff]
0:03.0s 0000:00: root bus resource [mem 0x924000000-0x963ffffff]
pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
pci 0000:00:08.0: [8086:359b] type 00 class 0x088000
pci 0000:00:1c.0: [8086:25ae] type 01 class 0x060400
calling  pci_fixup_transparent_bridge+0x0/0x1d @ 1 for 0000:00:1c.0
pci fixup pci_fixup_transparent_bridge+0x0/0x1d returned after 0 usecs for 0000:00:1c.0
pci 0000:00:1d.0: [8086:25a9] type 00 class 0x0c0300
pci 0000:00:1d.0: reg 20: [io  0x2200-0x221f]
pci 0000:00:1d.1: [8086:25aa] type 00 class 0x0c0300
pci 0000:00:1d.1: reg 20: [io  0x2600-0x261f]
pci 0000:00:1d.4: [8086:25ab] type 00 class 0x088000
pci 0000:00:1d.4: reg 10: [mem 0x00000000-0x0000000f]
pci 0000:00:1d.5: [8086:25ac] type 00 class 0x080020
pci 0000:00:1e.0: [8086:244e] type 01 class 0x060400
calling  pci_fixup_transparent_bridge+0x0/0x1d @ 1 for 0000:00:1e.0
pci fixup pci_fixup_transparent_bridge+0x0/0x1d returned after 0 usecs for 0000:00:1e.0
pci 0000:00:1f.0: [8086:25a1] type 00 class 0x060100
calling  old_ich_force_enable_hpet_user+0x0/0x30 @ 1 for 0000:00:1f.0
pci fixup old_ich_force_enable_hpet_user+0x0/0x30 returned after 0 usecs for 0000:00:1f.0
calling  quirk_ich4_lpc_acpi+0x0/0xbc @ 1 for 0000:00:1f.0
pci fixup quirk_ich4_lpc_acpi+0x0/0xbc returned after 0 usecs for 0000:00:1f.0
pci 0000:00:1f.1: [8086:25a2] type 00 class 0x01018a
pci 0000:00:1f.1: reg 10: [io  0x0000-0x0007]
pci 0000:00:1f.1: reg 14: [io  0x0000-0x0003]
pci 0000:00:1f.1: reg 18: [io  0x0000-0x0007]
pci 0000:00:1f.1: reg 1c: [io  0x0000-0x0003]
pci 0000:00:1f.1: reg 20: [io  0x0000-0x000f]
pci 0000:00:1f.1: reg 24: [mem 0x00000000-0x000003ff]
pci 0000:00:1f.3: [8086:25a4] type 00 class 0x0c0500
pci 0000:00:1f.3: reg 20: [io  0x0440-0x045f]
pci 0000:04:00.0: [8086:0329] type 01 class 0x060400
calling  quirk_pcie_pxh+0x0/0x31 @ 1 for 0000:04:00.0
pci 0000:04:00.0: PXH quirk detected; SHPC device MSI disabled
pci fixup quirk_pcie_pxh+0x0/0x31 returned after 976 usecs for 0000:04:00.0
calling  pci_fixup_transparent_bridge+0x0/0x1d @ 1 for 0000:04:00.0
pci fixup pci_fixup_transparent_bridge+0x0/0x1d returned after 0 usecs for 0000:04:00.0
pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
pci 0000:04:00.2: [8086:032a] type 01 class 0x060400
calling  quirk_pcie_pxh+0x0/0x31 @ 1 for 0000:04:00.2
pci 0000:04:00.2: PXH quirk detected; SHPC device MSI disabled
pci fixup quirk_pcie_pxh+0x0/0x31 returned after 976 usecs for 0000:04:00.2
calling  pci_fixup_transparent_bridge+0x0/0x1d @ 1 for 0000:04:00.2
pci fixup pci_fixup_transparent_bridge+0x0/0x1d returned after 0 usecs for 0000:04:00.2
pci 0000:04:00.2: PME# supported from D0 D3hot D3cold
pci 0000:04:00.0: disabling ASPM on pre-1.1 PCIe device.  You can enable it with 'pcie_aspm=force'
pci 0000:00:03.0: PCI bridge to [bus 04-06]
pci 0000:00:03.0:   bridge window [io  0x5000-0xffff]
pci 0000:00:03.0:   bridge window [mem 0xdb000000-0xdcffffff]
pci 0000:04:00.0: PCI bridge to [bus 06-06]
pci 0000:04:00.0:   bridge window [io  0x5000-0xffff]
pci 0000:05:01.0: [14e4:16tive decode)
pci 0000:00:1e.0:   bridge window [mem 0xd24000000-0xd63ffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xca4000000-0xce3ffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xc24000000-0xc63ffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xba4000000-0xbe3ffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xb24000000-0xb63ffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xaa4000000-0xae3ffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xa24000000-0xa63ffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x9a4000000-0x9e3ffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x924000000-0x963ffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x8a4000000-0x8e3ffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x824000000-0x863ffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x7a40ow [mem 0x2a4000000-0x2e3ffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x224000000-0x263ffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xd8000000-0xffffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x0d00-0xffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x0000-0x0cf7] (subtractive decode)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1.PCI2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1.PCI3._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIS._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIX._PRT]
 pci0000:00: Requesting ACPI _OSC control (0x1d)
 pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
ACPI _OSC control for PCIe not granted, disabling ASPM
(XEN) PCI add device 0000:00:00.0
(XEN) PCI add device 0000:00:00.1
(XEN) PCI add device 0000:00:03.0
(XEN) PCI add device 0000:00:08.0
(XEN) PCI add device 0000:00:1c.0
(XEN) Platform timer appears to have unexpectedly wrapped 1 times.
(XEN) traps.c:486:d0 Unhandled nmi fault/trap [#2] on VCPU 0 [ec=0000]
(XEN) PCI add device 0000:00:1d.0
(XEN) PCI add device 0000:00:1d.1
(XEN) PCI add device 0000:00:1d.4
(XEN) PCI add device 0000:00:1d.5
(XEN) PCI add device 0000:00:1e.0
(XEN) PCI add device 0000:00:1f.0
(XEN) PCI add device 0000:00:1f.1
(XEN) PCI add device 0000:00:1f.3
(XEN) PCI add device 0000:04:00.0
(XEN) PCI add device 0000:04:00.2
(XEN) PCI add device 0000:05:01.0
(XEN) PCI add device 0000:05:01.1
(XEN) PCI add device 0000:02:01.0
(XEN) PCI add device 0000:01:01.0
initcall acpi_pci_root_init+0x0/0x32 returned 0 after 226527 usecs
calling  acpi_pci_link_init+0x0/0x43 @ 1
ACPI: PCI Interrupt Link [LP00] (IRQs *10)
ACPI: PCI Interrupt Link [LP01] (IRQs *7)
ACPI: PCI Interrupt Link [LP02] (IRQs *5)
ACPI: PCI Interrupt Link [LP03] (IRQs *5)
ACPI: PCI Interrupt Link [LP04] (IRQs *10)
ACPI: PCI Interrupt Link [LP05] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP06] (IRQs *10)
ACPI: PCI Interrupt Link [LP07] (IRQs) *0, disabled.
initcall acpi_pci_link_init+0x0/0x43 returned 0 after 0 usecs
calling  pnp_init+0x0/0x19 @ 1
initcall pnp_init+0x0/0x19 returned 0 after 0 usecs
calling  xen_setup_shutdown_event+0x0/0x30 @ 1
initcall xen_setup_shutdown_event+0x0/0x30 returned 0 after 0 usecs
calling  balloon_init+0x0/0x133 @ 1
xen/balloon: Initialising balloon driver.
initcall balloon_init+0x0/0x133 returned 0 after 0 usecs
calling  xenbus_probe_backend_init+0x0/0x5e @ 1
initcall xenbus_probe_backend_init+0x0/0x5e returned 0 after 0 usecs
calling  xenbus_probe_frontend_init+0x0/0x5e @ 1
initcall xenbus_probe_frontend_init+0x0/0x5e returned 0 after 0 usecs
calling  balloon_init+0x0/0x35 @ 1
xen-balloon: Initialising balloon driver.
initcall balloon_init+0x0/0x35 returned 0 after 0 usecs
calling  ab8500_regulator_init+0x0/0x31 @ 1
initcall ab8500_regulator_init+0x0/0x31 returned 0 after 0 usecs
calling  misc_init+0x0/0xba @ 1
initcall misc_init+0x0/0xba returned 0 after 0 usecs
calling  vga_arb_device_init+0x0/0xde @ 1
vgaarb: device added: PCI:0000:01:01.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
vgaarb: bridge control possible 0000:01:01.0
initcall vga_arb_device_init+0x0/0xde returned 0 after 0 usecs
calling  cn_init+0x0/0x9e @ 1
initcall cn_init+0x0/0x9e returned 0 after 0 usecs
calling  stmpe_init+0x0/0x14 @ 1
initcall stmpe_init+0x0/0x14 returned 0 after 0 usecs
calling  stmpe_init+0x0/0x12 @ 1
initcall stmpe_init+0x0/0x12 returned 0 after 0 usecs
calling  wm831x_spi_init+0x0/0x28 @ 1
initcall wm831x_spi_init+0x0/0x28 returned 0 after 0 usecs
calling  tps65912_spi_init+0x0/0x28 @ 1
initcall tps65912_spi_init+0x0/0x28 returned 0 after 0 usecs
calling  ezx_pcap_init+0x0/0x12 @ 1
initcall ezx_pcap_init+0x0/0x12 returned 0 after 0 usecs
calling  da9052_spi_init+0x0/0x31 @ 1
initcall da9052_spi_init+0x0/0x31 returned 0 after 0 usecs
calling  ab8500_sysctrl_init+0x0/0x12 @ 1
initcall ab8500_sysctrl_ini: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
reserve RAM buffer: 000000000009d000 - 000000000009ffff
reserve RAM buffer: 0000000010063000 - 0000000013ffffff
initcall pci_subsys_init+0x0/0x4f returned 0 after 0 usecs
calling  proto_init+0x0/0x12 @ 1
initcall proto_init+0x0/0x12 returned 0 after 0 usecs
calling  net_dev_init+0x0/0x1b3 @ 1
initcall net_dev_init+0x0/0x1b3 returned 0 after 0 usecs
calling  neigh_init+0x0/0x80 @ 1
initcall neigh_init+0x0/0x80 returned 0 after 0 usecs
calling  fib_rules_init+0x0/0xaf @ 1
initcall fib_rules_init+0x0/0xaf returned 0 after 0 usecs
calling  pktsched_init+0x0/0xfe @ 1
initcall pktsched_init+0x0/0xfe returned 0 after 0 usecs
calling  tc_filter_init+0x0/0x55 @ 1
initcall tc_filter_init+0x0/0x55 returned 0 after 0 usecs
calling  tc_action_init+0x0/0x55 @ 1
initcall tc_action_init+0x0/0x55 returned 0 after 0 usecs
calling  genl_init+0x0/0x84 @ 1
initcall genl_init+0x0/0x84 returned 0 after 0 usecs
calling  cipso_v4_init+0x0/0x61 @ 1
initcall cipso_v4_init+0x0/0x61 returned 0 after 0 usecs
calling  wireless_nlevent_init+0x0/0x12 @ 1
initcall wireless_nlevent_init+0x0/0x12 returned 0 after 0 usecs
calling  netlbl_init+0x0/0x81 @ 1
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
initcall netlbl_init+0x0/0x81 returned 0 after 0 usecs
calling  net_sysctl_init+0x0/0x49 @ 1
initcall net_sysctl_init+0x0/0x49 returned 0 after 0 usecs
calling  nfc_init+0x0/0x9e @ 1
nfc: nfc_init: NFC Core ver 0.1
NET: Registered protocol family 39
initcall nfc_init+0x0/0x9e returned 0 after 0 usecs
calling  ab8500_gpadc_init+0x0/0x12 @ 1
initcall ab8500_gpadc_init+0x0/0x12 returned 0 after 0 usecs
calling  ab8500_charger_init+0x0/0x12 @ 1
initcall ab8500_charger_init+0x0/0x12 returned 0 after 0 usecs
calling  ab8500_btemp_init+0x0/0x12 @ 1
initcall ab8500_btemp_init+0x0/0x12 returned 0 after 0 usecs
calling  ab8500_fg_init+0x0/0x12 @ 1
initcall ab8500_fg_init+0x0/0x12 returned 0 after 0 usecs
calling  xen_p2m_debugfs+0x0/0x4a @ 1
initcall xen_p2m_debugfs+0x0/0x4a returned 0 after 0 usecs
calling  hpet_late_init+0x0/0x103 @ 1
initcall hpet_late_init+0x0/0x103 returned -19 after 0 usecs
calling  init_amd_nbs+0x0/0x3f @ 1
initcall init_amd_nbs+0x0/0x3f returned 0 after 0 usecs
calling  clocksource_done_booting+0x0/0x5a @ 1
Switching to clocksource xen
initcall clocksource_done_booting+0x0/0x5a returned 0 after 8 usecs
calling  ftrace_init_debugfs+0x0/0xdx314 @ 1
initcall tracer_init_debugfs+0x0/0x314 returned 0 after 156 usecs
calling  init_trace_printk_function_export+0x0/0x2f @ 1
initcall init_trace_printk_function_export+0x0/0x2f returned 0 after 5 usecs
calling  event_trace_init+0x0/0x1bb @ 1
initcall event_trace_init+0x0/0x1bb returned 0 after 13106 usecs
calling  init_kprobe_trace+0x0/0x93 @ 1
initcall init_kprobe_trace+0x0/0x93 returned 0 after 7 usecs
calling  init_pipe_fs+0x0/0x4c @ 1
initcall init_pipe_fs+0x0/0x4c returned 0 after 30 usecs
calling  eventpoll_init+0x0/0xda @ 1
initcall eventpoll_init+0x0/0xda returned 0 after 106 usecs
calling  anon_inode_init+0x0/0x5b @ 1
initcall anon_inode_init+0x0/0x5b returned 0 after 17 usecs
calling  tomoyo_initerface_init+0x0/0x17d @ 1
initcall tomoyo_initerface_init+0x0/0x17d returned 0 after 0 usecs
calling  blk_scsi_ioctl_init+0x0/0x289 @ 1
initcall blk_scsi_ioctl_init+0x0/0x289 returned 0 after 0 usecs
calling  acpi_event_init+0x0/0x81 @ 1
initcall acpi_event_init+0x0/0x81 returned 0 after 18 usecs
calling  pnp_system_init+0x0/0x12 @ 1
initcall pnp_system_init+0x0/0x12 returned 0 after 24 usecs
calling  pnpacpi_init+0x0/0x8c @ 1
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp 00:00: [mem 0xf24000000-0xfffffffff window]
pnp 00:00: [mem 0xea4000000-0xee3ffffff window]
pnp 00:00: [mem 0xe24000000-0xe63ffffff window]
pnp 00:00: [mem 0xda4000000-0xde3ffffff window]
pnp 00:00: [mem 0xd24000000-0xd63ffffff window]
pnp 00:00: [mem 0xca4000000-0xce3ffffff window]
pnp 00:00: [mem 0xc24000000-0xc63ffffff window]
pnp 00:00: [mem 0xba4000000-0xbe3ffsign_resources+0x0/0xf8 @ 1
pci 0000:00:1c.0: BAR 15: assigned [mem 0xd8000000-0xd80fffff pref]
pci 0000:00:1f.1: BAR 5: assigned [mem 0xd8100000-0xd81003ff]
pci 0000:00:1d.4: BAR 0: assigned [mem 0xd8100400-0xd810040f]
pci 0000:00:1f.1: BAR 4: assigned [io  0x1000-0x100f]
pci 0000:04:00.0: PCI bridge to [bus 06-06]
pci 0000:04:00.0:   bridge window [io  0x5000-0xffff]
pci 0000:04:00.2: PCI bridge to [bus 05-05]
pci 0000:04:00.2:   bridge window [mem 0xdb000000-0xdcffffff]
pci 0000:00:03.0: PCI bridge to [bus 04-06]
pci 0000:00:03.0:   bridge window [io  0x5000-0xffff]
pci 0000:00:03.0:   bridge window [mem 0xdb000000-0xdcffffff]
pci 0000:02:01.0: BAR 6: assigned [mem 0xd8000000-0xd80fffff pref]
pci 0000:00:1c.0: PCI bridge to [bus 02-02]
pci 0000:00:1c.0:   bridge window [io  0x4000-0x4fff]
pci 0000:00:1c.0:   bridge window [mem 0xdd000000-0xdeffffff]
pci 0000:00:1c.0:   bridge window [mem 0xd8000000-0xd80fffff pref]
pci 0000:01:01.0: BAR 6: assigned [mem 0xf8020000-0xf803ffff pref]
pci 0000:00:1e.0: PCI bridge to [bus 01-01]
pci 0000:00:1e.0:   bridge window [io  0x3000-0x3fff]
pci 0000:00:1e.0:   bridge window [mem 0xf8000000-0xf8ffffff]
pci 0000:00:1e.0:   bridge window [mem 0xf0000000-0xf7ffffff pref]
xen: registering gsi 16 triggering 0 pole 0 [io  0x5000-0xffff]
pci_bus 0000:04: resource 1 [mem 0xdb000000-0xdcffffff]
pci_bus 0000:06: resource 0 [io  0x5000-0xffff]
pci_bus 0000:05: resource 1 [mem 0xdb000000-0xdcffffff]
pci_bus 0000:02: resource 0 [io  0x4000-0x4fff]
pci_bus 0000:02: resource 1 [mem 0xdd000000-0xdeffffff]
pci_bus 0000:02: resource 2 [mem 0xd8000000-0xd80fffff pref]
pci_bus 0000:01: resource 0 [io  0x3000-0x3fff]
pci_bus 0000:01: resource 1 [mem 0xf8000000-0xf8ffffff]
pci_bus 0000:01: resource 2 [mem 0xf0000000-0xf7ffffff pref]
pci_bus 0000:01: resource 4 [mem 0xf24000000-0xfffffffff]
pci_bus 0000:01: resource 5 [mem 0xea4000000-0xee3ffffff]
pci_bus 0000:01: resource 6 [mem 0xe24000000-0xe63ffffff]
pci_bus 0000:01: resource 7 [mem 0xda4000000-0xde3ffffff]
pci_bus 0000:01: resource 8 [mem 0xd24000000-0xd63ffffff]
pci_bus 0000:01: resource 9 [mem 0xca4000000-0xce3ffffff]
pci_bus 0000:01: resource 10 [mem 0xc24000000-0xc63ffffff]
pci_bus 0000:01: resource 11 [mem 0xba4000000-0xbe3ffffff]
pci_bus 0000:01: resource 12 [mem 0xb24000000-0xb63ffffff]
pci_bus 0000:01: resource 13 [mem 0xaa4000000-0xae3ffffff]
pci_bus 0000:01: resource 14 [mem 0xa24000000-0xa63ffffff]
pci_bus 0000:01: resource 15 [mem 0x9a4000000-0x9e3ffffff]
pci_bus 0000:01: resource 16 [mem 0x924000000-0x963ffffff]
pci_bus 0000:01: resource 17 [mem 0x8a4000000-0x8e3ffffff]
pci_bus 0000:01: resource 18 [mem 0x824000000-0x863ffffff]
pci_bus 0000:01: resource 19 [mem 0x7a4000000-0x7e3ffffff]
pci_bus 0000:01: resource 20 [mem 0x724000000-0x763ffffff]
pci_bus 0000:01: resource 21 [mem 0x6a4000000-0x6e3ffffff]
pci_bus 0000:01: resource 22 [mem 0x624000000-0x663ffffff]
pci_bus 0000:01: resource 23 [mem 0x5a4000000-0x5e3ffffff]
pci_bus 0000:01: resource 24 [mem 0x524000000-0x563ffffff]
pci_bus 0000:01: resource 25 [mem 0x4a4000000-0x4e3ffffff]
pci_bus 0000:0?[2J



-- Pasi

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[Jan Beulich]

>>> On 05.02.13 at 21:08, Pasi Kärkkäinen<pasik@iki.fi> wrote:
> 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, earlier
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 event
that Xen has no control over.

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[Pasi Kärkkäinen]

On Wed, Feb 06, 2013 at 07:58:56AM +0000, Jan Beulich wrote:
> >>> On 05.02.13 at 21:08, Pasi Kärkkäinen<pasik@iki.fi> wrote:
> > 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, earlier
> 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 event
> 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 not 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 further analysis? 

-- Pasi

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[Jan Beulich]

>>> On 06.02.13 at 12:29, Pasi Kärkkäinen<pasik@iki.fi> wrote:
> On Wed, Feb 06, 2013 at 07:58:56AM +0000, Jan Beulich wrote:
>> >>> On 05.02.13 at 21:08, Pasi Kärkkäinen<pasik@iki.fi> wrote:
>> > 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, earlier
>> 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 event
>> 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 not 
> 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.

Even with the IOMMU fully enabled?

> Do you have any Xen and/or dom0 kernel options to use to do further 
> analysis? 

I don't recall if sync_console was used - if not, it should be.

And of course the inverse of the above - turning the IOMMU off -
should be tried in Xen.

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[agya naila]

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

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, its in french
but we can translate it easily using google
http://debian.2.n7.nabble.com/Probleme-XEN-4-0-1-et-SQUEEZE-64bits-reboot-td1230690.html

I found parameter nmi=ignore | dom0 | fatal

nmi=reaction : 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.

Agya


On Wed, Feb 6, 2013 at 12:29 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:

> On Wed, Feb 06, 2013 at 07:58:56AM +0000, Jan Beulich wrote:
> > >>> On 05.02.13 at 21:08, Pasi Kärkkäinen<pasik@iki.fi> wrote:
> > > 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, earlier
> > 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 event
> > 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 not
> 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 further
> analysis?
>
> -- Pasi
>
>

[-- Attachment #1.2: Type: text/html, Size: 3127 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[agya naila]

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

As I read on IBM paper :

When a non-maskable interrupt (NMI) signal is received, the processor
immediately drops what it was doing and attends to it. The NMI signal is
normally used only for critical problem situations, such as serious
hardware errors This setting is Enabled by default. When an NMI is issued
by a critical event the BMC performs the system to reset for recovering the
system. The BMC logs the reboot and additional error events in the SEL.

I dont know why XEN trigger or cause this NMI signal, since when I boot the
machine with the same Operating system Ubuntu 12.04.1 Desktop 64 bit
without XEN its run perfectly. One more interesting fact with the same Dom0
with excacly the same XEN version and configuration running perfectly on my
notebook Toshiba Satelite L735 Intel I5, Hopefully anyone have solution for
the server.

Agya

On Wed, Feb 6, 2013 at 12:48 PM, agya naila <agya.naila@gmail.com> 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, its in
> french but we can translate it easily using google
> http://debian.2.n7.nabble.com/Probleme-XEN-4-0-1-et-SQUEEZE-64bits-reboot-td1230690.html
>
> I found parameter nmi=ignore | dom0 | fatal
>
> nmi=reaction : 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.
>
> Agya
>
>
> On Wed, Feb 6, 2013 at 12:29 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
>
>> On Wed, Feb 06, 2013 at 07:58:56AM +0000, Jan Beulich wrote:
>> > >>> On 05.02.13 at 21:08, Pasi Kärkkäinen<pasik@iki.fi> wrote:
>> > > 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, earlier
>> > 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 event
>> > 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 not
>> 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 further
>> analysis?
>>
>> -- Pasi
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 4490 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[Pasi Kärkkäinen]

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, its 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=ignore | dom0 | fatal
>    nmi=reaction : 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=ignore" for xen.gz in grub settings and it didn't help? 
Did you try the other possible values? 

-- Pasi

>    Agya
>    On Wed, Feb 6, 2013 at 12:29 PM, Pasi Kärkkäinen <[2]pasik@iki.fi> wrote:
> 
>      On Wed, Feb 06, 2013 at 07:58:56AM +0000, Jan Beulich wrote:
>      > >>> On 05.02.13 at 21:08, Pasi Kärkkäinen<[3]pasik@iki.fi> wrote:
>      > > 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, earlier
>      > 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 event
>      > 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 not
>      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 further
>      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

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[agya naila]

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

I configure it by added nmi=ignore 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='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set=root
730a0f5f-4c35-4391-b760-0b6cf0cdd6a7
        echo    'Loading Xen 4.1-amd64 ...'
        multiboot       /boot/xen-4.1-amd64.gz placeholder noreboot
dom0_mem=1024M nmi=ignore
        echo    'Loading Linux 3.2.0-29-generic ...'
        module  /boot/vmlinuz-3.2.0-29-generic placeholder
root=UUID=730a0f5f-4c35-4391-b760-0b6cf0cdd6a7 ro rootdelay=180 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ärkkäinen <pasik@iki.fi> 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, its
> 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=ignore | dom0 | fatal
> >    nmi=reaction : 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=ignore" for xen.gz in grub settings and it didn't
> help?
> Did you try the other possible values?
>
> -- Pasi
>
> >    Agya
> >    On Wed, Feb 6, 2013 at 12:29 PM, Pasi Kärkkäinen <[2]pasik@iki.fi>
> wrote:
> >
> >      On Wed, Feb 06, 2013 at 07:58:56AM +0000, Jan Beulich wrote:
> >      > >>> On 05.02.13 at 21:08, Pasi Kärkkäinen<[3]pasik@iki.fi> wrote:
> >      > > 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, earlier
> >      > 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 event
> >      > 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 not
> >      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 further
> >      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
>

[-- Attachment #1.2: Type: text/html, Size: 5502 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[Fabian Arrotin]

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

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[agya naila]

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

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.

Agya

On Thu, Feb 7, 2013 at 9:51 PM, Fabian Arrotin <arrfab@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
>

[-- Attachment #1.2: Type: text/html, Size: 1172 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[Pasi Kärkkäinen]

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]arrfab@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:arrfab@centos.org

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[Trenta sis]

[-- 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

IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[Trenta sis]

[-- Attachment #1.1: Type: text/plain, Size: 1571 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: 2221 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[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.

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[Trenta sis]

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

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?

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: 1665 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[Konrad Rzeszutek Wilk]

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.
> >

Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash

[Trenta sis]

[-- 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