From: Jerone Young <jerone@gmail.com>
To: David F Barrera <dfbp@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: x86_64 Dom0 crash - Kernel BUG at hypervisor:53
Date: Fri, 3 Jun 2005 10:27:47 -0500 [thread overview]
Message-ID: <9f50a7a005060308274680826f@mail.gmail.com> (raw)
In-Reply-To: <1117905435.6079.4.camel@dyn95394185.austin.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 9615 bytes --]
What happens when you add "acpi=off" as an argument for the Xen kernel.
On 6/4/05, David F Barrera <dfbp@us.ibm.com> wrote:
> Dom0 will not boot on x86_64. Here's a more complete log:
> --------------
> Booting 'Xen Domain 0 on a FC4 Linux platform'
>
> kernel (hd0,0)/boot/xen.gz dom0_mem=256000 com2=19200,8n1
> console=vga,com2 nore
> boot
> [Multiboot-elf, <0x100000:0x5c358:0x22ca8>, shtab=0x17f078,
> entry=0x100000]
> module (hd0,0)/boot/vmlinuz-2.6-xen0 root=/dev/sda1 ro console=tty0
> [Multiboot-module @ 0x180000, 0x68c6d0 bytes]
> module (hd0,0)/boot/initrd-2.6.11.11-xen0
> [Multiboot-module @ 0x80d000, 0x19cc00 bytes]
>
> __ __ _____ ___ _ _
> \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| |
> \ // _ \ '_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
> / \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ |
> /_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_|
>
> http://www.cl.cam.ac.uk/netos/xen
> University of Cambridge Computer Laboratory
>
> Xen version 3.0-devel (root@ltc.austin.ibm.com) (gcc version 4.0.0
> 20050405 (Red Hat 4.0.0-0.40)) Fri Jun 3 09:18:15 CDT 2005
> Latest ChangeSet: information unavailable
>
> (XEN) Physical RAM map:
> (XEN) 0000000000000000 - 000000000009d400 (usable)
> (XEN) 000000000009d400 - 00000000000a0000 (reserved)
> (XEN) 00000000000e0000 - 0000000000100000 (reserved)
> (XEN) 0000000000100000 - 000000003ffbe680 (usable)
> (XEN) 000000003ffbe680 - 000000003ffd0000 (ACPI data)
> (XEN) 000000003ffd0000 - 0000000040000000 (reserved)
> (XEN) 00000000fec00000 - 0000000100000000 (reserved)
> (XEN) System RAM: 1023MB (1047916kB)
> (XEN) Xen heap: 14MB (14820kB)
> (XEN) found SMP MP-table at 0009d540
> (XEN) DMI 2.3 present.
> (XEN) Using APIC driver default
> (XEN) ACPI: RSDP (v000 IBM ) @
> 0x00000000000fdfc0
> (XEN) ACPI: RSDT (v001 IBM SERBLADE 0x00001000 IBM 0x45444f43) @
> 0x000000003ffcff80
> (XEN) ACPI: FADT (v002 IBM SERBLADE 0x00001000 IBM 0x45444f43) @
> 0x000000003ffcfec™\x01á™™™'
> (XEN) ACPI: DSDT (v001 IBM SERBLADE 0x00001000 INTL
> 0x02002025) @ 0x0000000000000000
> (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)
> 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) Using ACPI (MADT) for SMP configuration information
> (XEN) Initializing CPU#0
> (XEN) Detected 3600.308 MHz processor.
> (XEN) Using scheduler: Bo1\x11…¡•-XEN) CPU: L2 cache: 1024K
> (XEN) CPU: Physical Processor ID: 0
> (XEN) CPU1: Intel(R) Xeon(TM) CPU 3.60GHz stepping 01
> (XEN) Booting processor 2/6 eip 90000
> (XEN) Initializing CPU#2
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
> (XEN) CPU: L2 cache: 1024K
> (XEN) CPU: Physical Processor ID: 3
> (XEN) CPU2: Intel(R) Xeon(TM) CPU 3.60GHz stepping 01
> (XEN) Booting processor 3/7 eip 90000
> (XEN) Initializing CPU#3
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
> (XEN) CPU: L2 cache(XEN) Time init:
> (XEN) .... cpu_freq: 00000000:D6985928
> (XEN) .... scale: 00000001:1C6B89AF
> (XEN) .... Wall Clock: 1117792227s 180000us
> (XEN) Brought up 4 CPUs
> (XEN) mtrr: v2.0 (20020519)
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found:
> 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xffffffff80100000,LOADER=generic'
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN) Dom0 alloc.: 0000000008000000->0000000010000000 (31232 pages to
> be allocated)
> (XEN) VIRTUAL MEMORY ARRK\x022™™™™™™™™™™™™™™™XEN) Init. ramdisk:
> ffffffff80584000->ffffffff80720c00
> (XEN) Phys-Mach map: ffffffff80721000->ffffffff8075f800
> (XEN) Page tables: ffffffff80760000->ffffffff80767000
> (XEN) Start info: ffffffff80767000->ffffffff80768000
> (XEN) Boot stack: ffffffff80768000->ffffffff80769000
> (XEN) TOTAL: ffffffff80000000->ffffffff80800000
> (XEN) ENTRY ADDRESS: ffffffff80100000
> (XEN) Initrd len 0x19cc00, start at 0xffffffff80584000
> (XEN) Scrubbing Free RAM: ...........done.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen).
> Linux version 2.6.11.11-xen0 (root@bl2-10.ltc.austin.ibm.com) (gcc
> version 4.0.0 20050405 (Red Hat 4.0.0-0.40)) #1 Fri Jun 3 09:24:34 CDT
> 2005
> kernel direct mapping tables upto ffff88000fa00000 @ 800000-87f000
> Registering memory for bootmem: from a00000, size = f000000
> No mptable found.
> arch/xen/x86_64/mm/init.c:336: bad pte
> ffff88000136eec8(0000055555555067).
> arch/xen/x86_64/mm/init.c:336: bad
> pt…ɡᕹá}µµ¥¹¥Ñ‰…'ÁÑ•™™™™••…ɡᕹá}µµ¥¹¥Ñ‰…'ÁÑ•™™™™••…ɡᕹá}µµ¥¹¥Ñ‰…'ÁÑ•™™™™••…ɡᕹá}µµ¥¹¥Ñ‰…'ÁÑ•™™™™••…ɡᕹá}µµ¥¹¥Ñ‰…'ÁÑ•™™™™••…ɡᕹá}µµ¥¹¥Ñ‰…'ÁÑ•™™™™••…ɡᕹá}µµ¥¹¥Ñ‰…'ÁÑ•™™™™••¥'máu…''É•ÍÍmᙕ000] gsi_base[48])á}µµ¥¹¥Ñ‰…']–––‚‚‚Šš²*•
> IOAPIC[2]: apic_id 12, version 32, address 0xfec81000, GSI 48-71
> ACPI: IOAPIC (id[0x0b] address[0xfec81400] gsi_base[72])
> IOAPIC[3]: apic_id 11, version 32, address 0xfec81400, GSI 72-95
> 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)
> Setting APIC routing to flat
> Using ACPI (MADT) for SMP configuration information
> Built ɕ͕ÉÙ•''…Ñ…¥¹¥Ñount-cache hash table entries: 256 (order: 0,
> 4096 bytes)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: Intel(R) Xeon(TM) CPU 3.60GHz stepping 01
> NET: Registered protocol family 16
> PCI: Using configuration type 1
> ACPI: Subsystem revision 20050211
> ACPI: Interpreter enabled
> ACPI: Using IOAPIC for interrupt routing
> ACPI: PCI Root Bridge [PCI0] (00:00)
> PCI: Probing PCI hardware (bus 00)
> PCI: Ignoring BAR0-3 of IDE controller
> 0]Z‹+%™Ñ¡¥Í…Õ͕ͅ'•Ù¥•ѽÍѽÁݽɥ¹¥Ñ¥ÍÁɽ‰…‰±å‰•…Õ͕ѡ•'É¥Ù•É™…¥±•'ѽ…±±Á¥}•¹…‰±•}'•Ù¥•Í…Ñ•µÁ½É…ÉåݽɅɽչ'Ñ¡•Á¥É½ÕÑ•¥ÉÅ…ÉÕµ•¹ÑÉ•ÍѽɕÍÑ¡•½±'‰•¡…Ù¥½É%™Ñ¡¥Í…ÉÕµ•¹Ñµ…•ÍÑ¡•'•Ù¥•ݽɅ…¥¹Á±•…ÍÉåÁѽɅÁ¡¥A%8042.c: Can't read CTR while initializing i8042.
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> Floppy drive(s): fd0 is 1.44M
> floppy0: no floppy controllers found
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> loop: loaded (max 8 devices)
> HP CISS Driver (v 2.6.4)
> Intel(R) PRO/1000 Network Driver - version 5.6.10.1-k2
> Copyright (c) 1999-2004 Intel Corporation.
> pcnet32.c:v1.30i 06.28.2004 tsbogend@alpha.franken.de
> e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
> e100: Copyright(c) 1999-2004 Intel Corporation
> tg3.c:v3.23 (February 15, 2005)
> ACPI: PCI interrupt 0000:05:01.0[A] -> GSI 77 (level, low) -> IRQ 77
> ----------- [cut here ] --------- [please bite here ] ---------
> Kernel BUG at hypervisor:53
> invalid operand: 0000 [1]
> CPU 0
> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.11.11-xen0
> RIP: e030:[<ffffffff80118911>]
> <ffffffff80118911>{xen_l1_entry_update+113}
> RSP: e02b:ffff880000a05c08 EFLAGS: 00010282
> RAX: 00000000ffffffea RBX: ffff800000000000 RCX: ffffffff8011890d
> RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff880000a05c08
> RBP: 0000000000000000 R08: 0000000000007ff0 R09: ffff880000a05c78
> R10: 0000000000007ff0 R11: 0000000000000202 R12: 0000000000000001
> R13: ffff88000f9e4000 R14: ffff88000f9e4000 R15: 0000000000000400
> FS: 0000000000000000(0000) GS:ffffffff804e3980(0000)
> knlGS:0000000000000000
> CS: e033 DS: 0000 ES: 0000
> Process swapper (pid: 1, threadinfo ffff880000a04000, task
> ffff880000a11440)
> Stack: 000000000887ef20 800000003ffba067 ffff880000a05c58
> ffffffff80113d84
> ffff880000a05c78 000000000f9e4000 ffff88008f9e4000
> 000000000f9e4000
> ffff88008f9e4000 ffff880000a05cc0
> Call Trace:<ffffffff80113d84>{dma_alloc_coherent+1028}
> <ffffffff80535365>{tg3_test_dma+53}
> <ffffffff80536ec0>{tg3_init_one+6400}
> <ffffffff80109eb6>{evtchn_do_upcall+118}
> <ffffffff8020eaaf>{pci_device_probe+95}
> <ffffffff8024760d>{driver_probe_device+77}
> <ffffffff80247686>{driver_attach+70}
> <ffffffff8024775e>{bus_add_driver+142}
> <f
> --
>
> David F Barrera
> IBM Linux Technology Center
> dfbp@us.ibm.com
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2005-06-03 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 15:18 x86_64 Dom0 crash - Kernel BUG at hypervisor:53 David F Barrera
2005-06-03 15:27 ` Jerone Young [this message]
2005-06-03 15:41 ` David F Barrera
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=9f50a7a005060308274680826f@mail.gmail.com \
--to=jerone@gmail.com \
--cc=dfbp@us.ibm.com \
--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.