Re: Re: Continuing problems booting

[Jeremy Fitzhardinge <jeremy@goop.org>]

M A Young wrote:
> And here are a couple more. First I get this traceback with a dom0 
> enabled kernel not running under xen atthe start of the boot log
> BUG: spinlock bad magic on CPU#0, swapper/0 (Not tainted)
>  lock: ffffffff81a39c90, .magic: 00000000, .owner: swapper/0, 
> .owner_cpu: 0
> Pid: 0, comm: swapper Not tainted 2.6.29-0.135.rc5.git3.fc10.x86_64 #1
> Call Trace:
>  [<ffffffff811f0af7>] spin_bug+0xb9/0xd8
>  [<ffffffff811f0b46>] _raw_spin_unlock+0x30/0xb9
>  [<ffffffff8143f17c>] _spin_unlock+0x35/0x50
>  [<ffffffff8102ebd5>] ? flat_send_IPI_mask+0x1f/0x35
>  [<ffffffff810402ef>] native_flush_tlb_others+0xf6/0x119
>  [<ffffffff810403a6>] flush_tlb_all+0x2a/0x60
>  [<ffffffff810f1f07>] __purge_vmap_area_lazy+0x142/0x1bc
>  [<ffffffff810f1e1f>] ? __purge_vmap_area_lazy+0x5a/0x1bc
>  [<ffffffff811ee6d4>] ? __bitmap_weight+0x4d/0xac
>  [<ffffffff810f25dc>] free_unmap_vmap_area_noflush+0x80/0x9b
>  [<ffffffff810f1941>] ? find_vmap_area+0x5b/0x7b
>  [<ffffffff810f262b>] remove_vm_area+0x34/0x97
>  [<ffffffff810f27ad>] __vunmap+0x50/0x103
>  [<ffffffff810857ff>] ? trace_hardirqs_on_caller+0x140/0x17a
>  [<ffffffff81392be0>] ? neigh_proxy_process+0xad/0x124
>  [<ffffffff810f2899>] vunmap+0x39/0x4f
>  [<ffffffff81440dde>] text_poke+0x13c/0x186
>  [<ffffffff8116df16>] ? __sysfs_put+0x1c/0x41
>  [<ffffffff81446641>] ? _etext+0x0/0x3
>  [<ffffffff8101a765>] alternatives_smp_unlock+0x59/0x85
>  [<ffffffff8101aa31>] alternatives_smp_switch+0x16a/0x1bd
>  [<ffffffff816ca9ef>] alternative_instructions+0x110/0x166
>  [<ffffffff816cb241>] ? identify_boot_cpu+0x23/0x5b
>  [<ffffffff816cb3c8>] check_bugs+0x21/0x54
>  [<ffffffff816beffe>] start_kernel+0x410/0x43b
>  [<ffffffff816be140>] ? early_idt_handler+0x0/0x71
>  [<ffffffff816be2ce>] x86_64_start_reservations+0xb9/0xd4
>  [<ffffffff816be000>] ? _sinittext+0x0/0x140
>  [<ffffffff816be3d6>] x86_64_start_kernel+0xed/0x110
>
> Secondly I get this crash when trying to start xen under qemu-kvm. 
> Something similar is happening when I try to start xen directly, but I 
> can't do serial logging on this computer so I can't be sure.
>
>  \ \/ /___ _ __   |___ / |___ / / |
>   \  // _ \ '_ \    |_ \   |_ \ | |
>   /  \  __/ | | |  ___) | ___) || |
>  /_/\_\___|_| |_| |____(_)____(_)_|
>
> (XEN) Xen version 3.3.1 (michael@home) (gcc version 4.3.2 20081105 
> (Red Hat 4.3.2-7) (GCC) ) Tue Feb  3 23:13:03 GMT 2009
> (XEN) Latest ChangeSet: unavailable
> (XEN) Command line: console=com1
> (XEN) Video information:
> (XEN)  VGA is text mode 80x25, font 8x16
> (XEN) Disc information:
> (XEN)  Found 0 MBR signatures
> (XEN)  Found 0 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 000000000009fc00 (usable)
> (XEN)  000000000009fc00 - 00000000000a0000 (reserved)
> (XEN)  00000000000e8000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 000000003fff0000 (usable)
> (XEN)  000000003fff0000 - 0000000040000000 (ACPI data)
> (XEN)  00000000fffbd000 - 0000000100000000 (reserved)
> (XEN) System RAM: 1023MB (1048124kB)
> (XEN) ACPI: RSDP 000FB9D0, 0014 (r0 QEMU  )
> (XEN) ACPI: RSDT 3FFF0000, 002C (r1 QEMU   QEMURSDT        1 
> QEMU        1)
> (XEN) ACPI: FACP 3FFF002C, 0074 (r1 QEMU   QEMUFACP        1 
> QEMU        1)
> (XEN) ACPI: DSDT 3FFF0100, 253C (r1   BXPC   BXDSDT        1 INTL 
> 20061109)
> (XEN) ACPI: FACS 3FFF00C0, 0040
> (XEN) ACPI: APIC 3FFF2640, 00E0 (r1 QEMU   QEMUAPIC        1 
> QEMU        1)
> (XEN) Xen heap: 14MB (14632kB)
> (XEN) Domain heap initialised
> (XEN) Processor #0 6:2 APIC version 20
> (XEN) IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23
> (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Detected 2394.081 MHz processor.
> (XEN) CPU0: Intel QEMU Virtual CPU version 0.9.1 stepping 03
> (XEN) Total of 1 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  -> Using new ACK method
> (XEN) Platform timer is 3.579MHz ACPI PM Timer
> (XEN) Brought up 1 CPUs
> (XEN) I/O virtualisation disabled
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN)  Xen  kernel: 64-bit, lsb, compat32
> (XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x239bbc0
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   0000000038000000->000000003c000000 (221906 pages 
> to be allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff81000000->ffffffff8239bbc0
> (XEN)  Init. ramdisk: ffffffff8239c000->ffffffff82f5f000
> (XEN)  Phys-Mach map: ffffffff82f5f000->ffffffff83130690
> (XEN)  Start info:    ffffffff83131000->ffffffff831314a4
> (XEN)  Page tables:   ffffffff83132000->ffffffff8314f000
> (XEN)  Boot stack:    ffffffff8314f000->ffffffff83150000
> (XEN)  TOTAL:         ffffffff80000000->ffffffff83400000
> (XEN)  ENTRY ADDRESS: ffffffff816be200
> (XEN) Dom0 has maximum 1 VCPUs
> (XEN) Scrubbing Free RAM: done.
> (XEN) Xen trace buffers: disabled
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch 
> input to Xen)
> (XEN) Freed 120kB init memory.
> (XEN) d0:v0: unhandled page fault (ec=0000)
> (XEN) Pagetable walk from 0000000000000028:
> (XEN)  L4[0x000] = 0000000000000000 ffffffffffffffff
> (XEN) domain_crash_sync called from entry.S
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) ----[ Xen-3.3.1  x86_64  debug=n  Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    e033:[<ffffffff816c5315>]

What does this correspond to in the kernel?

$ gdb vmlinux
(gdb) x/i 0xffffffff816c5315


    J