thr3ads.net - Xen devel - [Xen-devel] Current xen-unstable xen crashing in boot [Aug 2009]

If this information is useful, please help other people find it:
Share via:

Jeremy Fitzhardinge

2009-Aug-14 19:19 UTC

[Xen-devel] Current xen-unstable xen crashing in boot

I updated from hg today, and xen is crashing fairly early.  I haven''t
tried bisecting yet, but the last
working version was a week or two ago.

          _____  ____                     _        _     _      
 \ \/ /___ _ __   |___ / | ___|    _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ ''_ \    |_ \ |___ \ __| | | | ''_ \/ __| __/ _` |
''_ \| |/ _ \
  /  \  __/ | | |  ___) | ___) |__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_| |____(_)____/    \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                         
(XEN) Xen version 3.5-unstable (jeremy@eng.hq.xensource.com) (gcc version 4.4.0
20090506 (Red Hat 4.4.0-4) (GCC) ) Fri Aug 14 10:48:57 PDT 2009
(XEN) Latest ChangeSet: Fri Aug 14 17:26:23 2009 +0100 20067:5619bed51ec4
(XEN) Command line: loglvl=all guest_loglvl=all com1=115200,8n1 console=com1
noreboot dom0_mem=768m
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 2 seconds
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 00000000000a0000 (usable)
(XEN)  0000000000100000 - 000000007ffc0000 (usable)
(XEN)  000000007ffc0000 - 000000007ffcfc00 (ACPI data)
(XEN)  000000007ffcfc00 - 000000007ffff000 (reserved)
(XEN)  00000000e0000000 - 00000000fec90000 (reserved)
(XEN)  00000000fed00000 - 00000000fed00400 (reserved)
(XEN)  00000000fee00000 - 00000000fee10000 (reserved)
(XEN)  00000000ffb00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2047MB (2096512kB)
(XEN) ACPI: RSDP 000FD650, 0014 (r0 DELL  )
(XEN) ACPI: RSDT 000FD664, 0038 (r1 DELL   PE BKC          1 MSFT  100000A)
(XEN) ACPI: FACP 000FD6B0, 0074 (r1 DELL   PE BKC          1 MSFT  100000A)
(XEN) ACPI: DSDT 7FFC0000, 388D (r1 DELL   PE BKC          1 MSFT  100000E)
(XEN) ACPI: FACS 7FFCFC00, 0040
(XEN) ACPI: APIC 000FD724, 009C (r1 DELL   PE BKC          1 MSFT  100000A)
(XEN) ACPI: SPCR 000FD7CC, 0050 (r1 DELL   PE BKC          1 MSFT  100000A)
(XEN) ACPI: HPET 000FD81C, 0038 (r1 DELL   PE BKC          1 MSFT  100000A)
(XEN) ACPI: MCFG 000FD854, 003C (r1 DELL   PE BKC          1 MSFT  100000A)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000007ffc0000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000fe710
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x808
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
(XEN) ACPI:                  wakeup_vec[7ffcfc0c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 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[0x06] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x03] address[0xfec80000] gsi_base[32])
(XEN) IOAPIC[1]: apic_id 3, version 32, address 0xfec80000, GSI 32-55
(XEN) ACPI: IOAPIC (id[0x04] address[0xfec83000] gsi_base[64])
(XEN) IOAPIC[2]: apic_id 4, version 32, address 0xfec83000, GSI 64-87
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 3 I/O APICs
(XEN) ACPI: HPET id: 0xffffffff base: 0xfed00000
(XEN) PCI: Found Intel Corporation E7520 Memory Controller Hub with MMCONFIG
support.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Early fatal page fault at e008:ffff828c8015415c (cr2=ffff83007fc75008,
ec=0000)
(XEN) Stack dump: 000000000007fc76 000000000000000c ffff83007fc77ff0
ffff83007fc76000 ffff828c8026fe58 0000000000000262 0000000000000020
0180000000000000 000000000000010c ffff828c802a6380 ffff83007fc75008
0000000000000001 ffff830000000000 ffff828c80219b0c ffff83007fc76000
0000000000000000 ffff828c8015415c 000000000000e008 0000000000010082
ffff828c8026fdd8 0000000000000000 ffff828c80154158 ffff828c8026fde8
0000000000000262 00000000000002e2 0000000000000086 0000000000000262
0000000000000000 000000008026fe18 ffff83007fc75008 ffff828c00000027
ffff83007fc76000 ffff828c8021dd60 0000000000000002 000000007fc42000
ffff83000008bfc0 ffff83000008bf40 0000000000002000 ffff828c8026fe68
ffff828c80154f85 ffff828c8026fe78 ffff828c80154fa5 ffff828c8026ff18
ffff828c802343ef 0000000000000000 0000000000000000 0000000000a1e000
0000000000aca3e0 ffff83000008bf40 0000000000000000 00000000ffffffff
ffff83000000000c 0000000800000000 000000010000006e 0000000000000003
00000000000002f8 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000067e8c
ffff828c801000b5 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 00000000fffff000

This appears to be:
(gdb) x/i 0xffff828c8015415c 
0xffff828c8015415c <map_pages_to_xen+112>:	mov    (%rax),%rax
(gdb) x/i 0xffff828c80154f85 
0xffff828c80154f85 <__memguard_change_range+237>:	leaveq 

but I can''t find a good enclosing frame from there (is there a tool to
pretty-print these stack traces?).

	J



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

Jeremy Fitzhardinge

2009-Aug-14 20:48 UTC

head link

Re: [Xen-devel] Current xen-unstable xen crashing in boot

On 08/14/09 12:19, Jeremy Fitzhardinge wrote:> I updated from hg today, and xen is crashing fairly early.  I
haven''t tried bisecting yet, but the last
> working version was a week or two ago.
>
>           _____  ____                     _        _     _      
>  \ \/ /___ _ __   |___ / | ___|    _   _ _ __  ___| |_ __ _| |__ | | ___ 
>   \  // _ \ ''_ \    |_ \ |___ \ __| | | | ''_ \/ __| __/
_` | ''_ \| |/ _ \
>   /  \  __/ | | |  ___) | ___) |__| |_| | | | \__ \ || (_| | |_) | |  __/
>  /_/\_\___|_| |_| |____(_)____/    \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
>                                                                          
> (XEN) Xen version 3.5-unstable (jeremy@eng.hq.xensource.com) (gcc version
4.4.0 20090506 (Red Hat 4.4.0-4) (GCC) ) Fri Aug 14 10:48:57 PDT 2009
> (XEN) Latest ChangeSet: Fri Aug 14 17:26:23 2009 +0100 20067:5619bed51ec4
> (XEN) Command line: loglvl=all guest_loglvl=all com1=115200,8n1
console=com1 noreboot dom0_mem=768m
> (XEN) Video information:
> (XEN)  VGA is text mode 80x25, font 8x16
> (XEN)  VBE/DDC methods: V2; EDID transfer time: 2 seconds
> (XEN) Disc information:
> (XEN)  Found 1 MBR signatures
> (XEN)  Found 1 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 00000000000a0000 (usable)
> (XEN)  0000000000100000 - 000000007ffc0000 (usable)
> (XEN)  000000007ffc0000 - 000000007ffcfc00 (ACPI data)
> (XEN)  000000007ffcfc00 - 000000007ffff000 (reserved)
> (XEN)  00000000e0000000 - 00000000fec90000 (reserved)
> (XEN)  00000000fed00000 - 00000000fed00400 (reserved)
> (XEN)  00000000fee00000 - 00000000fee10000 (reserved)
> (XEN)  00000000ffb00000 - 0000000100000000 (reserved)
> (XEN) System RAM: 2047MB (2096512kB)
> (XEN) ACPI: RSDP 000FD650, 0014 (r0 DELL  )
> (XEN) ACPI: RSDT 000FD664, 0038 (r1 DELL   PE BKC          1 MSFT  100000A)
> (XEN) ACPI: FACP 000FD6B0, 0074 (r1 DELL   PE BKC          1 MSFT  100000A)
> (XEN) ACPI: DSDT 7FFC0000, 388D (r1 DELL   PE BKC          1 MSFT  100000E)
> (XEN) ACPI: FACS 7FFCFC00, 0040
> (XEN) ACPI: APIC 000FD724, 009C (r1 DELL   PE BKC          1 MSFT  100000A)
> (XEN) ACPI: SPCR 000FD7CC, 0050 (r1 DELL   PE BKC          1 MSFT  100000A)
> (XEN) ACPI: HPET 000FD81C, 0038 (r1 DELL   PE BKC          1 MSFT  100000A)
> (XEN) ACPI: MCFG 000FD854, 003C (r1 DELL   PE BKC          1 MSFT  100000A)
> (XEN) NUMA turned off
> (XEN) Faking a node at 0000000000000000-000000007ffc0000
> (XEN) Domain heap initialised
> (XEN) found SMP MP-table at 000fe710
> (XEN) DMI 2.3 present.
> (XEN) Using APIC driver default
> (XEN) ACPI: PM-Timer IO Port: 0x808
> (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
> (XEN) ACPI:                  wakeup_vec[7ffcfc0c], vec_size[20]
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> (XEN) Processor #0 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[0x06] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
> (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
> (XEN) ACPI: IOAPIC (id[0x03] address[0xfec80000] gsi_base[32])
> (XEN) IOAPIC[1]: apic_id 3, version 32, address 0xfec80000, GSI 32-55
> (XEN) ACPI: IOAPIC (id[0x04] address[0xfec83000] gsi_base[64])
> (XEN) IOAPIC[2]: apic_id 4, version 32, address 0xfec83000, GSI 64-87
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> (XEN) ACPI: IRQ0 used by override.
> (XEN) ACPI: IRQ2 used by override.
> (XEN) ACPI: IRQ9 used by override.
> (XEN) Enabling APIC mode:  Flat.  Using 3 I/O APICs
> (XEN) ACPI: HPET id: 0xffffffff base: 0xfed00000
> (XEN) PCI: Found Intel Corporation E7520 Memory Controller Hub with
MMCONFIG support.
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) Early fatal page fault at e008:ffff828c8015415c
(cr2=ffff83007fc75008, ec=0000)
> (XEN) Stack dump: 000000000007fc76 000000000000000c ffff83007fc77ff0
ffff83007fc76000 ffff828c8026fe58 0000000000000262 0000000000000020
0180000000000000 000000000000010c ffff828c802a6380 ffff83007fc75008
0000000000000001 ffff830000000000 ffff828c80219b0c ffff83007fc76000
0000000000000000 ffff828c8015415c 000000000000e008 0000000000010082
ffff828c8026fdd8 0000000000000000 ffff828c80154158 ffff828c8026fde8
0000000000000262 00000000000002e2 0000000000000086 0000000000000262
0000000000000000 000000008026fe18 ffff83007fc75008 ffff828c00000027
ffff83007fc76000 ffff828c8021dd60 0000000000000002 000000007fc42000
ffff83000008bfc0 ffff83000008bf40 0000000000002000 ffff828c8026fe68
ffff828c80154f85 ffff828c8026fe78 ffff828c80154fa5 ffff828c8026ff18
ffff828c802343ef 0000000000000000 0000000000000000 0000000000a1e000
0000000000aca3e0 ffff83000008bf40 0000000000000000 00000000ffffffff
ffff83000000000c 0000000800000000 000000010000006e 0000000000000003
00000000000002f8 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000067e8c
ffff828c801000b5 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 00000000fffff000
>
> This appears to be:
> (gdb) x/i 0xffff828c8015415c 
> 0xffff828c8015415c <map_pages_to_xen+112>:	mov    (%rax),%rax
> (gdb) x/i 0xffff828c80154f85 
> 0xffff828c80154f85 <__memguard_change_range+237>:	leaveq 
>
> but I can''t find a good enclosing frame from there (is there a
tool to pretty-print these stack traces?).
>   
I bisected it down to:

The first bad revision is:
changeset:   20038:1197585e32b7
user:        Keir Fraser <keir.fraser@citrix.com>
date:        Fri Aug 07 17:29:50 2009 +0100
summary:     x86: Increase default max CPUs to 64.

    J


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

Jeremy Fitzhardinge

2009-Aug-14 21:02 UTC

head link

Re: [Xen-devel] Current xen-unstable xen crashing in boot

On 08/14/09 13:48, Jeremy Fitzhardinge wrote:>> (XEN) Early fatal page fault at e008:ffff828c8015415c
(cr2=ffff83007fc75008, ec=0000)
>> (XEN) Stack dump: 000000000007fc76 000000000000000c ffff83007fc77ff0
ffff83007fc76000 ffff828c8026fe58 0000000000000262 0000000000000020
0180000000000000 000000000000010c ffff828c802a6380 ffff83007fc75008
0000000000000001 ffff830000000000 ffff828c80219b0c ffff83007fc76000
0000000000000000 ffff828c8015415c 000000000000e008 0000000000010082
ffff828c8026fdd8 0000000000000000 ffff828c80154158 ffff828c8026fde8
0000000000000262 00000000000002e2 0000000000000086 0000000000000262
0000000000000000 000000008026fe18 ffff83007fc75008 ffff828c00000027
ffff83007fc76000 ffff828c8021dd60 0000000000000002 000000007fc42000
ffff83000008bfc0 ffff83000008bf40 0000000000002000 ffff828c8026fe68
ffff828c80154f85 ffff828c8026fe78 ffff828c80154fa5 ffff828c8026ff18
ffff828c802343ef 0000000000000000 0000000000000000 0000000000a1e000
0000000000aca3e0 ffff83000008bf40 0000000000000000 00000000ffffffff
ffff83000000000c 0000000800000000 000000010000006e 0000000000000003
00000000000002f8 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000067e8c
ffff828c801000b5 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 00000000fffff000
>>
>> This appears to be:
>> (gdb) x/i 0xffff828c8015415c 
>> 0xffff828c8015415c <map_pages_to_xen+112>:	mov    (%rax),%rax
>> (gdb) x/i 0xffff828c80154f85 
>> 0xffff828c80154f85 <__memguard_change_range+237>:	leaveq 
>>
>> but I can''t find a good enclosing frame from there (is there a
tool to pretty-print these stack traces?).
>>   
>>     
>
> I bisected it down to:
>
> The first bad revision is:
> changeset:   20038:1197585e32b7
> user:        Keir Fraser <keir.fraser@citrix.com>
> date:        Fri Aug 07 17:29:50 2009 +0100
> summary:     x86: Increase default max CPUs to 64.
>   
Reverting this change on current tip works fine for me.

    J


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

Keir Fraser

2009-Aug-15 06:33 UTC

head link

Re: [Xen-devel] Current xen-unstable xen crashing in boot

On 14/08/2009 22:02, "Jeremy Fitzhardinge" <jeremy@goop.org>
wrote:
>> I bisected it down to:
>> 
>> The first bad revision is:
>> changeset:   20038:1197585e32b7
>> user:        Keir Fraser <keir.fraser@citrix.com>
>> date:        Fri Aug 07 17:29:50 2009 +0100
>> summary:     x86: Increase default max CPUs to 64.
> 
> Reverting this change on current tip works fine for me.
We''ll have to see if we can reproduce the bug.

 Thanks,
 Keir



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

Wei, Gang

2009-Aug-15 12:03 UTC

head link

RE: [Xen-devel] Current xen-unstable xen crashing in boot

I used to meet similar problem before I do a clean build. The
xen/arch/x86/xen.lds could not be regenerated without a clean build, which would
cause __per_cpu_end still equal __per_cpu_start + (32 << 13).

Please confirm it is not caused by this factor.

Jimmy

Jeremy Fitzhardinge wrote:> On 08/14/09 13:48, Jeremy Fitzhardinge wrote:
>>> (XEN) Early fatal page fault at e008:ffff828c8015415c
> (cr2=ffff83007fc75008, ec=0000)
>>> (XEN) Stack dump: 000000000007fc76 000000000000000c
> ffff83007fc77ff0 ffff83007fc76000 ffff828c8026fe58
> 0000000000000262 0000000000000020 0180000000000000
> 000000000000010c ffff828c802a6380 ffff83007fc75008
> 0000000000000001 ffff830000000000 ffff828c80219b0c
> ffff83007fc76000 0000000000000000 ffff828c8015415c
> 000000000000e008 0000000000010082 ffff828c8026fdd8
> 0000000000000000 ffff828c80154158 ffff828c8026fde8
> 0000000000000262 00000000000002e2 0000000000000086
> 0000000000000262 0000000000000000 000000008026fe18
> ffff83007fc75008 ffff828c00000027 ffff83007fc76000
> ffff828c8021dd60 0000000000000002 000000007fc42000
> ffff83000008bfc0 ffff83000008bf40 0000000000002000
> ffff828c8026fe68 ffff828c80154f85 ffff828c8026fe78
> ffff828c80154fa5 ffff828c8026ff18 ffff828c802343ef
> 0000000000000000 0000000000000000 0000000000a1e000
> 0000000000aca3e0 ffff83000008bf40 0000000000000000
> 00000000ffffffff ffff83000000000c 0000000800000000
> 000000010000006e 0000000000000003 00000000000002f8
> 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 0000000000000000 0000000000000000
> 0000000000067e8c ffff828c801000b5 0000000000000000
> 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 00000000fffff000
>>> 
>>> This appears to be:
>>> (gdb) x/i 0xffff828c8015415c
>>> 0xffff828c8015415c <map_pages_to_xen+112>:	mov    (%rax),%rax
(gdb)
>>> x/i 0xffff828c80154f85 0xffff828c80154f85
>>> <__memguard_change_range+237>:	leaveq 
>>> 
>>> but I can''t find a good enclosing frame from there (is
> there a tool to pretty-print these stack traces?).
>>> 
>>> 
>> 
>> I bisected it down to:
>> 
>> The first bad revision is:
>> changeset:   20038:1197585e32b7
>> user:        Keir Fraser <keir.fraser@citrix.com>
>> date:        Fri Aug 07 17:29:50 2009 +0100
>> summary:     x86: Increase default max CPUs to 64.
>> 
> 
> Reverting this change on current tip works fine for me.
> 
>    J_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Keir Fraser

2009-Aug-15 17:58 UTC

head link

Re: [Xen-devel] Current xen-unstable xen crashing in boot

Yes, the dependencies on xen.lds are broken, as only xen.lds.S is indicated
as a dependency. Completely clean build required.

I should remember to fix this, and similar for asm-offsets.s.

 -- Keir

On 15/08/2009 13:03, "Wei, Gang" <gang.wei@intel.com> wrote:
> I used to meet similar problem before I do a clean build. The
> xen/arch/x86/xen.lds could not be regenerated without a clean build, which
> would cause __per_cpu_end still equal __per_cpu_start + (32 << 13).
> 
> Please confirm it is not caused by this factor.
> 
> Jimmy
> 
> Jeremy Fitzhardinge wrote:
>> On 08/14/09 13:48, Jeremy Fitzhardinge wrote:
>>>> (XEN) Early fatal page fault at e008:ffff828c8015415c
>> (cr2=ffff83007fc75008, ec=0000)
>>>> (XEN) Stack dump: 000000000007fc76 000000000000000c
>> ffff83007fc77ff0 ffff83007fc76000 ffff828c8026fe58
>> 0000000000000262 0000000000000020 0180000000000000
>> 000000000000010c ffff828c802a6380 ffff83007fc75008
>> 0000000000000001 ffff830000000000 ffff828c80219b0c
>> ffff83007fc76000 0000000000000000 ffff828c8015415c
>> 000000000000e008 0000000000010082 ffff828c8026fdd8
>> 0000000000000000 ffff828c80154158 ffff828c8026fde8
>> 0000000000000262 00000000000002e2 0000000000000086
>> 0000000000000262 0000000000000000 000000008026fe18
>> ffff83007fc75008 ffff828c00000027 ffff83007fc76000
>> ffff828c8021dd60 0000000000000002 000000007fc42000
>> ffff83000008bfc0 ffff83000008bf40 0000000000002000
>> ffff828c8026fe68 ffff828c80154f85 ffff828c8026fe78
>> ffff828c80154fa5 ffff828c8026ff18 ffff828c802343ef
>> 0000000000000000 0000000000000000 0000000000a1e000
>> 0000000000aca3e0 ffff83000008bf40 0000000000000000
>> 00000000ffffffff ffff83000000000c 0000000800000000
>> 000000010000006e 0000000000000003 00000000000002f8
>> 0000000000000000 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000 0000000000000000
>> 0000000000067e8c ffff828c801000b5 0000000000000000
>> 0000000000000000 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000 0000000000000000
>> 0000000000000000 00000000fffff000
>>>> 
>>>> This appears to be:
>>>> (gdb) x/i 0xffff828c8015415c
>>>> 0xffff828c8015415c <map_pages_to_xen+112>: mov   
(%rax),%rax (gdb)
>>>> x/i 0xffff828c80154f85 0xffff828c80154f85
>>>> <__memguard_change_range+237>: leaveq
>>>> 
>>>> but I can''t find a good enclosing frame from there (is
>> there a tool to pretty-print these stack traces?).
>>>> 
>>>> 
>>> 
>>> I bisected it down to:
>>> 
>>> The first bad revision is:
>>> changeset:   20038:1197585e32b7
>>> user:        Keir Fraser <keir.fraser@citrix.com>
>>> date:        Fri Aug 07 17:29:50 2009 +0100
>>> summary:     x86: Increase default max CPUs to 64.
>>> 
>> 
>> Reverting this change on current tip works fine for me.
>> 
>>    J


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

Jeremy Fitzhardinge

2009-Aug-17 00:30 UTC

head link

Re: [Xen-devel] Current xen-unstable xen crashing in boot

On 08/15/09 10:58, Keir Fraser wrote:> Yes, the dependencies on xen.lds are broken, as only xen.lds.S is indicated
> as a dependency. Completely clean build required.
>
> I should remember to fix this, and similar for asm-offsets.s.
>   
Yep, forcing a rebuild of xen.lds fixed the bug.

    J

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

Xen devel - Aug 2009 - Current xen-unstable xen crashing in boot

[Xen-devel] Current xen-unstable xen crashing in boot

Re: [Xen-devel] Current xen-unstable xen crashing in boot

Re: [Xen-devel] Current xen-unstable xen crashing in boot

Re: [Xen-devel] Current xen-unstable xen crashing in boot

RE: [Xen-devel] Current xen-unstable xen crashing in boot

Re: [Xen-devel] Current xen-unstable xen crashing in boot

Re: [Xen-devel] Current xen-unstable xen crashing in boot