xen-devel
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't
On 04/08/2010 03:19 PM, Thomas Schwinge wrote:
> Hello!
>
> OK. You really tricked me into doing that: soldering iron, D-Sub 9
> sockets, null modem cable, and all that... :-)
>
> But here we go:
>
> (XEN) Xen version 3.4 (Debian 3.4.3~rc3-1) (waldi@xxxxxxxxxx) (gcc
> version 4.4.3 (Debian 4.4.3-2) ) Mon Mar 1 21:16:18 UTC 2010
> (XEN) Console output is synchronous.
> (XEN) Command line: com1=38400,8n1 console=com1 loglvl=all
> guest_loglvl=all sync_console console_to_ring apic=debug apic_verbosity=debug
> (XEN) Video information:
> (XEN) VGA is text mode 80x25, font 8x16
> (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
> (XEN) Disc information:
> (XEN) Found 1 MBR signatures
> (XEN) Found 1 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN) 0000000000000000 - 000000000009e000 (usable)
> (XEN) 000000000009e000 - 00000000000a0000 (reserved)
> (XEN) 00000000000e4000 - 0000000000100000 (reserved)
> (XEN) 0000000000100000 - 00000000ddee0000 (usable)
> (XEN) 00000000ddee0000 - 00000000ddeef000 (ACPI data)
> (XEN) 00000000ddeef000 - 00000000ddf00000 (ACPI NVS)
> (XEN) 00000000ddf00000 - 00000000e0000000 (reserved)
> (XEN) 00000000fec00000 - 00000000fec10000 (reserved)
> (XEN) 00000000fee00000 - 00000000fee01000 (reserved)
> (XEN) 00000000fff00000 - 0000000100000000 (reserved)
> (XEN) 0000000100000000 - 0000000120000000 (usable)
> (XEN) System RAM: 4062MB (4159992kB)
> (XEN) ACPI: RSDP 000F7350, 0024 (r2 PTLTD )
> (XEN) ACPI: XSDT DDEEB7E4, 004C (r1 PTLTD XSDT 50000 LTP
> 0)
> (XEN) ACPI: FACP DDEEB8A4, 00F4 (r3 FSC �PZ- 50000
> F4240)
> (XEN) ACPI: DSDT DDEEB998, 34FB (r1 FSC D2030 50000 MSFT
> 2000002)
> (XEN) ACPI: FACS DDEEFFC0, 0040
> (XEN) ACPI: SSDT DDEEEE93, 00B5 (r1 PTLTD POWERNOW 50000 LTP
> 1)
> (XEN) ACPI: APIC DDEEEF48, 0050 (r1 PTLTD APIC 50000 LTP
> 0)
> (XEN) ACPI: MCFG DDEEEF98, 0040 (r1 PTLTD MCFG 50000 LTP
> 0)
> (XEN) ACPI: BOOT DDEEEFD8, 0028 (r1 PTLTD $SBFTBL$ 50000 LTP
> 1)
> (XEN) NUMA turned off
> (XEN) Faking a node at 0000000000000000-0000000120000000
> (XEN) Domain heap initialised
> (XEN) found SMP MP-table at 000f73b0
> (XEN) DMI present.
> (XEN) Using APIC driver default
> (XEN) ACPI: PM-Timer IO Port: 0xf008
> (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[f004,0], pm1x_evt[f000,0]
> (XEN) ACPI: wakeup_vec[ddeeffcc], vec_size[20]
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> (XEN) Processor #0 15:15 APIC version 16
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 1, version 20, address 0xfec00000, GSI 0-23
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
> (XEN) ACPI: IRQ0 used by override.
> (XEN) ACPI: IRQ2 used by override.
> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) mapped APIC to ffff828bffffe000 (fee00000)
> (XEN) mapped IOAPIC to ffff828bffffd000 (fec00000)
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Initializing CPU#0
> (XEN) Detected 1800.104 MHz processor.
> (XEN) CPU0: AMD Flush Filter disabled
> (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> (XEN) CPU: L2 Cache: 128K (64 bytes/line)
> (XEN) CPU0: AMD K8 machine check reporting enabled.
> (XEN) CPU0: AMD Sempron(tm) Processor 3000+ stepping 02
> (XEN) Getting VERSION: 50010
> (XEN) Getting VERSION: 50010
> (XEN) Getting ID: 0
> (XEN) Getting LVT0: 10000
> (XEN) Getting LVT1: 10000
> (XEN) masked ExtINT on CPU#0
> (XEN) Total of 1 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN) -> Using new ACK method
> (XEN) init IO_APIC IRQs
> (XEN) IO-APIC (apicid-pin) 1-0, 1-16, 1-17, 1-18, 1-19, 1-20, 1-21,
> 1-22, 1-23 not connected.
> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0
> (XEN) number of MP IRQ sources: 15.
> (XEN) number of IO-APIC #1 registers: 24.
> (XEN) testing the IO APIC.......................
> (XEN) IO APIC #1......
> (XEN) .... register #00: 01000000
> (XEN) ....... : physical APIC id: 01
> (XEN) ....... : Delivery Type: 0
> (XEN) ....... : LTS : 0
> (XEN) .... register #01: 00178014
> (XEN) ....... : max redirection entries: 0017
> (XEN) ....... : PRQ implemented: 1
> (XEN) ....... : IO APIC version: 0014
> (XEN) .... register #02: 01000000
> (XEN) ....... : arbitration: 01
> (XEN) .... IRQ redirection table:
> (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
> (XEN) 00 000 00 1 0 0 0 0 0 0 00
> (XEN) 01 001 01 0 0 0 0 0 1 1 20
> (XEN) 02 001 01 0 0 0 0 0 1 1 F0
> (XEN) 03 001 01 0 0 0 0 0 1 1 28
> (XEN) 04 001 01 0 0 0 0 0 1 1 F1
> (XEN) 05 001 01 0 0 0 0 0 1 1 30
> (XEN) 06 001 01 0 0 0 0 0 1 1 38
> (XEN) 07 001 01 0 0 0 0 0 1 1 40
> (XEN) 08 001 01 0 0 0 0 0 1 1 48
> (XEN) 09 001 01 0 0 0 0 0 1 1 50
> (XEN) 0a 001 01 0 0 0 0 0 1 1 58
> (XEN) 0b 001 01 0 0 0 0 0 1 1 60
> (XEN) 0c 001 01 0 0 0 0 0 1 1 68
> (XEN) 0d 001 01 0 0 0 0 0 1 1 70
> (XEN) 0e 001 01 0 0 0 0 0 1 1 78
> (XEN) 0f 001 01 0 0 0 0 0 1 1 88
> (XEN) 10 000 00 1 0 0 0 0 0 0 00
> (XEN) 11 000 00 1 0 0 0 0 0 0 00
> (XEN) 12 000 00 1 0 0 0 0 0 0 00
> (XEN) 13 000 00 1 0 0 0 0 0 0 00
> (XEN) 14 000 00 1 0 0 0 0 0 0 00
> (XEN) 15 000 00 1 0 0 0 0 0 0 00
> (XEN) 16 000 00 1 0 0 0 0 0 0 00
> (XEN) 17 000 00 1 0 0 0 0 0 0 00
> (XEN) Using vector-based indexing
> (XEN) IRQ to pin mappings:
> (XEN) IRQ240 -> 0:2
> (XEN) IRQ32 -> 0:1
> (XEN) IRQ40 -> 0:3
> (XEN) IRQ241 -> 0:4
> (XEN) IRQ48 -> 0:5
> (XEN) IRQ56 -> 0:6
> (XEN) IRQ64 -> 0:7
> (XEN) IRQ72 -> 0:8
> (XEN) IRQ80 -> 0:9
> (XEN) IRQ88 -> 0:10
> (XEN) IRQ96 -> 0:11
> (XEN) IRQ104 -> 0:12
> (XEN) IRQ112 -> 0:13
> (XEN) IRQ120 -> 0:14
> (XEN) IRQ136 -> 0:15
> (XEN) .................................... done.
> (XEN) Using local APIC timer interrupts.
> (XEN) calibrating APIC timer ...
> (XEN) ..... CPU clock speed is 1800.0912 MHz.
> (XEN) ..... host bus clock speed is 200.0099 MHz.
> (XEN) ..... bus_scale = 0x0000CCD7
> (XEN) Platform timer is 3.579MHz ACPI PM Timer
> �(XEN) Brought up 1 CPUs
> (XEN) I/O virtualisation disabled
> (XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'.
> (XEN) ACPI sleep modes: S3
> (XEN) mcheck_poll: Machine check polling timer started.
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen kernel: 64-bit, lsb, compat32
> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x16b3000
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN) Dom0 alloc.: 0000000118000000->000000011c000000 (976900 pages to
> be allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN) Loaded kernel: ffffffff81000000->ffffffff816b3000
> (XEN) Init. ramdisk: ffffffff816b3000->ffffffff82fdc800
> (XEN) Phys-Mach map: ffffffff82fdd000->ffffffff83771020
> (XEN) Start info: ffffffff83772000->ffffffff837724b4
> (XEN) Page tables: ffffffff83773000->ffffffff83794000
> (XEN) Boot stack: ffffffff83794000->ffffffff83795000
> (XEN) TOTAL: ffffffff80000000->ffffffff83c00000
> (XEN) ENTRY ADDRESS: ffffffff814f6200
> (XEN) Dom0 has maximum 1 VCPUs
> (XEN) Scrubbing Free RAM: .done.
> (XEN) Xen trace buffers: disabled
> (XEN) Std. Loglevel: All
> (XEN) Guest Loglevel: All
> (XEN) **********************************************
> (XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
> (XEN) ******* This option is intended to aid debugging of Xen by ensuring
> (XEN) ******* that all output is synchronously delivered on the serial
> line.
> (XEN) ******* However it can introduce SIGNIFICANT latencies and affect
> (XEN) ******* timekeeping. It is NOT recommended for production use!
> (XEN) **********************************************
> (XEN) 3... 2... 1...
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input
> to Xen)
> (XEN) Freed 132kB init memory.
> mapping kernel into physical memory
> Xen: setup ISA identity maps
> about to get started...
> (XEN) d0:v0: unhandled page fault (ec=0000)
> (XEN) Pagetable walk from ffff80000420f878:
> (XEN) L4[0x100] = 000000011fdfc067 5555555555555555
> (XEN) L3[0x000] = 000000011fdfa067 5555555555555555
> (XEN) L2[0x021] = 0000000000000000 ffffffffffffffff
> (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 Tainted: C ]----
> (XEN) CPU: 0
> (XEN) RIP: e033:[<ffffffff814f8d88>]
>
Looks like it crashed very early. Do you have symbol information for
this kernel? If so, could you resolve this to a function?
> (XEN) RFLAGS: 0000000000000286 EM: 1 CONTEXT: pv guest
> (XEN) rax: ffff80000420f878 rbx: 00000000000f2813 rcx:
> 0000000000000000
> (XEN) rdx: 0000000000841f0f rsi: ffffffffffffffff rdi:
> 0000000000000013
> (XEN) rbp: 00000000000e0000 rsp: ffffffff81435df0 r8:
> 0000000000000002
> (XEN) r9: ffffffff813b441d r10: 0000000000000000 r11:
> 0000000000000009
> (XEN) r12: 00000000000fec00 r13: 0000000000012804 r14:
> 0000000000000000
> (XEN) r15: ffffffff81435e38 cr0: 000000008005003b cr4:
> 00000000000006f0
> (XEN) cr3: 0000000119001000 cr2: ffff80000420f878
> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
> (XEN) Guest stack trace from rsp=ffffffff81435df0:
> (XEN) 0000000000000000 0000000000000009 0000000000000000
> ffffffff814f8d88
> (XEN) 000000010000e030 0000000000010086 ffffffff81435e38
> 000000000000e02b
> (XEN) >ffffffff814f8d3d ffffffff81435e60 0000000000000001
> 0000000000000000
> (XEN) 0000000000007ff0 0000000002fdd000 0000000000841f0f
> 0000014081435f98
> (XEN) >ffffffff815a93ac 0000000000000007 0000000000000000
> ffffffff81435f98
> (XEN) 0000000000000000 0000000000000000>ffffffff814f8f85
> 000000010000000b
> (XEN) >ffffffff8152d2d0 0000000000000000 0000000000000000
> ffffffffffffffff
> (XEN) >ffffffff814fb5fb
> 0000000000000000>ffffffff814fa249>ffffffff813f5136
> (XEN) >ffffffff813b441d ffffffff81435f90
> ffffffff811ff14f>ffffffff8100e361
> (XEN) >ffffffff8100e343 00000000bbacb60c
> 00000000effea900>ffffffff813b441d
> (XEN) >ffffffff813f5136 0000000000000000 faa662c854df1257
> 0000000000000000
> (XEN) 0000000000000000 0000000000000000
> ffffffffffffffff>ffffffff8152c7b0
> (XEN) 0000000000000000 0000000000000000>ffffffff814f69d0
> 0000000001692cd4
>
And the addresses I marked with '>' as well?
[ If you have a vmlinux, you can do this with:
$ gdb vmlinux
(gdb) x/i 0xXXXXXX < show faulting instruction
(gdb) list *0xXXXXXX < get line info
]
Thanks,
J
> (XEN) faa662c854df1257 0000000000000000 ffffffff81001000
> 0000000000000000
> (XEN) 0000000000000000 0000000000000000 ffffffff814f8aca
> 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000000
> 0000000000000001
> (XEN) 0000000000000000 0000000000000000 ffffffff82fdd000
> ffffffff82fde000
> (XEN) ffffffff82fdf000 ffffffff82fe0000 ffffffff82fe1000
> ffffffff82fe2000
> (XEN) ffffffff82fe3000 ffffffff82fe4000 ffffffff82fe5000
> ffffffff82fe6000
> (XEN) ffffffff82fe7000 ffffffff82fe8000 ffffffff82fe9000
> ffffffff82fea000
> (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
>
>
> Regards,
> Thomas
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Thomas Schwinge
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Konrad Rzeszutek Wilk
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Ian Campbell
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Thomas Schwinge
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages,
Jeremy Fitzhardinge <=
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Thomas Schwinge
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Jeremy Fitzhardinge
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Thomas Schwinge
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Jeremy Fitzhardinge
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Thomas Goirand
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Jeremy Fitzhardinge
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Thomas Goirand
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Pasi Kärkkäinen
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Thomas Goirand
- Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages, Pasi Kärkkäinen
|
|
|