From: Jeremy Fitzhardinge <jeremy@goop.org>
To: M A Young <m.a.young@durham.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: Continuing problems booting
Date: Sat, 21 Feb 2009 07:43:39 -0800 [thread overview]
Message-ID: <49A0212B.2080608@goop.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0902211225540.14632@vega4.dur.ac.uk>
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
Oh, I thought I'd fixed that (hm, must have lost the change somewhere).
Does it keep going OK anyway?
> 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.
Interesting. Xen has certainly revealed bugs in kvm's pagetable
management before, so it wouldn't surprise me if they've broken
something again (apparently they're not in the habit of testing with
Xen). Report it to kvm-devel <kvm@vger.kernel.org>
J
>
> \ \/ /___ _ __ |___ / |___ / / |
> \ // _ \ '_ \ |_ \ |_ \ | |
> / \ __/ | | | ___) | ___) || |
> /_/\_\___|_| |_| |____(_)____(_)_|
>
> (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>]
> (XEN) RFLAGS: 0000000000000296 EM: 1 CONTEXT: pv guest
> (XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx:
> 0000000000000000
> (XEN) rdx: 0000000000000000 rsi: ffffffff83131000 rdi:
> ffffffff83131000
> (XEN) rbp: ffffffff81695ff8 rsp: ffffffff81695f90 r8:
> 0000000000000000
> (XEN) r9: 0000000000000000 r10: 0000000000000000 r11:
> 0000000000000000
> (XEN) r12: 0000000000000000 r13: 0000000000000000 r14:
> 0000000000000000
> (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4:
> 00000000000006b0
> (XEN) cr3: 000000003b132000 cr2: 0000000000000028
> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
> (XEN) Guest stack trace from rsp=ffffffff81695f90:
> (XEN) 0000000000000000 0000000000000000 0000000000000000
> ffffffff816c5315
> (XEN) 000000010000e030 0000000000010096 ffffffff81695fd8
> 000000000000e02b
> (XEN) 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> (XEN) 0000000000000000 0000000000000000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) ffffffff816b6000 ffffffff816b6000 ffffffff816b6000
> ffffffff816b6000
> (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
>
> Michael Young
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-02-21 15:43 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 12:50 Continuing problems booting M A Young
2009-02-20 16:19 ` M A Young
2009-02-21 12:34 ` M A Young
2009-02-21 15:43 ` Jeremy Fitzhardinge [this message]
2009-02-21 15:52 ` M A Young
2009-02-21 22:26 ` M A Young
2009-02-22 6:54 ` Jeremy Fitzhardinge
2009-02-22 9:38 ` M A Young
2009-02-22 14:58 ` M A Young
2009-02-22 17:13 ` Jeremy Fitzhardinge
2009-02-22 23:02 ` M A Young
2009-02-22 23:19 ` Jeremy Fitzhardinge
2009-02-23 0:20 ` M A Young
2009-02-23 6:27 ` Jeremy Fitzhardinge
2009-02-25 0:56 ` M A Young
2009-02-27 23:27 ` M A Young
2009-02-28 1:18 ` Jeremy Fitzhardinge
2009-03-02 10:05 ` Gerd Hoffmann
2009-03-02 10:38 ` M A Young
2009-03-02 10:56 ` Gerd Hoffmann
2009-03-05 5:15 ` Jeremy Fitzhardinge
2009-03-05 7:35 ` Gerd Hoffmann
2009-03-05 11:01 ` Gerd Hoffmann
2009-03-05 18:56 ` Jeremy Fitzhardinge
2009-03-06 14:15 ` Gerd Hoffmann
2009-03-06 14:56 ` Gerd Hoffmann
2009-03-06 15:21 ` Jeremy Fitzhardinge
2009-03-09 15:38 ` Gerd Hoffmann
2009-03-09 15:56 ` Gerd Hoffmann
2009-03-09 16:35 ` Jeremy Fitzhardinge
2009-03-06 15:20 ` Jeremy Fitzhardinge
2009-03-06 15:34 ` Gerd Hoffmann
2009-03-06 16:08 ` Jeremy Fitzhardinge
2009-03-09 8:02 ` Gerd Hoffmann
2009-03-09 13:20 ` Gerd Hoffmann
2009-03-09 16:24 ` Jeremy Fitzhardinge
2009-03-10 9:39 ` Gerd Hoffmann
2009-03-10 17:13 ` Jeremy Fitzhardinge
2009-03-10 22:00 ` Gerd Hoffmann
2009-03-10 22:46 ` Jeremy Fitzhardinge
2009-03-11 10:33 ` Gerd Hoffmann
2009-03-05 15:57 ` Pasi Kärkkäinen
2009-03-05 1:52 ` Jeremy Fitzhardinge
2009-03-05 20:23 ` M A Young
2009-03-05 20:34 ` Jeremy Fitzhardinge
2009-03-06 1:07 ` M A Young
[not found] ` <49B0BF8B.9070002@zytor.com>
2009-03-06 19:35 ` M A Young
-- strict thread matches above, loose matches on Subject: below --
2009-02-21 22:59 Jeremy Fitzhardinge
2009-02-21 23:57 ` M A Young
2009-02-22 4:47 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49A0212B.2080608@goop.org \
--to=jeremy@goop.org \
--cc=m.a.young@durham.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.