WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] current xen/stable 2.6.32.9 failed upgrade from 2.6.31.6

To: Josip Rodin <joy@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] current xen/stable 2.6.32.9 failed upgrade from 2.6.31.6
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Fri, 12 Mar 2010 15:02:07 +0200
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 12 Mar 2010 05:02:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100312114139.GA4067@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20100306115833.GA28039@xxxxxxxxxxxxxxx> <20100306132711.GK2580@xxxxxxxxxxx> <20100307233147.GA20068@xxxxxxxxxxxxxxx> <20100311150823.GA9011@xxxxxxxxxxxxxxx> <20100311192456.GY1878@xxxxxxxxxxx> <20100312114139.GA4067@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Fri, Mar 12, 2010 at 12:41:39PM +0100, Josip Rodin wrote:
> On Thu, Mar 11, 2010 at 09:24:56PM +0200, Pasi Kärkkäinen wrote:
> > > Sadly, it looks this iLO VSP is completely useless, because when I defined
> > > com1, the hypervisor started *not* displaying anything on the physical
> > > console or the virtual serial port.
> > > Maybe I'm missing something regarding the iLO VSP setup on this HP 
> > > DL380...
> > 
> > If you boot baremetal (non-Xen) Linux, on what IO-port and IRQ is the iLO
> > serial port?
> > 
> > Is it on the standard IO-port/IRQ, or some non-standard? In this case you
> > might have to specify the IOport on the xen cmdline options in grub.conf.
> > 
> > See also:
> > http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00263709/c00263709.pdf
> 
> Oh, thanks, that was useful. The manual actually documents that VSP is on
> COM *2*, not 1, and despite my prior ample negative experience with the
> off-by-one in port numbering, and the fact I had even used ttyS1=COM2 on
> this exact machine, I managed to screw that one up. Sorry for the noise.
> 
> So, I managed to get GRUB, the hypervisor and dom0 to display messages on
> VSP. (No luck yet with BIOS POST, but that is irrelevant for now.)
> 
> I'll first paste the few odd bits of log from the *working* 2.6.31.6 dom0,
> just to set up a possible baseline:
> 

<snip>

> 
> Everything else seems normal, and indeed the machine has worked normally
> in this setup for a few months.
> 
> And now here goes the whole output preceding the 2.6.32 crash:
>

<snip>

> 
> [    0.000000] ACPI: PM-Timer IO Port: 0x908
> [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
> [    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
> [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
> (XEN) mm.c:720:d0 Bad L1 flags 800000
> (XEN) mm.c:4221:d0 ptwr_emulate: could not get_page_from_l1e()
> (XEN) d0:v0: unhandled page fault (ec=0003)
> (XEN) Pagetable walk from ffff8800014fdfd8:
> (XEN)  L4[0x110] = 0000000115002067 0000000000001002
> (XEN)  L3[0x000] = 0000000115006067 0000000000001006
> (XEN)  L2[0x00a] = 0000000116c8a067 0000000000002c8a 
> (XEN)  L1[0x0fd] = 00100001154fd065 00000000000014fd
> (XEN) domain_crash_sync called from entry.S
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) ----[ Xen-3.4  x86_64  debug=n  Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    e033:[<ffffffff8100d9df>]
> (XEN) RFLAGS: 0000000000000246   EM: 1   CONTEXT: pv guest
> (XEN) rax: 0000000000000000   rbx: 80000001154fc163   rcx: 00000000014fd000
> (XEN) rdx: 0000000000000000   rsi: 80000001154fc163   rdi: ffff8800014fdfd8
> (XEN) rbp: ffff8800014fdfd8   rsp: ffffffff813abd70   r8:  0000000000000002
> (XEN) r9:  ffffffff8146a060   r10: ffffffff8100b6a3   r11: ffffffff8146a060
> (XEN) r12: 80000001154fc163   r13: 0000000000000000   r14: ffffffffff4002c2
> (XEN) r15: ffffffff8147cbb0   cr0: 000000008005003b   cr4: 00000000000006f0
> (XEN) cr3: 0000000115001000   cr2: ffff8800014fdfd8
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
> (XEN) Guest stack trace from rsp=ffffffff813abd70:
> (XEN)    00000000014fd000 ffffffff8146a060 0000000000000003 ffffffff8100d9df
> (XEN)    000000010000e030 0000000000010046 ffffffff813abdb8 000000000000e02b
> (XEN)    ffffffff8100d9df ffffffffff5fb000 ffffffffff5fb000 0000000000000804
> (XEN)    ffffffff81025db1 0000000115003067 80000001154fc163 ffffffff81001000
> (XEN)    80000001154fc163 0000000000000008 ffffffff81029e63 0000000000000000
> (XEN)    ffffffff8100c40d ffffffff813abe88 0000000000000000 0000000000000000
> (XEN)    ffffffff814816a0 ffffffff8147cbb0 ffffffffff40026c ffffffffff40026c
> (XEN)    0000000000000080 ffffffff81336a73 ffffffff8147cbdc 0000000000000001
> (XEN)    ffffffff814925aa 00000001813abf78 00000000000000c2 ffffffffff400200
> (XEN)    0000000000000000 0000000000000000 ffffffffffffffff ffffffff813abf78
> (XEN)    0000000000000000 0000000000000000 ffffffff8147d220 ffffffff813abf78
> (XEN)    0000000001580600 0000000020000000 ffffffff81477685 ffffffff8100db3d
> (XEN)    0000000002b7b600 00000000015fb000 0000000002b7b600 ffffffff8133b055
> (XEN)    ffffffff8133fb05 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 ffffffffffffffff ffffffff814a2090
> (XEN)    0000000000000000 0000000000000000 ffffffff8147297d 00000000015dadd4
> (XEN)    0000000000000000 ffffffff814a3fc0 ffffffff81001000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 ffffffff81475686 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000001
> (XEN) Domain 0 crashed: 'noreboot' set - not rebooting.
> 
> In the meantime there was another update to the stable branch, I'll go
> compile that...
> 

This is a known problem.. I see it also on my old 32bit testbox.
64bit dom0 kernel works for me.

Jeremy has some ideas about what might be causing this..

-- Pasi


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel