Alan J. Wylie
2010-Oct-07 09:57 UTC
[Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
System: Supermicro SM-SC825TQ-R720LPB, 8GB RAM
Motherboard: X8DTL
Processor: 1 x Intel XEON E5506 quad core
RAID controller: LSI MegaRAID SAS 8708
Bisected (by hand) to between
69e50db2 (good) 2.6.32.21 "Merge commit ''v2.6.32.21''
into xen/next-2.6.32"
and
dda56688 (bad) "Merge branch ''xen/next'' into
xen/next-2.6.32"
I don''t know if it is of any relevance, but lshw hangs during DMI.
The end of the strace is:
mmap(NULL, 4080, PROT_READ, MAP_SHARED, 3, 0xff000) = 0x7fc182228000
munmap(0x7fc182228000, 4080) = 0
mmap(NULL, 4096, PROT_READ, MAP_SHARED, 3, 0xff000) = 0x7fc182228000
munmap(0x7fc182228000, 4096) = 0
mmap(NULL, 4112, PROT_READ, MAP_SHARED, 3, 0xff000) = 0x7fc182227000
^C--- SIGINT (Interrupt) @ 0 (0) ---
and XEN then outputs large numbers of the following message:
(XEN) mm.c:860:d0 Error getting mfn 15b3 (pfn 21973) from L1 entry
80000000015b3625 for l1e_owner=0, pg_owner=32753
This patch to LSHW stops it hanging, the output of this lshw can be
found later in this e-mail, along with grub.conf, /proc/cpuinfo, lshw,
dmidecode and the console output for a crash and a good boot.
diff -Nau -r lshw-B.02.14/src/core/dmi.cc
lshw-B.02.14.patched/src/core/dmi.cc
--- lshw-B.02.14/src/core/dmi.cc 2009-02-12 22:53:09.000000000 +0000
+++ lshw-B.02.14.patched/src/core/dmi.cc 2010-10-07 08:56:46.000000000
+0100
@@ -1725,7 +1725,7 @@
}
fp -= 16;
- while (efi || (fp < 0xFFFFF))
+ while (efi || (fp < 0xFFFE0))
{
fp += 16;
mmoffset = fp % getpagesize();
I''ve attempted to disassemble what I believe to be the crashing code:
(XEN) RIP: e033:[<ffffffff8100bd47>]
From System.map:
ffffffff8100bd10 T get_phys_to_machine
ffffffff8100bd4c t pin_pagetable_pfn
(gdb) x/20i 0xffffffff8100bd10
0xffffffff8100bd10: or $0xffffffffffffffff,%rax
0xffffffff8100bd14: cmp $0x7ffffff,%rdi
0xffffffff8100bd1b: ja 0xffffffff8100bd4b
0xffffffff8100bd1d: mov %rdi,%rcx
0xffffffff8100bd20: mov %rdi,%rax
0xffffffff8100bd23: shr $0x12,%rcx
0xffffffff8100bd27: shr $0x9,%rax
0xffffffff8100bd2b: mov %ecx,%ecx
0xffffffff8100bd2d: and $0x1ff,%eax
0xffffffff8100bd32: mov 0x53222f(%rip),%rdx #
0xffffffff8153df68
0xffffffff8100bd39: and $0x1ff,%edi
0xffffffff8100bd3f: mov (%rdx,%rcx,8),%rdx
0xffffffff8100bd43: mov (%rdx,%rax,8),%rax
0xffffffff8100bd47: mov (%rax,%rdi,8),%rax
0xffffffff8100bd4b: retq
0xffffffff8100bd4c: sub $0x28,%rsp
0xffffffff8100bd50: mov %rsi,%rax
0xffffffff8100bd53: mov %edi,(%rsp)
0xffffffff8100bd56: cmpb $0x0,0x4acfc5(%rip) #
0xffffffff814b8d22
0xffffffff8100bd5d: jne 0xffffffff8100bd7a
If there is any more information that I can provide, I will be glad to
do so.
------8<------8<------8<------8<------8<------8<------8<------8<------8<
# grub.conf
default 0
timeout 30
serial --unit=1 --speed=19200 --word=8 --parity=no --stop=1
terminal serial
title Xen 4.0.1 / Linux 2.6.32.18
root (hd0,0)
kernel /xen.gz com2=19200,8n1 console=com2 noreboot
module /vmlinuz-2.6.32.18-xen0 root=/dev/sda2 console=hvc0
title test
root (hd0,0)
kernel /xen-4.0.2-rc1-pre.gz com2=19200,8n1 console=com2 noreboot
module /vmlinuz-test root=/dev/sda2 console=hvc0 earlyprintk=xen
------8<------8<------8<------8<------8<------8<------8<------8<------8<
# console output for failed boot of xen/next
commit 179eca50d08fa05d7650fcb8a0d3e6598cf2388a
Merge commit ''v2.6.32.24'' into xen/next-2.6.32
\ \/ /___ _ __ | || | / _ \ |___ \ _ __ ___/ | _ __ _ __ ___
\ // _ \ ''_ \ | || |_| | | | __) |__| ''__/ __| |__|
''_ \| ''__/ _ \
/ \ __/ | | | |__ _| |_| | / __/|__| | | (__| |__| |_) | | | __/
/_/\_\___|_| |_| |_|(_)___(_)_____| |_| \___|_| | .__/|_| \___|
|_|
(XEN) Xen version 4.0.2-rc1-pre (root@example.com) (gcc version 4.4.3
(Gentoo 4.4.3-r2 p1.2) ) Tue Oct 5 11:03:53 BST 2010
(XEN) Latest ChangeSet: Fri Sep 17 17:06:57 2010 +0100 21350:6e0ffcd2d9e0
(XEN) Bootloader: GNU GRUB 0.97
(XEN) Command line: com2=19200,8n1 console=com2 noreboot
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN) EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 0000000000098c00 (usable)
(XEN) 0000000000098c00 - 00000000000a0000 (reserved)
,(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000bf780000 (usable)
(XEN) 00000000bf78e000 - 00000000bf790000 type 9arlyprintk=xen
(XEN) 00000000bf790000 - 00000000bf79e000 (ACPI data)
(XEN) 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS)
(XEN) 00000000bf7d0000 - 00000000bf7e0000 (reserved)
(XEN) 00000000bf7ec000 - 00000000c0000000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ffc00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000240000000 (usable)
(XEN) ACPI: RSDP 000FAC10, 0024 (r2 ACPIAM)
(XEN) ACPI: XSDT BF790100, 007C (r1 SMCI 20100528 MSFT 97)
(XEN) ACPI: FACP BF790290, 00F4 (r3 052810 FACP1443 20100528 MSFT 97)
(XEN) ACPI: DSDT BF7906A0, 650A (r1 10006 10006000 0 INTL 20051117)
(XEN) ACPI: FACS BF79E000, 0040
(XEN) ACPI: APIC BF790390, 011E (r1 052810 APIC1443 20100528 MSFT 97)
(XEN) ACPI: MCFG BF7904B0, 003C (r1 052810 OEMMCFG 20100528 MSFT 97)
(XEN) ACPI: SLIT BF7904F0, 0030 (r1 052810 OEMSLIT 20100528 MSFT 97)
(XEN) ACPI: OEMB BF79E040, 007D (r1 052810 OEMB1443 20100528 MSFT 97)
(XEN) ACPI: HPET BF79A6A0, 0038 (r1 052810 OEMHPET 20100528 MSFT 97)
(XEN) ACPI: SSDT BF79EE90, 0363 (r1 DpgPmm CpuPm 12 INTL 20051117)
(XEN) ACPI: EINJ BF79A6E0, 0130 (r1 AMIER AMI_EINJ 20100528 MSFT 97)
(XEN) ACPI: BERT BF79A870, 0030 (r1 AMIER AMI_BERT 20100528 MSFT 97)
(XEN) ACPI: ERST BF79A8A0, 01B0 (r1 AMIER AMI_ERST 20100528 MSFT 97)
(XEN) ACPI: HEST BF79AA50, 00A8 (r1 AMIER ABC_HEST 20100528 MSFT 97)
(XEN) System RAM: 8183MB (8379488kB)
(XEN) Domain heap initialised
(XEN) Processor #0 7:10 APIC version 21
(XEN) Processor #2 7:10 APIC version 21
(XEN) Processor #4 7:10 APIC version 21
(XEN) Processor #6 7:10 APIC version 21
(XEN) IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 3, version 32, address 0xfec8a000, GSI 24-47
(XEN) Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2133.440 MHz processor.
(XEN) Initing memory sharing.
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) EPT supports 2MB super page.
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) I/O virtualisation disabled
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) TSC is reliable, synchronization unnecessary
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 16 KiB.
(XEN) Brought up 4 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x16b5000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000234000000->0000000238000000 (2021733 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff816b5000
(XEN) Init. ramdisk: ffffffff816b5000->ffffffff816b5000
(XEN) Phys-Mach map: ffffffff816b5000->ffffffff82641b28
(XEN) Start info: ffffffff82642000->ffffffff826424b4
(XEN) Page tables: ffffffff82643000->ffffffff8265a000
(XEN) Boot stack: ffffffff8265a000->ffffffff8265b000
(XEN) TOTAL: ffffffff80000000->ffffffff82800000
(XEN) ENTRY ADDRESS: ffffffff814d0200
(XEN) Dom0 has maximum 4 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 172kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
Linux version 2.6.32.24-xen0 (root@xenity) (gcc version 4.4.3 (Gentoo
4.4.3-r2 p1.2) ) #1 SMP Thu Oct 7 10:20:02 BST 2010
Command line: root=/dev/sda2 console=hvc0 earlyprintk=xen
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
Centaur CentaurHauls
xen_release_chunk: looking at area pfn bf780-bf78e: 14 pages freed
xen_release_chunk: looking at area pfn bf7e0-bf7ec: 12 pages freed
xen_release_chunk: looking at area pfn c0000-e0000: 131072 pages freed
xen_release_chunk: looking at area pfn f0000-fec00: 60416 pages freed
xen_release_chunk: looking at area pfn fec01-fec8a: 137 pages freed
xen_release_chunk: looking at area pfn fec8b-fee00: 373 pages freed
xen_release_chunk: looking at area pfn fee01-ffc00: 3583 pages freed
released 195607 pages of unused memory
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000000098c00 (usable)
Xen: 0000000000098c00 - 0000000000100000 (reserved)
Xen: 0000000000100000 - 00000000bf780000 (usable)
Xen: 00000000bf78e000 - 00000000bf790000 type 9
Xen: 00000000bf790000 - 00000000bf79e000 (ACPI data)
Xen: 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS)
Xen: 00000000bf7d0000 - 00000000bf7e0000 (reserved)
Xen: 00000000bf7ec000 - 00000000c0000000 (reserved)
Xen: 00000000e0000000 - 00000000f0000000 (reserved)
Xen: 00000000fec00000 - 00000000fec01000 (reserved)
Xen: 00000000fec8a000 - 00000000fec8b000 (reserved)
Xen: 00000000fee00000 - 00000000fee01000 (reserved)
Xen: 00000000ffc00000 - 0000000100000000 (reserved)
Xen: 0000000100000000 - 000000026fc17000 (usable)
bootconsole [xenboot0] enabled
DMI present.
AMI BIOS detected: BIOS may corrupt low RAM, working around it.
last_pfn = 0x26fc17 max_arch_pfn = 0x400000000
x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106
last_pfn = 0xbf780 max_arch_pfn = 0x400000000
init_memory_mapping: 0000000000000000-00000000bf780000
init_memory_mapping: 0000000100000000-000000026fc17000
(XEN) d0:v0: unhandled page fault (ec=0000)
(XEN) Pagetable walk from ffffffff816c82d0:
(XEN) L4[0x1ff] = 0000000235003067 0000000000001003
(XEN) L3[0x1fe] = 0000000235007067 0000000000001007
(XEN) L2[0x00b] = 0000000000000000 ffffffffffffffff
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-4.0.2-rc1-pre x86_64 debug=n Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e033:[<ffffffff8100bd47>]
(XEN) RFLAGS: 0000000000000206 EM: 1 CONTEXT: pv guest
(XEN) rax: ffffffff816c8000 rbx: 800000000265a063 rcx: 0000000000000000
(XEN) rdx: ffffffff8158f000 rsi: ffffffffff400000 rdi: 000000000000005a
(XEN) rbp: 000000000265a000 rsp: ffffffff81449c10 r8: 8000000000000163
(XEN) r9: 000000000000000f r10: ffffffff815593e0 r11: 00000000000003bf
(XEN) r12: 000000000265a000 r13: 8000000000000163 r14: 0000000000000001
(XEN) r15: 00000000000009ff cr0: 000000008005003b cr4: 00000000000026f0
(XEN) cr3: 0000000235001000 cr2: ffffffff816c82d0
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
(XEN) Guest stack trace from rsp=ffffffff81449c10:
(XEN) 0000000000000000 00000000000003bf 0000000000000000 ffffffff8100bd47
(XEN) 000000010000e030 0000000000010006 ffffffff81449c58 000000000000e02b
(XEN) 0000000000000020 ffffffff8100be83 800000000265a063 ffffffff8100c000
(XEN) 0000000000000000 ffffffff8100b789 00000000000003bf ffffffff815593e0
(XEN) 000000000000000f 8000000000000163 800000000265a063 ffffffffff400000
(XEN) ffffffff8153a000 000000026fc17000 ffffffff814e2197 00000000000003bf
(XEN) ffffffff815593e0 ffffffffff400000 00000001815593e0 0000000000000000
(XEN) ffffffff81449d90 000000000265a000 ffff88026fc17000 000000026fc17000
(XEN) 000000026fc17000 0000000000000000 ffffffff8130aef8 ffff880001002020
(XEN) 0000000100000000 ffff88026fc17000 ffffffff814fc1ba 0000000000000001
(XEN) ffffffff814c70a0 8000000000000163 0000000000000000 0000000000000004
(XEN) 0000000000000000 0000000000000000 ffff880001002000 ffffffff8100b76b
(XEN) 00000000000003bf ffffffff815593e0 ffffffff81001880 000000026fc17000
(XEN) ffff88026fc17000 ffffffff813ca5c5 ffff88026fc17000 0000000000000000
(XEN) ffffffff814fc363 000000026fc17000 ffffffff8131c16d 0000000000000020
(XEN) ffff880100000000 ffffffff81449e08 00000000bf780000 00000000bf780000
(XEN) ffffffff81449e78 0000000000000001 0000000000000001 ffffffff813ca5c5
(XEN) 0000000000000000 000000026fc17000 ffffffff8130ad22 0000000000000000
(XEN) 0000000000000000 ffffffff00000000 0000000100000000 ffff880000000000
(XEN) 0000000000000000 0000000100000000 000000026fc17000 0000000000000000
(XEN) Domain 0 crashed: ''noreboot'' set - not rebooting.
------8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------
# good boot of 2.6.32.18
(XEN) Xen version 4.0.1 (@example.com) (gcc version 4.4.3 (Gentoo
4.4.3-r2 p1.2) ) Mon Oct 4 13:34:41 BST 2010
(XEN) Latest ChangeSet: unavailable
(XEN) Bootloader: GNU GRUB 0.97
(XEN) Command line: com2=19200,8n1 console=com2 noreboot
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN) EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 0000000000098c00 (usable)
(XEN) 0000000000098c00 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000bf780000 (usable)
(XEN) 00000000bf78e000 - 00000000bf790000 type 9
(XEN) 00000000bf790000 - 00000000bf79e000 (ACPI data)
(XEN) 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS)
(XEN) 00000000bf7d0000 - 00000000bf7e0000 (reserved)
(XEN) 00000000bf7ec000 - 00000000c0000000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ffc00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000240000000 (usable)
(XEN) ACPI: RSDP 000FAC10, 0024 (r2 ACPIAM)
(XEN) ACPI: XSDT BF790100, 007C (r1 SMCI 20100528 MSFT 97)
(XEN) ACPI: FACP BF790290, 00F4 (r3 052810 FACP1443 20100528 MSFT 97)
(XEN) ACPI: DSDT BF7906A0, 650A (r1 10006 10006000 0 INTL 20051117)
(XEN) ACPI: FACS BF79E000, 0040
(XEN) ACPI: APIC BF790390, 011E (r1 052810 APIC1443 20100528 MSFT 97)
(XEN) ACPI: MCFG BF7904B0, 003C (r1 052810 OEMMCFG 20100528 MSFT 97)
(XEN) ACPI: SLIT BF7904F0, 0030 (r1 052810 OEMSLIT 20100528 MSFT 97)
(XEN) ACPI: OEMB BF79E040, 007D (r1 052810 OEMB1443 20100528 MSFT 97)
(XEN) ACPI: HPET BF79A6A0, 0038 (r1 052810 OEMHPET 20100528 MSFT 97)
(XEN) ACPI: SSDT BF79EE90, 0363 (r1 DpgPmm CpuPm 12 INTL 20051117)
(XEN) ACPI: EINJ BF79A6E0, 0130 (r1 AMIER AMI_EINJ 20100528 MSFT 97)
(XEN) ACPI: BERT BF79A870, 0030 (r1 AMIER AMI_BERT 20100528 MSFT 97)
(XEN) ACPI: ERST BF79A8A0, 01B0 (r1 AMIER AMI_ERST 20100528 MSFT 97)
(XEN) ACPI: HEST BF79AA50, 00A8 (r1 AMIER ABC_HEST 20100528 MSFT 97)
(XEN) System RAM: 8183MB (8379488kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-0000000240000000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000ff780
(XEN) DMI 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[bf79e00c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
(XEN) Processor #4 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
(XEN) Processor #6 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x84] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x85] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x86] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x87] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x88] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x89] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x8a] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x8b] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x8c] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x8d] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x8e] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x8f] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x90] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x91] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x92] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x93] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x94] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x95] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x96] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x97] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
(XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x03] address[0xfec8a000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 3, version 32, address 0xfec8a000, GSI 24-47
(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 2 I/O APICs
(XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
(XEN) PCI: MCFG area at e0000000 reserved in E820
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2133.464 MHz processor.
(XEN) Initing memory sharing.
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) EPT supports 2MB super page.
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) Intel machine check reporting enabled
(XEN) I/O virtualisation disabled
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) TSC is reliable, synchronization unnecessary
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 32 KiB.
(XEN) microcode.c:73:d32767 microcode: CPU1 resumed
(XEN) microcode.c:73:d32767 microcode: CPU2 resumed
(XEN) Brought up 4 CPUs
(XEN) microcode.c:73:d32767 microcode: CPU3 resumed
(XEN) HPET: 4 timers in total, 0 timers will be used for broadcast
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x444000
(XEN) elf_parse_binary: phdr: paddr=0x1444000 memsz=0xf34a4
(XEN) elf_parse_binary: phdr: paddr=0x1538000 memsz=0x888
(XEN) elf_parse_binary: phdr: paddr=0x1539000 memsz=0x132d8
(XEN) elf_parse_binary: phdr: paddr=0x154d000 memsz=0x160000
(XEN) elf_parse_binary: memory: 0x1000000 -> 0x16ad000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff8154d200
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81009000
(XEN) elf_xen_parse_note: FEATURES
"!writable_page_tables|pae_pgdir_above_4gb"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) elf_xen_addr_calc_check: addresses:
(XEN) virt_base = 0xffffffff80000000
(XEN) elf_paddr_offset = 0x0
(XEN) virt_offset = 0xffffffff80000000
(XEN) virt_kstart = 0xffffffff81000000
(XEN) virt_kend = 0xffffffff816ad000
(XEN) virt_entry = 0xffffffff8154d200
(XEN) p2m_base = 0xffffffffffffffff
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x16ad000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000234000000->0000000238000000 (2021507 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff816ad000
(XEN) Init. ramdisk: ffffffff816ad000->ffffffff816ad000
(XEN) Phys-Mach map: ffffffff816ad000->ffffffff82639418
(XEN) Start info: ffffffff8263a000->ffffffff8263a4b4
(XEN) Page tables: ffffffff8263b000->ffffffff82652000
(XEN) Boot stack: ffffffff82652000->ffffffff82653000
(XEN) TOTAL: ffffffff80000000->ffffffff82800000
(XEN) ENTRY ADDRESS: ffffffff8154d200
(XEN) Dom0 has maximum 4 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81444000
(XEN) elf_load_binary: phdr 1 at 0xffffffff81444000 -> 0xffffffff815374a4
(XEN) elf_load_binary: phdr 2 at 0xffffffff81538000 -> 0xffffffff81538888
(XEN) elf_load_binary: phdr 3 at 0xffffffff81539000 -> 0xffffffff8154c2d8
(XEN) elf_load_binary: phdr 4 at 0xffffffff8154d000 -> 0xffffffff815b3000
(XEN) Scrubbing Free RAM: .done.
(XEN) trace.c:89:d32767 calc_tinfo_first_offset: NR_CPUs 128,
offset_in_bytes 258, t_info_first_offset 65
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch
input to Xen)
(XEN) Freed 164kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
Linux version 2.6.32.18-xen0 (root@xenity) (gcc version 4.4.3 (Gentoo
4.4.3-r2 p1.2) ) #2 SMP Wed Oct 6 09:31:27 BST 2010
Command line: root=/dev/sda2 console=hvc0
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
Centaur CentaurHauls
xen_release_chunk: looking at area pfn bf780-bf78e: 14 pages freed
xen_release_chunk: looking at area pfn bf7e0-bf7ec: 12 pages freed
xen_release_chunk: looking at area pfn c0000-e0000: 131072 pages freed
xen_release_chunk: looking at area pfn f0000-fec00: 60416 pages freed
xen_release_chunk: looking at area pfn fec01-fec8a: 137 pages freed
xen_release_chunk: looking at area pfn fec8b-fee00: 373 pages freed
xen_release_chunk: looking at area pfn fee01-ffc00: 3583 pages freed
released 195607 pages of unused memory
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000000098c00 (usable)
Xen: 0000000000098c00 - 0000000000100000 (reserved)
Xen: 0000000000100000 - 00000000bf780000 (usable)
Xen: 00000000bf78e000 - 00000000bf790000 type 9
Xen: 00000000bf790000 - 00000000bf79e000 (ACPI data)
Xen: 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS)
Xen: 00000000bf7d0000 - 00000000bf7e0000 (reserved)
Xen: 00000000bf7ec000 - 00000000c0000000 (reserved)
Xen: 00000000e0000000 - 00000000f0000000 (reserved)
Xen: 00000000fec00000 - 00000000fec01000 (reserved)
Xen: 00000000fec8a000 - 00000000fec8b000 (reserved)
Xen: 00000000fee00000 - 00000000fee01000 (reserved)
Xen: 00000000ffc00000 - 0000000100000000 (reserved)
Xen: 0000000100000000 - 00000001f1883000 (usable)
DMI present.
AMI BIOS detected: BIOS may corrupt low RAM, working around it.
last_pfn = 0x1f1883 max_arch_pfn = 0x400000000
x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106
last_pfn = 0xbf780 max_arch_pfn = 0x400000000
init_memory_mapping: 0000000000000000-00000000bf780000
init_memory_mapping: 0000000100000000-00000001f1883000
ACPI: RSDP 00000000000fac10 00024 (v02 ACPIAM)
ACPI: XSDT 00000000bf790100 0007C (v01 SMCI 20100528 MSFT 00000097)
ACPI: FACP 00000000bf790290 000F4 (v03 052810 FACP1443 20100528 MSFT 00000097)
ACPI: DSDT 00000000bf7906a0 0650A (v01 10006 10006000 00000000 INTL 20051117)
ACPI: FACS 00000000bf79e000 00040
ACPI: APIC 00000000bf790390 0011E (v01 052810 APIC1443 20100528 MSFT 00000097)
ACPI: MCFG 00000000bf7904b0 0003C (v01 052810 OEMMCFG 20100528 MSFT 00000097)
ACPI: SLIT 00000000bf7904f0 00030 (v01 052810 OEMSLIT 20100528 MSFT 00000097)
ACPI: OEMB 00000000bf79e040 0007D (v01 052810 OEMB1443 20100528 MSFT 00000097)
ACPI: HPET 00000000bf79a6a0 00038 (v01 052810 OEMHPET 20100528 MSFT 00000097)
ACPI: SSDT 00000000bf79ee90 00363 (v01 DpgPmm CpuPm 00000012 INTL 20051117)
ACPI: EINJ 00000000bf79a6e0 00130 (v01 AMIER AMI_EINJ 20100528 MSFT 00000097)
ACPI: BERT 00000000bf79a870 00030 (v01 AMIER AMI_BERT 20100528 MSFT 00000097)
ACPI: ERST 00000000bf79a8a0 001B0 (v01 AMIER AMI_ERST 20100528 MSFT 00000097)
ACPI: HEST 00000000bf79aa50 000A8 (v01 AMIER ABC_HEST 20100528 MSFT 00000097)
(8 early reservations) ==> bootmem [0000000000 - 01f1883000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [000263b000 - 0002652000] XEN PAGETABLES ==> [000263b000 - 0002652000]
#2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
#3 [0001000000 - 000168c60c] TEXT DATA BSS ==> [0001000000 - 000168c60c]
#4 [00016ad000 - 000263b000] XEN START INFO ==> [00016ad000 - 000263b000]
#5 [000168d000 - 000168d21d] BRK ==> [000168d000 - 000168d21d]
#6 [0000100000 - 00006e6000] PGTABLE ==> [0000100000 - 00006e6000]
#7 [0002652000 - 0002de3000] PGTABLE ==> [0002652000 - 0002de3000]
found SMP MP-table at [ffff8800000ff780] ff780
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
DMA32 0x00001000 -> 0x00100000
Normal 0x00100000 -> 0x001f1883
Movable zone start PFN for each node
early_node_map[3] active PFN ranges
0: 0x00000010 -> 0x00000098
0: 0x00000100 -> 0x000bf780
0: 0x00100000 -> 0x001f1883
ACPI: PM-Timer IO Port: 0x808
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x84] disabled)
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x85] disabled)
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x86] disabled)
ACPI: LAPIC (acpi_id[0x08] lapic_id[0x87] disabled)
ACPI: LAPIC (acpi_id[0x09] lapic_id[0x88] disabled)
ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x89] disabled)
ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x8a] disabled)
ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x8b] disabled)
ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x8c] disabled)
ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x8d] disabled)
ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x8e] disabled)
ACPI: LAPIC (acpi_id[0x10] lapic_id[0x8f] disabled)
ACPI: LAPIC (acpi_id[0x11] lapic_id[0x90] disabled)
ACPI: LAPIC (acpi_id[0x12] lapic_id[0x91] disabled)
ACPI: LAPIC (acpi_id[0x13] lapic_id[0x92] disabled)
ACPI: LAPIC (acpi_id[0x14] lapic_id[0x93] disabled)
ACPI: LAPIC (acpi_id[0x15] lapic_id[0x94] disabled)
ACPI: LAPIC (acpi_id[0x16] lapic_id[0x95] disabled)
ACPI: LAPIC (acpi_id[0x17] lapic_id[0x96] disabled)
ACPI: LAPIC (acpi_id[0x18] lapic_id[0x97] disabled)
ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 0, address 0xfec00000, GSI 0-0
ACPI: IOAPIC (id[0x03] address[0xfec8a000] gsi_base[24])
IOAPIC[1]: apic_id 3, version 0, address 0xfec8a000, GSI 24-24
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ERROR: Unable to locate IOAPIC for GSI 2
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ERROR: Unable to locate IOAPIC for GSI 9
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a301 base: 0xfed00000
SMP: Allowing 4 CPUs, 0 hotplug CPUs
Allocating PCI resources starting at c0000000 (gap: c0000000:20000000)
Booting paravirtualized kernel on Xen
Xen version: 4.0.1 (preserve-AD) (dom0)
NR_CPUS:16 nr_cpumask_bits:16 nr_cpu_ids:4 nr_node_ids:1
PERCPU: Embedded 27 pages/cpu @ffff880028038000 s78552 r8192 d23848 u110592
pcpu-alloc: s78552 r8192 d23848 u110592 alloc=27*4096
pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Xen: using vcpu_info placement
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1744076
Kernel command line: root=/dev/sda2 console=hvc0
PID hash table entries: 4096 (order: 3, 32768 bytes)
Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Initializing CPU#0
DMA: Placing 64MB software IO TLB between ffff880020000000 -
ffff880024000000
DMA: software IO TLB at phys 0x20000000 - 0x24000000
xen_swiotlb_fixup: buf=ffff880020000000 size=67108864
xen_swiotlb_fixup: buf=ffff880024060000 size=32768
Memory: 6879112k/8151564k available (3188k kernel code, 1057760k absent,
214220k reserved, 2152k data, 456k init)
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is enabled.
NR_IRQS:1024
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
xen: sci override: source_irq=9 global_irq=9 trigger=c polarity=1
xen_allocate_pirq: returning irq 9 for gsi 9
xen: acpi sci 9
Console: colour VGA+ 80x25
console [hvc0] enabled
installing Xen timer for CPU 0
Detected 2133.464 MHz processor.
Calibrating delay loop (skipped), value calculated using timer
frequency.. 4266.92 BogoMIPS (lpj=21334640)
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 256K
CPU: L3 cache: 4096K
CPU: Unsupported number of siblings 16
mce: CPU supports 9 MCE banks
Performance Events: unsupported p6 CPU model 26 no PMU driver, software
events only.
SMP alternatives: switching to UP code
ACPI: Core revision 20090903
installing Xen timer for CPU 1
SMP alternatives: switching to SMP code
Initializing CPU#1
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 256K
CPU: L3 cache: 4096K
CPU: Unsupported number of siblings 16
installing Xen timer for CPU 2
Initializing CPU#2
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 256K
CPU: L3 cache: 4096K
CPU: Unsupported number of siblings 16
installing Xen timer for CPU 3
Initializing CPU#3
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 256K
CPU: L3 cache: 4096K
CPU: Unsupported number of siblings 16
Brought up 4 CPUs
xor: automatically using best checksumming function: generic_sse
generic_sse: 2180.000 MB/sec
xor: using function: generic_sse (2180.000 MB/sec)
Grant table initialized
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
PCI: MCFG area at e0000000 reserved in E820
PCI: Using MMCONFIG at e0000000 - efffffff
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ERROR: Unable to locate IOAPIC for GSI 9
ACPI Warning for \_SB_._OSC: Return type mismatch - found Integer,
expected Buffer (20090903/nspredef-1006)
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Interpreter enabled
ACPI: (supports S0 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI Warning: Incorrect checksum in table [OEMB] - 54, should be 51
(20090903/tbutils-314)
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
pci 0000:00:00.0: PME# disabled
pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: PME# disabled
pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
pci 0000:00:03.0: PME# disabled
pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
pci 0000:00:07.0: PME# disabled
pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
pci 0000:00:09.0: PME# disabled
pci 0000:00:13.0: PME# supported from D0 D3hot D3cold
pci 0000:00:13.0: PME# disabled
pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.7: PME# disabled
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.4: PME# disabled
pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.5: PME# disabled
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.0: quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
pci 0000:00:1f.0: quirk: region 0500-053f claimed by ICH6 GPIO
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0a00 (mask 00ff)
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 4700 (mask 00ff)
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 4 PIO at 0ca0 (mask 000f)
pci 0000:06:00.0: PME# supported from D0 D3hot D3cold
pci 0000:06:00.0: PME# disabled
pci 0000:07:00.0: PME# supported from D0 D3hot D3cold
pci 0000:07:00.0: PME# disabled
pci 0000:00:1e.0: transparent bridge
(XEN) PCI add device 00:00.0
(XEN) PCI add device 00:01.0
(XEN) PCI add device 00:03.0
(XEN) PCI add device 00:07.0
(XEN) PCI add device 00:09.0
(XEN) PCI add device 00:13.0
(XEN) PCI add device 00:14.0
(XEN) PCI add device 00:14.1
(XEN) PCI add device 00:14.2
(XEN) PCI add device 00:14.3
(XEN) PCI add device 00:16.0
(XEN) PCI add device 00:16.1
(XEN) PCI add device 00:16.2
(XEN) PCI add device 00:16.3
(XEN) PCI add device 00:16.4
(XEN) PCI add device 00:16.5
(XEN) PCI add device 00:16.6
(XEN) PCI add device 00:16.7
(XEN) PCI add device 00:1a.0
(XEN) PCI add device 00:1a.1
(XEN) PCI add device 00:1a.2
(XEN) PCI add device 00:1a.7
(XEN) PCI add device 00:1b.0
(XEN) PCI add device 00:1c.0
(XEN) PCI add device 00:1c.4
(XEN) PCI add device 00:1c.5
(XEN) PCI add device 00:1d.0
(XEN) PCI add device 00:1d.1
(XEN) PCI add device 00:1d.2
(XEN) PCI add device 00:1d.7
(XEN) PCI add device 00:1e.0
(XEN) PCI add device 00:1f.0
(XEN) PCI add device 00:1f.2
(XEN) PCI add device 00:1f.3
(XEN) PCI add device 00:1f.5
(XEN) PCI add device 04:00.0
(XEN) PCI add device 06:00.0
(XEN) PCI add device 07:00.0
(XEN) PCI add device 08:01.0
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 12 14 *15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 11 12 *14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 *7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 6 7 *10 11 12 14 15)
xen_balloon: Initialising balloon driver with page order 0.
vgaarb: device added: PCI:0000:08:01.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
SCSI subsystem initialized
raid6: int64x1 2129 MB/s
raid6: int64x2 2095 MB/s
raid6: int64x4 1825 MB/s
raid6: int64x8 1379 MB/s
raid6: sse2x1 4926 MB/s
raid6: sse2x2 5845 MB/s
raid6: sse2x4 6479 MB/s
raid6: using algorithm sse2x4 (6479 MB/s)
PCI: Using ACPI for IRQ routing
Switching to clocksource xen
pnp: PnP ACPI init
ACPI: bus type pnp registered
xen_allocate_pirq: returning irq 8 for gsi 8
xen_allocate_pirq: returning irq 12 for gsi 12
xen_allocate_pirq: returning irq 13 for gsi 13
xen_allocate_pirq: returning irq 4 for gsi 4
xen_allocate_pirq: returning irq 3 for gsi 3
Already setup the GSI :3
pnp: PnP ACPI: found 15 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: iomem range 0xfed1c000-0xfed1ffff has been reserved
system 00:07: ioport range 0xa10-0xa1f has been reserved
system 00:0a: ioport range 0xca2-0xca3 has been reserved
system 00:0a: ioport range 0xcf8-0xcff could not be reserved
system 00:0a: ioport range 0x4d0-0x4d1 has been reserved
system 00:0a: ioport range 0x800-0x87f has been reserved
system 00:0a: ioport range 0x500-0x57f could not be reserved
system 00:0a: iomem range 0x400-0x4ff could not be reserved
system 00:0a: iomem range 0xfed1c000-0xfed1ffff has been reserved
system 00:0a: iomem range 0xfed20000-0xfed3ffff has been reserved
system 00:0a: iomem range 0xfed40000-0xfed8ffff has been reserved
system 00:0c: iomem range 0xfec00000-0xfec00fff could not be reserved
system 00:0c: iomem range 0xfee00000-0xfee00fff has been reserved
system 00:0d: iomem range 0xe0000000-0xefffffff has been reserved
system 00:0e: iomem range 0xc0000-0xcffff could not be reserved
system 00:0e: iomem range 0xe0000-0xfffff could not be reserved
system 00:0e: iomem range 0xfed90000-0xffffffff could not be reserved
PM-Timer failed consistency check (0x0xffffff) - aborting.
pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
pci 0000:00:01.0: IO window: disabled
pci 0000:00:01.0: MEM window: disabled
pci 0000:00:01.0: PREFETCH window: disabled
pci 0000:00:03.0: PCI bridge, secondary bus 0000:02
pci 0000:00:03.0: IO window: disabled
pci 0000:00:03.0: MEM window: disabled
pci 0000:00:03.0: PREFETCH window: disabled
pci 0000:00 * No configuration specified; defaulting to DHCP
* dhcp ...
* Running dhcpcd ...
dhcpcd[846]: version 5.2.7 starting
dhcpcd[846]: eth0: waiting for carrier
dhcpcd[846]: eth0: carrier acquired
dhcpcd[846]: eth0: rebinding lease of 192.168.81.179
dhcpcd[846]: eth0: acknowledged 192.168.81.179 from 192.168.80.1
dhcpcd[846]: eth0: checking for 192.168.81.179
dhcpcd[846]: eth0: leased 192.168.81.179 for 86400 seconds
dhcpcd[846]: forked to background, child pid 888
[ ok ]
* received address 192.168.81.179/23
------8<------8<------8<------8<------8<------8<------8<------8<------8<
BB ~ # cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 26
model name : Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
stepping : 5
cpu MHz : 2133.472
cache size : 4096 KB
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat
clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good
nonstop_tsc aperfmperf pni est ssse3 cx16 sse4_1 sse4_2 popcnt
hypervisor lahf_lm
bogomips : 4266.94
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 26
model name : Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
stepping : 5
cpu MHz : 2133.472
cache size : 4096 KB
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat
clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good
nonstop_tsc aperfmperf pni est ssse3 cx16 sse4_1 sse4_2 popcnt
hypervisor lahf_lm
bogomips : 4266.94
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 26
model name : Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
stepping : 5
cpu MHz : 2133.472
cache size : 4096 KB
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat
clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good
nonstop_tsc aperfmperf pni est ssse3 cx16 sse4_1 sse4_2 popcnt
hypervisor lahf_lm
bogomips : 4266.94
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 26
model name : Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
stepping : 5
cpu MHz : 2133.472
cache size : 4096 KB
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat
clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good
nonstop_tsc aperfmperf pni est ssse3 cx16 sse4_1 sse4_2 popcnt
hypervisor lahf_lm
bogomips : 4266.94
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
------8<------8<------8<------8<------8<------8<------8<------8<------8<
# lshw
bb
description: System
product: X8DTL
vendor: Supermicro
version: 1234567890
serial: 1234567890
width: 64 bits
capabilities: smbios-2.6 dmi-2.6 vsyscall64 vsyscall32
configuration: boot=normal chassis=server
uuid=534D4349-0002-0990-2500-09902500EB70
*-core
description: Motherboard
product: X8DTL
vendor: Supermicro
physical id: 0
version: 1234567890
serial: 1234567890
slot: To Be Filled By O.E.M.
*-firmware
description: BIOS
vendor: American Megatrends Inc.
physical id: 0
version: 2.0 (05/28/2010)
size: 64KiB
capacity: 4032KiB
capabilities: isa pci pnp upgrade shadowing escd cdboot
bootselect socketedrom edd int13floppy1200 int13floppy720
int13floppy2880 int5printscreen int9keyboard int14serial int17printer
int10video acpi usb ls120boot zipboot biosbootspecification
*-cpu:0
description: CPU
product: Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
serial: To Be Filled By O.E.M.
slot: CPU 1
size: 2133MHz
capacity: 2133MHz
width: 64 bits
clock: 133MHz
capabilities: fpu fpu_exception wp de tsc msr pae mce cx8 apic
sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx
x86-64 constant_tsc rep_good nonstop_tsc aperfmperf pni est ssse3 cx16
sse4_1 sse4_2 popcnt hypervisor lahf_lm
*-cache:0
description: L1 cache
physical id: 5
slot: L1-Cache
size: 256KiB
capacity: 256KiB
capabilities: internal write-through instruction
*-cache:1
description: L2 cache
physical id: 6
slot: L2-Cache
size: 1MiB
capacity: 1MiB
capabilities: internal write-through unified
*-cache:2
description: L3 cache
physical id: 7
slot: L3-Cache
size: 4MiB
capacity: 4MiB
capabilities: internal write-back unified
*-cpu:1 DISABLED
description: CPU [empty]
product: (To Be Filled By O.E.M.)
physical id: 8
serial: To Be Filled By O.E.M.
slot: CPU 2
*-memory:0
description: System Memory
physical id: 2d
slot: System board or motherboard
*-bank:0
description: DIMM [empty]
product: ModulePartNumber00
vendor: Manufacturer00
physical id: 0
serial: SerNum00
slot: P2_DIMM1A
width: 64 bits
*-bank:1
description: DIMM [empty]
product: ModulePartNumber01
vendor: Manufacturer01
physical id: 1
serial: SerNum01
slot: P2_DIMM2A
width: 64 bits
*-bank:2
description: DIMM [empty]
product: ModulePartNumber02
vendor: Manufacturer02
physical id: 2
serial: SerNum02
slot: P2_DIMM3A
width: 64 bits
*-memory:1
description: System Memory
physical id: 35
slot: System board or motherboard
*-bank:0
description: DIMM 800 MHz (1.2 ns)
product: M393B5170EH1-CH9
vendor: Samsung
physical id: 0
serial: 85201546
slot: P1_DIMM1A
size: 4GiB
width: 64 bits
clock: 800MHz (1.2ns)
*-bank:1
description: DIMM 800 MHz (1.2 ns)
product: M393B5170EH1-CH9
vendor: Samsung
physical id: 1
serial: E6201546
slot: P1_DIMM2A
size: 4GiB
width: 64 bits
clock: 800MHz (1.2ns)
*-bank:2
description: DIMM [empty]
product: ModulePartNumber05
vendor: Manufacturer05
physical id: 2
serial: SerNum05
slot: P1_DIMM3A
width: 64 bits
*-memory:2 UNCLAIMED
description: Flash Memory
physical id: 3d
slot: System board or motherboard
capacity: 4MiB
*-bank UNCLAIMED
description: FLASH Non-volatile 33 MHz (30.3 ns)
product: 25L3205
vendor: MXIC
physical id: 0
slot: BIOS
size: 4MiB
width: 8 bits
clock: 33MHz (30.3ns)
*-memory:3 UNCLAIMED
physical id: 1
*-memory:4 UNCLAIMED
physical id: 2
*-cpu:2
product: Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
vendor: Intel Corp.
physical id: 3
bus info: cpu@1
width: 64 bits
capabilities: fpu fpu_exception wp de tsc msr pae mce cx8 apic
sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx
x86-64 constant_tsc rep_good nonstop_tsc aperfmperf pni est ssse3 cx16
sse4_1 sse4_2 popcnt hypervisor lahf_lm
*-cpu:3
product: Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
vendor: Intel Corp.
physical id: 5
bus info: cpu@2
width: 64 bits
capabilities: fpu fpu_exception wp de tsc msr pae mce cx8 apic
sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx
x86-64 constant_tsc rep_good nonstop_tsc aperfmperf pni est ssse3 cx16
sse4_1 sse4_2 popcnt hypervisor lahf_lm
*-cpu:4
product: Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
vendor: Intel Corp.
physical id: 6
bus info: cpu@3
width: 64 bits
capabilities: fpu fpu_exception wp de tsc msr pae mce cx8 apic
sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx
x86-64 constant_tsc rep_good nonstop_tsc aperfmperf pni est ssse3 cx16
sse4_1 sse4_2 popcnt hypervisor lahf_lm
*-pci
description: Host bridge
product: 5500 I/O Hub to ESI Port
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 22
width: 32 bits
clock: 33MHz
*-pci:0
description: PCI bridge
product: 5520/5500/X58 I/O Hub PCI Express Root Port 1
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:00:01.0
version: 22
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode
bus_master cap_list
*-pci:1
description: PCI bridge
product: 5520/5500/X58 I/O Hub PCI Express Root Port 3
vendor: Intel Corporation
physical id: 3
bus info: pci@0000:00:03.0
version: 22
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode
bus_master cap_list
*-pci:2
description: PCI bridge
product: 5520/5500/X58 I/O Hub PCI Express Root Port 7
vendor: Intel Corporation
physical id: 7
bus info: pci@0000:00:07.0
version: 22
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode
bus_master cap_list
*-pci:3
description: PCI bridge
product: 5520/5500/X58 I/O Hub PCI Express Root Port 9
vendor: Intel Corporation
physical id: 9
bus info: pci@0000:00:09.0
version: 22
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode
bus_master cap_list
resources: ioport:c000(size=4096) memory:fbb00000-fbbfffff
*-storage
description: RAID bus controller
product: MegaRAID SAS 1078
vendor: LSI Logic / Symbios Logic
physical id: 0
bus info: pci@0000:04:00.0
logical name: scsi0
version: 04
width: 64 bits
clock: 33MHz
capabilities: storage pciexpress msi msix pm vpd
bus_master cap_list rom
configuration: driver=megaraid_sas latency=0
resources: irq:32 memory:fbbc0000-fbbfffff
ioport:c000(size=256) memory:fbb80000-fbbbffff
memory:fbb60000-fbb7ffff(prefetchable)
*-disk
description: SCSI Disk
product: MegaRAID 8708EM2
vendor: LSI
physical id: 2.0.0
bus info: scsi@0:2.0.0
logical name: /dev/sda
version: 1.40
serial: 00faf2d1068c212a1480d61902b00506
size: 5582GiB (5993GB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: ansiversion=5
guid=7b9f13db-157a-4ad4-9bd1-36abf9889475
*-volume:0
description: Data partition
vendor: Linux
physical id: 1
bus info: scsi@0:2.0.0,1
logical name: /dev/sda1
logical name: /boot
version: 1.0
serial: 92bcd77b-7e91-4adf-997b-32386954d21c
size: 32MiB
capabilities: extended_attributes ext2 initialized
configuration: filesystem=ext2 modified=2010-10-06
16:48:42 mount.fstype=ext2 mount.options=rw,relatime,errors=continue
mounted=2010-10-05 16:19:56 name=boot state=mounted
*-volume:1
description: Data partition
vendor: Linux
physical id: 2
bus info: scsi@0:2.0.0,2
logical name: /dev/sda2
logical name: /
version: 1.0
serial: 3cbcb27b-db12-45d2-97aa-0646b7458217
size: 224MiB
capabilities: extended_attributes ext2 initialized
configuration: filesystem=ext2 modified=2010-10-07
08:51:13 mount.fstype=ext2 mount.options=rw,relatime,errors=continue
mounted=2010-09-29 12:17:35 name=root state=mounted
*-volume:2
description: Linux swap volume
physical id: 3
bus info: scsi@0:2.0.0,3
logical name: /dev/sda3
version: 1
serial: 217c9e7e-3d31-40a9-95dc-7a4869532410
size: 8190MiB
capacity: 8191MiB
capabilities: nofs swap initialized
configuration: filesystem=swap name=swap pagesize=4095
*-volume:3
description: Linux LVM Physical Volume
physical id: 4
bus info: scsi@0:2.0.0,4
logical name: /dev/sda4
serial: tMx36k-sx52-OlZV-g6fn-jCeu-tKSZ-wiEVW2
size: 5574GiB
capabilities: multi lvm2
configuration: name=Linux LVM
*-generic:0 UNCLAIMED
description: PIC
product: 5520/5500/X58 I/O Hub I/OxAPIC Interrupt Controller
vendor: Intel Corporation
physical id: 13
bus info: pci@0000:00:13.0
version: 22
width: 32 bits
clock: 33MHz
capabilities: pm io_x_-apic bus_master cap_list
configuration: latency=0
resources: memory:fec8a000-fec8afff
*-generic:1 UNCLAIMED
description: PIC
product: 5520/5500/X58 I/O Hub System Management Registers
vendor: Intel Corporation
physical id: 14
bus info: pci@0000:00:14.0
version: 22
width: 32 bits
clock: 33MHz
capabilities: pciexpress 8259 cap_list
configuration: latency=0
*-generic:2 UNCLAIMED
description: PIC
product: 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers
vendor: Intel Corporation
physical id: 14.1
bus info: pci@0000:00:14.1
version: 22
width: 32 bits
clock: 33MHz
capabilities: pciexpress 8259 cap_list
configuration: latency=0
*-generic:3 UNCLAIMED
description: PIC
product: 5520/5500/X58 I/O Hub Control Status and RAS Registers
vendor: Intel Corporation
physical id: 14.2
bus info: pci@0000:00:14.2
version: 22
width: 32 bits
clock: 33MHz
capabilities: pciexpress 8259 cap_list
configuration: latency=0
*-generic:4 UNCLAIMED
description: PIC
product: 5520/5500/X58 I/O Hub Throttle Registers
vendor: Intel Corporation
physical id: 14.3
bus info: pci@0000:00:14.3
version: 22
width: 32 bits
clock: 33MHz
capabilities: 8259
configuration: latency=0
*-generic:5
description: System peripheral
product: 5520/5500/X58 Chipset QuickData Technology Device
vendor: Intel Corporation
physical id: 16
bus info: pci@0000:00:16.0
version: 22
width: 64 bits
clock: 33MHz
capabilities: msix pciexpress pm bus_master cap_list
configuration: driver=ioatdma latency=0
resources: irq:43 memory:fbef8000-fbefbfff
*-generic:6
description: System peripheral
product: 5520/5500/X58 Chipset QuickData Technology Device
vendor: Intel Corporation
physical id: 16.1
bus info: pci@0000:00:16.1
version: 22
width: 64 bits
clock: 33MHz
capabilities: msix pciexpress pm bus_master cap_list
configuration: driver=ioatdma latency=0
resources: irq:44 memory:fbef4000-fbef7fff
*-generic:7
description: System peripheral
product: 5520/5500/X58 Chipset QuickData Technology Device
vendor: Intel Corporation
physical id: 16.2
bus info: pci@0000:00:16.2
version: 22
width: 64 bits
clock: 33MHz
capabilities: msix pciexpress pm bus_master cap_list
configuration: driver=ioatdma latency=0
resources: irq:45 memory:fbef0000-fbef3fff
*-generic:8
description: System peripheral
product: 5520/5500/X58 Chipset QuickData Technology Device
vendor: Intel Corporation
physical id: 16.3
bus info: pci@0000:00:16.3
version: 22
width: 64 bits
clock: 33MHz
capabilities: msix pciexpress pm bus_master cap_list
configuration: driver=ioatdma latency=0
resources: irq:46 memory:fbeec000-fbeeffff
*-generic:9
description: System peripheral
product: 5520/5500/X58 Chipset QuickData Technology Device
vendor: Intel Corporation
physical id: 16.4
bus info: pci@0000:00:16.4
version: 22
width: 64 bits
clock: 33MHz
capabilities: msix pciexpress pm bus_master cap_list
configuration: driver=ioatdma latency=0
resources: irq:43 memory:fbee8000-fbeebfff
*-generic:10
description: System peripheral
product: 5520/5500/X58 Chipset QuickData Technology Device
vendor: Intel Corporation
physical id: 16.5
bus info: pci@0000:00:16.5
version: 22
width: 64 bits
clock: 33MHz
capabilities: msix pciexpress pm bus_master cap_list
configuration: driver=ioatdma latency=0
resources: irq:44 memory:fbee4000-fbee7fff
*-generic:11
description: System peripheral
product: 5520/5500/X58 Chipset QuickData Technology Device
vendor: Intel Corporation
physical id: 16.6
bus info: pci@0000:00:16.6
version: 22
width: 64 bits
clock: 33MHz
capabilities: msix pciexpress pm bus_master cap_list
configuration: driver=ioatdma latency=0
resources: irq:45 memory:fbee0000-fbee3fff
*-generic:12
description: System peripheral
product: 5520/5500/X58 Chipset QuickData Technology Device
vendor: Intel Corporation
physical id: 16.7
bus info: pci@0000:00:16.7
version: 22
width: 64 bits
clock: 33MHz
capabilities: msix pciexpress pm bus_master cap_list
configuration: driver=ioatdma latency=0
resources: irq:46 memory:fbedc000-fbedffff
*-usb:0
description: USB Controller
product: 82801JI (ICH10 Family) USB UHCI Controller #4
vendor: Intel Corporation
physical id: 1a
bus info: pci@0000:00:1a.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master cap_list
configuration: driver=uhci_hcd latency=0
resources: irq:16 ioport:bc00(size=32)
*-usb:1
description: USB Controller
product: 82801JI (ICH10 Family) USB UHCI Controller #5
vendor: Intel Corporation
physical id: 1a.1
bus info: pci@0000:00:1a.1
version: 00
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master cap_list
configuration: driver=uhci_hcd latency=0
resources: irq:21 ioport:b880(size=32)
*-usb:2
description: USB Controller
product: 82801JI (ICH10 Family) USB UHCI Controller #6
vendor: Intel Corporation
physical id: 1a.2
bus info: pci@0000:00:1a.2
version: 00
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master cap_list
configuration: driver=uhci_hcd latency=0
resources: irq:19 ioport:b800(size=32)
*-usb:3
description: USB Controller
product: 82801JI (ICH10 Family) USB2 EHCI Controller #2
vendor: Intel Corporation
physical id: 1a.7
bus info: pci@0000:00:1a.7
version: 00
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci_hcd latency=0
resources: irq:18 memory:fbeda000-fbeda3ff
*-multimedia UNCLAIMED
description: Audio device
product: 82801JI (ICH10 Family) HD Audio Controller
vendor: Intel Corporation
physical id: 1b
bus info: pci@0000:00:1b.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: latency=0
resources: memory:fbed4000-fbed7fff
*-pci:4
description: PCI bridge
product: 82801JI (ICH10 Family) PCI Express Port 1
vendor: Intel Corporation
physical id: 1c
bus info: pci@0000:00:1c.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode
bus_master cap_list
configuration: driver=pcieport
resources: irq:17 ioport:1000(size=4096)
memory:c0000000-c01fffff memory:c0200000-c03fffff(prefetchable)
*-pci:5
description: PCI bridge
product: 82801JI (ICH10 Family) PCI Express Port 5
vendor: Intel Corporation
physical id: 1c.4
bus info: pci@0000:00:1c.4
version: 00
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode
bus_master cap_list
configuration: driver=pcieport
resources: irq:17 ioport:d000(size=4096)
memory:fbc00000-fbcfffff memory:c0400000-c05fffff(prefetchable)
*-network
description: Ethernet interface
product: 82574L Gigabit Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:06:00.0
logical name: peth0
version: 00
serial: 00:25:90:09:70:ea
size: 100MB/s
capacity: 1GB/s
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes
driver=e1000e driverversion=1.0.2-k2 duplex=full firmware=1.8-0
latency=0 link=yes multicast=yes port=twisted pair promiscuous=yes
speed=100MB/s
resources: irq:16 memory:fbce0000-fbcfffff
ioport:dc00(size=32) memory:fbcdc000-fbcdffff
*-pci:6
description: PCI bridge
product: 82801JI (ICH10 Family) PCI Express Port 6
vendor: Intel Corporation
physical id: 1c.5
bus info: pci@0000:00:1c.5
version: 00
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode
bus_master cap_list
configuration: driver=pcieport
resources: irq:16 ioport:e000(size=4096)
memory:fbd00000-fbdfffff memory:c0600000-c07fffff(prefetchable)
*-network DISABLED
description: Ethernet interface
product: 82574L Gigabit Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:07:00.0
logical name: eth1
version: 00
serial: 00:25:90:09:70:eb
capacity: 1GB/s
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes
driver=e1000e driverversion=1.0.2-k2 firmware=1.8-0 latency=0 link=no
multicast=yes port=twisted pair
resources: irq:17 memory:fbde0000-fbdfffff
ioport:ec00(size=32) memory:fbddc000-fbddffff
*-usb:4
description: USB Controller
product: 82801JI (ICH10 Family) USB UHCI Controller #1
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:00:1d.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master cap_list
configuration: driver=uhci_hcd latency=0
resources: irq:23 ioport:b480(size=32)
*-usb:5
description: USB Controller
product: 82801JI (ICH10 Family) USB UHCI Controller #2
vendor: Intel Corporation
physical id: 1d.1
bus info: pci@0000:00:1d.1
version: 00
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master cap_list
configuration: driver=uhci_hcd latency=0
resources: irq:19 ioport:b400(size=32)
*-usb:6
description: USB Controller
product: 82801JI (ICH10 Family) USB UHCI Controller #3
vendor: Intel Corporation
physical id: 1d.2
bus info: pci@0000:00:1d.2
version: 00
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master cap_list
configuration: driver=uhci_hcd latency=0
resources: irq:18 ioport:b080(size=32)
*-usb:7
description: USB Controller
product: 82801JI (ICH10 Family) USB2 EHCI Controller #1
vendor: Intel Corporation
physical id: 1d.7
bus info: pci@0000:00:1d.7
version: 00
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci_hcd latency=0
resources: irq:23 memory:fbed8000-fbed83ff
*-pci:7
description: PCI bridge
product: 82801 PCI Bridge
vendor: Intel Corporation
physical id: 1e
bus info: pci@0000:00:1e.0
version: 90
width: 32 bits
clock: 33MHz
capabilities: pci subtractive_decode bus_master cap_list
resources: memory:faf00000-fb7fffff
ioport:f9000000(size=16777216)
*-display UNCLAIMED
description: VGA compatible controller
product: MGA G200eW WPCM450
vendor: Matrox Graphics, Inc.
physical id: 1
bus info: pci@0000:08:01.0
version: 0a
width: 32 bits
clock: 33MHz
capabilities: pm vga_controller bus_master cap_list
configuration: latency=64 maxlatency=32 mingnt=16
resources: memory:f9000000-f9ffffff(prefetchable)
memory:faffc000-faffffff memory:fb000000-fb7fffff
*-isa
description: ISA bridge
product: 82801JIR (ICH10R) LPC Interface Controller
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: isa bus_master cap_list
configuration: latency=0
*-ide:0 UNCLAIMED
description: IDE interface
product: 82801JI (ICH10 Family) 4 port SATA IDE Controller
vendor: Intel Corporation
physical id: 1f.2
bus info: pci@0000:00:1f.2
version: 00
width: 32 bits
clock: 66MHz
capabilities: ide pm bus_master cap_list
configuration: latency=0
resources: ioport:b000(size=8) ioport:ac00(size=4)
ioport:a880(size=8) ioport:a800(size=4) ioport:a480(size=16)
ioport:a400(size=16)
*-serial
description: SMBus
product: 82801JI (ICH10 Family) SMBus Controller
vendor: Intel Corporation
physical id: 1f.3
bus info: pci@0000:00:1f.3
version: 00
width: 64 bits
clock: 33MHz
configuration: driver=i801_smbus latency=0
resources: irq:18 memory:fbed2000-fbed20ff ioport:400(size=32)
*-ide:1 UNCLAIMED
description: IDE interface
product: 82801JI (ICH10 Family) 2 port SATA IDE Controller
vendor: Intel Corporation
physical id: 1f.5
bus info: pci@0000:00:1f.5
version: 00
width: 32 bits
clock: 66MHz
capabilities: ide pm bus_master cap_list
configuration: latency=0
resources: ioport:a000(size=8) ioport:9c00(size=4)
ioport:9880(size=8) ioport:9800(size=4) ioport:9480(size=16)
ioport:9400(size=16)
------8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------
# dmidecode 2.10
SMBIOS 2.6 present.
70 structures occupying 2848 bytes.
Table at 0x00099C00.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 2.0
Release Date: 05/28/2010
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 4096 kB
Characteristics:
ISA is supported
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
BIOS Revision: 8.16
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Supermicro
Product Name: X8DTL
Version: 1234567890
Serial Number: 1234567890
UUID: 49434D53-0200-9009-2500-09902500EB70
Wake-up Type: Power Switch
SKU Number: To Be Filled By O.E.M.
Family: Server
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Supermicro
Product Name: X8DTL
Version: 1234567890
Serial Number: 1234567890
Asset Tag: To Be Filled By O.E.M.
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: To Be Filled By O.E.M.
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
Handle 0x0003, DMI type 3, 21 bytes
Chassis Information
Manufacturer: Supermicro
Type: Main Server Chassis
Lock: Not Present
Version: 1234567890
Serial Number: 1234567890
Asset Tag: To Be Filled By O.E.M.
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
Handle 0x0004, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU 1
Type: Central Processor
Family: Xeon
Manufacturer: Intel
ID: A5 06 01 00 FF FB EB BF
Signature: Type 0, Family 6, Model 26, Stepping 5
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (Fast floating-point save and restore)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Hyper-threading technology)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
Voltage: Unknown
External Clock: 133 MHz
Max Speed: 2133 MHz
Current Speed: 2133 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: 0x0005
L2 Cache Handle: 0x0006
L3 Cache Handle: 0x0007
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 4
Core Enabled: 4
Thread Count: 4
Characteristics:
64-bit capable
Handle 0x0005, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1-Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Through
Location: Internal
Installed Size: 256 kB
Maximum Size: 256 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Parity
System Type: Instruction
Associativity: 4-way Set-associative
Handle 0x0006, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2-Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Through
Location: Internal
Installed Size: 1024 kB
Maximum Size: 1024 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 8-way Set-associative
Handle 0x0007, DMI type 7, 19 bytes
Cache Information
Socket Designation: L3-Cache
Configuration: Enabled, Not Socketed, Level 3
Operational Mode: Write Back
Location: Internal
Installed Size: 4096 kB
Maximum Size: 4096 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 16-way Set-associative
Handle 0x0008, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU 2
Type: Central Processor
Family: Xeon
Manufacturer:
ID: 00 00 00 00 00 00 00 00
Signature: Type 0, Family 0, Model 0, Stepping 0
Flags: None
Version:
Voltage: 3.3 V 2.9 V
External Clock: Unknown
Max Speed: 2000 MHz
Current Speed: Unknown
Status: Unpopulated
Upgrade: Other
L1 Cache Handle: 0x0009
L2 Cache Handle: 0x000A
L3 Cache Handle: 0x000B
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Characteristics: None
Handle 0x0009, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1-Cache
Configuration: Disabled, Not Socketed, Level 1
Operational Mode: Unknown
Location: Internal
Installed Size: 0 kB
Maximum Size: 0 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x000A, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2-Cache
Configuration: Disabled, Not Socketed, Level 2
Operational Mode: Unknown
Location: Internal
Installed Size: 0 kB
Maximum Size: 0 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x000B, DMI type 7, 19 bytes
Cache Information
Socket Designation: L3-Cache
Configuration: Disabled, Not Socketed, Level 3
Operational Mode: Unknown
Location: Internal
Installed Size: 0 kB
Maximum Size: 0 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: PS2Mouse
External Connector Type: PS/2
Port Type: Mouse Port
Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: PS/2
Port Type: Keyboard Port
Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2
Internal Connector Type: None
External Reference Designator: USB1
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2
Internal Connector Type: None
External Reference Designator: USB2
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J4A1
Internal Connector Type: None
External Reference Designator: LPT 1
External Connector Type: DB-25 male
Port Type: Parallel Port ECP/EPP
Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A1
Internal Connector Type: None
External Reference Designator: COM A
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6A1
Internal Connector Type: None
External Reference Designator: Audio Mic In
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6A1
Internal Connector Type: None
External Reference Designator: Audio Line In
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6B1 - AUX IN
Internal Connector Type: On Board Sound Input From CD-ROM
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Audio Port
Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6B2 - CDIN
Internal Connector Type: On Board Sound Input From CD-ROM
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Audio Port
Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6J2 - PRI IDE
Internal Connector Type: On Board IDE
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6J1 - SEC IDE
Internal Connector Type: On Board IDE
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0018, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J4J1 - FLOPPY
Internal Connector Type: On Board Floppy
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0019, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9H1 - FRONT PNL
Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1B1 - CHASSIS REAR FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2F1 - CPU FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J8B4 - FRONT FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9G2 - FNT USB
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6C3 - FP AUD
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9G1 - CONFIG
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0020, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J8C1 - SCSI LED
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0021, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9J2 - INTRUDER
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0022, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9G4 - ITP
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0023, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2H1 - MAIN POWER
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0024, DMI type 9, 17 bytes
System Slot Information
Designation: PCI1
Type: 32-bit PCI
Current Usage: Available
Length: Short
ID: 1
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Handle 0x0025, DMI type 9, 17 bytes
System Slot Information
Designation: PCI2
Type: 32-bit PCI
Current Usage: Available
Length: Short
ID: 2
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Handle 0x0026, DMI type 9, 17 bytes
System Slot Information
Designation: PCIE3
Type: x4 PCI Express x8
Current Usage: Available
Length: Long
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Handle 0x0027, DMI type 9, 17 bytes
System Slot Information
Designation: PCIE4
Type: x4 PCI Express x8
Current Usage: In Use
Length: Short
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Handle 0x0028, DMI type 9, 17 bytes
System Slot Information
Designation: PCIE5
Type: x4 PCI Express x8
Current Usage: Available
Length: Long
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Handle 0x0029, DMI type 9, 17 bytes
System Slot Information
Designation: PCIE6
Type: x16 PCI Express x16
Current Usage: Available
Length: Long
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Handle 0x002A, DMI type 11, 5 bytes
OEM Strings
String 1: Intel Nehalem/Tylersburg/ICH10
String 2: Supermicro motherboard-X8 Series
Handle 0x002B, DMI type 13, 22 bytes
BIOS Language Information
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x002C, DMI type 15, 55 bytes
System Event Log
Area Length: 1008 bytes
Header Start Offset: 0x0810
Data Start Offset: 0x0810
Access Method: General-purpose non-volatile data functions
Access Address: 0x0001
Status: Valid, Not Full
Change Token: 0x00000000
Header Format: No Header
Supported Log Type Descriptors: 15
Descriptor 1: OEM-specific
Data Format 1: Multiple-event handle
Descriptor 2: OEM-specific
Data Format 2: Multiple-event handle
Descriptor 3: Single-bit ECC memory error
Data Format 3: Multiple-event handle
Descriptor 4: Multi-bit ECC memory error
Data Format 4: Multiple-event handle
Descriptor 5: Parity memory error
Data Format 5: Multiple-event
Descriptor 6: I/O channel block
Data Format 6: Multiple-event
Descriptor 7: POST error
Data Format 7: POST results bitmap
Descriptor 8: PCI parity error
Data Format 8: Multiple-event handle
Descriptor 9: PCI system error
Data Format 9: Multiple-event handle
Descriptor 1
--
Alan J. Wylie http://www.wylie.me.uk/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Alan J. Wylie
2010-Oct-07 10:25 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
P.S. kernel config is at http://www.wylie.me.uk/tmp/config.20101007a -- Alan J. Wylie http://www.wylie.me.uk/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Alan J. Wylie
2010-Oct-08 14:08 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
disabling ACPI doesn''t help Command line: root=/dev/sda2 console=hvc0 earlyprintk=xen acpi=off ... (XEN) Domain 0 crashed: ''noreboot'' set - not rebooting. (XEN) Command line: com2=19200,8n1 console=com2 noreboot acpi=off ... (XEN) Domain 0 crashed: ''noreboot'' set - not rebooting. My attempt to decode the stack trace> (XEN) Guest stack trace from rsp=ffffffff81449c10: > (XEN) 0000000000000000 00000000000003bf 0000000000000000 ffffffff8100bd47get_phys_to_machine=ffffffff8100bd10> (XEN) 000000010000e030 0000000000010006 ffffffff81449c58 000000000000e02birq_desc=ffffffff81446200> (XEN) 0000000000000020 ffffffff8100be83 800000000265a063 ffffffff8100c000lookup_pte_fn=ffffffff8100bdf9 xen_make_pte=ffffffff8100bf83> (XEN) 0000000000000000 ffffffff8100b789 00000000000003bf ffffffff815593e0lookup_pte_fn=ffffffff8100bdf9 futex_queues=ffffffff815572e0> (XEN) 000000000000000f 8000000000000163 800000000265a063 ffffffffff400000> (XEN) ffffffff8153a000 000000026fc17000 ffffffff814e2197 00000000000003bfalloc_large_system_hash=ffffffff814e2184> (XEN) ffffffff815593e0 ffffffffff400000 00000001815593e0 0000000000000000futex_queues=ffffffff815572e0> (XEN) ffffffff81449d90 000000000265a000 ffff88026fc17000 000000026fc17000irq_desc=ffffffff81446200> (XEN) 000000026fc17000 0000000000000000 ffffffff8130aef8 ffff880001002020quirk_vt8235_acpi=ffffffff8130ae9e> (XEN) 0000000100000000 ffff88026fc17000 ffffffff814fc1ba 0000000000000001map.24260=ffffffff814fba20> (XEN) ffffffff814c70a0 8000000000000163 0000000000000000 0000000000000004init_per_cpu__gdt_page=ffffffff814bc000> (XEN) 0000000000000000 0000000000000000 ffff880001002000 ffffffff8100b76b__raw_callee_save_xen_pgd_val=ffffffff8100b75a> (XEN) 00000000000003bf ffffffff815593e0 ffffffff81001880 000000026fc17000futex_queues=ffffffff815572e0 init_level4_pgt=ffffffff81001000> (XEN) ffff88026fc17000 ffffffff813ca5c5 ffff88026fc17000 0000000000000000> (XEN) ffffffff814fc363 000000026fc17000 ffffffff8131c16d 0000000000000020map.24260=ffffffff814fba20> (XEN) ffff880100000000 ffffffff81449e08 00000000bf780000 00000000bf780000irq_desc=ffffffff81446200> (XEN) ffffffff81449e78 0000000000000001 0000000000000001 ffffffff813ca5c5irq_desc=ffffffff81446200> (XEN) 0000000000000000 000000026fc17000 ffffffff8130ad22 0000000000000000quirk_ati_exploding_mce=ffffffff8130ad15> (XEN) 0000000000000000 ffffffff00000000 0000000100000000 ffff880000000000> (XEN) 0000000000000000 0000000100000000 000000026fc17000 0000000000000000-- Alan J. Wylie http://www.wylie.me.uk/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Andreas Kinzler
2010-Oct-12 08:10 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On 07.10.2010 11:57, Alan J. Wylie wrote:> System: Supermicro SM-SC825TQ-R720LPB, 8GB RAM > Motherboard: X8DTL > Processor: 1 x Intel XEON E5506 quad core > RAID controller: LSI MegaRAID SAS 8708 > > Bisected (by hand) to between > 69e50db2 (good) 2.6.32.21 "Merge commit ''v2.6.32.21'' into xen/next-2.6.32" > and > dda56688 (bad) "Merge branch ''xen/next'' into xen/next-2.6.32" > > ffffffff8100bd10 T get_phys_to_machine > ffffffff8100bd4c t pin_pagetable_pfnI am afflicted by this problem for a long while now. Should look very familiar to you. See http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00758.html No solution till now. Regards Andreas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Oct-12 18:49 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On 10/12/2010 01:10 AM, Andreas Kinzler wrote:> On 07.10.2010 11:57, Alan J. Wylie wrote: >> System: Supermicro SM-SC825TQ-R720LPB, 8GB RAM >> Motherboard: X8DTL >> Processor: 1 x Intel XEON E5506 quad core >> RAID controller: LSI MegaRAID SAS 8708 >> >> Bisected (by hand) to between >> 69e50db2 (good) 2.6.32.21 "Merge commit ''v2.6.32.21'' into >> xen/next-2.6.32" >> and >> dda56688 (bad) "Merge branch ''xen/next'' into >> xen/next-2.6.32" >> >> ffffffff8100bd10 T get_phys_to_machine >> ffffffff8100bd4c t pin_pagetable_pfn > > I am afflicted by this problem for a long while now. Should look very > familiar to you. See > http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00758.html > > No solution till now.Is it not fixed by current xen/stable-2.6.32.x kernels? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Valtteri Kiviniemi
2010-Oct-12 20:02 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
Hi, I just compiled Xen 4.0.0.1 with 2.6.32.24 and I stuck on this same problem with my own compiled kernel. However the default kernel with comes from "make world" boots fine. I traced the problem down to some settings in kernel''s menuconfig "Kernel hacking" menu. I dont exactly know what the option needs to be enabled in the "Kernel hacking" to get the kernel booting. In my own compiled kernels I have almost all the options in that "Kernel hacking" menu disabled, and when I enabled the same options in that menu that are in the default kernel which comes when you do "make world" the system booted fine. You probably know the problem already but I just thought that I should share this information with you anyway. - Valtteri Kiviniemi Jeremy Fitzhardinge kirjoitti:> On 10/12/2010 01:10 AM, Andreas Kinzler wrote: >> On 07.10.2010 11:57, Alan J. Wylie wrote: >>> System: Supermicro SM-SC825TQ-R720LPB, 8GB RAM >>> Motherboard: X8DTL >>> Processor: 1 x Intel XEON E5506 quad core >>> RAID controller: LSI MegaRAID SAS 8708 >>> >>> Bisected (by hand) to between >>> 69e50db2 (good) 2.6.32.21 "Merge commit ''v2.6.32.21'' into >>> xen/next-2.6.32" >>> and >>> dda56688 (bad) "Merge branch ''xen/next'' into >>> xen/next-2.6.32" >>> >>> ffffffff8100bd10 T get_phys_to_machine >>> ffffffff8100bd4c t pin_pagetable_pfn >> I am afflicted by this problem for a long while now. Should look very >> familiar to you. See >> http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00758.html >> >> No solution till now. > > Is it not fixed by current xen/stable-2.6.32.x kernels? > > J > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Oct-13 00:26 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On 10/12/2010 01:02 PM, Valtteri Kiviniemi wrote:> Hi, > > I just compiled Xen 4.0.0.1 with 2.6.32.24 and I stuck on this same > problem with my own compiled kernel. However the default kernel with > comes from "make world" boots fine. I traced the problem down to some > settings in kernel''s menuconfig "Kernel hacking" menu. I dont exactly > know what the option needs to be enabled in the "Kernel hacking" to > get the kernel booting. In my own compiled kernels I have almost all > the options in that "Kernel hacking" menu disabled, and when I enabled > the same options in that menu that are in the default kernel which > comes when you do "make world" the system booted fine. > > You probably know the problem already but I just thought that I should > share this information with you anyway.No, that''s interesting. So some kernel debugging config option makes the problem go away? That gives me some way to possibly repro the problem. J> > - Valtteri Kiviniemi > > Jeremy Fitzhardinge kirjoitti: >> On 10/12/2010 01:10 AM, Andreas Kinzler wrote: >>> On 07.10.2010 11:57, Alan J. Wylie wrote: >>>> System: Supermicro SM-SC825TQ-R720LPB, 8GB RAM >>>> Motherboard: X8DTL >>>> Processor: 1 x Intel XEON E5506 quad core >>>> RAID controller: LSI MegaRAID SAS 8708 >>>> >>>> Bisected (by hand) to between >>>> 69e50db2 (good) 2.6.32.21 "Merge commit ''v2.6.32.21'' into >>>> xen/next-2.6.32" >>>> and >>>> dda56688 (bad) "Merge branch ''xen/next'' into >>>> xen/next-2.6.32" >>>> >>>> ffffffff8100bd10 T get_phys_to_machine >>>> ffffffff8100bd4c t pin_pagetable_pfn >>> I am afflicted by this problem for a long while now. Should look very >>> familiar to you. See >>> http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00758.html >>> >>> >>> No solution till now. >> >> Is it not fixed by current xen/stable-2.6.32.x kernels? >> >> J >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Valtteri Kiviniemi
2010-Oct-13 07:03 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
Hi, Yes, probably some kernel hacking option. I have enabled these options: /boot/config-dom0 - Linux Kernel v2.6.32.24 Configuration Kernel hacking [*] Enable __must_check logic [*] Magic SysRq key -*- Debug Filesystem [*] Kernel debugging [*] Collect scheduler statistics [*] Collect kernel timers statistics [*] Compile the kernel with frame pointers [*] Sysctl checks [*] Tracers ---> [*] Support for tracing block io actions [*] Remote debugging over FireWire early on boot [*] Enable verbose x86 bootup info messages -*- Early printk [*] Early printk via EHCI debug port [*] Check for stack overflows [*] Write protect kernel read-only data structures [*] Debug boot parameters [*] Allow gcc to uninline functions marked ''inline'' All the other options are disabled. So it one/some of those that need to be enabled to get the kernel booting. Let me know if you need my config-file - Valtteri Kiviniemi Jeremy Fitzhardinge kirjoitti:> On 10/12/2010 01:02 PM, Valtteri Kiviniemi wrote: >> Hi, >> >> I just compiled Xen 4.0.0.1 with 2.6.32.24 and I stuck on this same >> problem with my own compiled kernel. However the default kernel with >> comes from "make world" boots fine. I traced the problem down to some >> settings in kernel''s menuconfig "Kernel hacking" menu. I dont exactly >> know what the option needs to be enabled in the "Kernel hacking" to >> get the kernel booting. In my own compiled kernels I have almost all >> the options in that "Kernel hacking" menu disabled, and when I enabled >> the same options in that menu that are in the default kernel which >> comes when you do "make world" the system booted fine. >> >> You probably know the problem already but I just thought that I should >> share this information with you anyway. > > No, that''s interesting. So some kernel debugging config option makes > the problem go away? That gives me some way to possibly repro the problem. > > J > > >> - Valtteri Kiviniemi >> >> Jeremy Fitzhardinge kirjoitti: >>> On 10/12/2010 01:10 AM, Andreas Kinzler wrote: >>>> On 07.10.2010 11:57, Alan J. Wylie wrote: >>>>> System: Supermicro SM-SC825TQ-R720LPB, 8GB RAM >>>>> Motherboard: X8DTL >>>>> Processor: 1 x Intel XEON E5506 quad core >>>>> RAID controller: LSI MegaRAID SAS 8708 >>>>> >>>>> Bisected (by hand) to between >>>>> 69e50db2 (good) 2.6.32.21 "Merge commit ''v2.6.32.21'' into >>>>> xen/next-2.6.32" >>>>> and >>>>> dda56688 (bad) "Merge branch ''xen/next'' into >>>>> xen/next-2.6.32" >>>>> >>>>> ffffffff8100bd10 T get_phys_to_machine >>>>> ffffffff8100bd4c t pin_pagetable_pfn >>>> I am afflicted by this problem for a long while now. Should look very >>>> familiar to you. See >>>> http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00758.html >>>> >>>> >>>> No solution till now. >>> Is it not fixed by current xen/stable-2.6.32.x kernels? >>> >>> J >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
"Alan J. Wylie" <NDA5OWUy@wylie.me.uk>,
2010-Oct-13 07:26 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
at 11:49 on Tue 12-Oct-2010 Jeremy Fitzhardinge (jeremy@goop.org) wrote:> Is it not fixed by current xen/stable-2.6.32.x kernels?My crash still occurs with the very latest git * xen/stable-2.6.32.x commit 4ac23c27f34a5ea45a098b0f6e08bf5cc6e74756 Merge: 179eca5 b10b86d Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Date: Tue Oct 12 11:00:21 2010 -0700 Merge branch ''xen/next'' into xen/next-2.6.32 I''ll have a play with kernel debug settings next. -- Alan J. Wylie http://www.wylie.me.uk/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Alan J. Wylie
2010-Oct-13 11:04 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
at 08:26 on Wed 13-Oct-2010 "Alan J. Wylie"
<NDA5OWUy@wylie.me.uk>, ("Alan J. Wylie"
<NDA5OWUy@wylie.me.uk>,) wrote:
> I''ll have a play with kernel debug settings next.
I can confirm that changing the debug settings makes the difference
between booting and crashing.
However, trying to narrow it down to a particular config option is
proving tricky.
At first I thought that just turning CONFIG_DEBUG_SPINLOCK on stopped
it crashing, however further checking was inconclusive. My suspicion
is that it''s things being moved around in memory as a result of code
being enabled that''s the issue.
I''ll continue investigating.
--
Alan J. Wylie http://www.wylie.me.uk/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Alan J. Wylie
2010-Oct-13 13:52 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
at 12:04 on Wed 13-Oct-2010 Alan J. Wylie (NDA5OWUy@wylie.me.uk) wrote:> I can confirm that changing the debug settings makes the difference > between booting and crashing. > > However, trying to narrow it down to a particular config option is > proving tricky. > > At first I thought that just turning CONFIG_DEBUG_SPINLOCK on stopped > it crashing, however further checking was inconclusive. My suspicion > is that it''s things being moved around in memory as a result of code > being enabled that''s the issue. > > I''ll continue investigating.Here''s one set of differences between .configs that makes the difference between booting and crashing: 8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------ xenity jeremy-git-xen-test # diff myconfig.009.boots myconfig.010.crashes 4c4 < # Wed Oct 13 12:17:38 2010 ---> # Wed Oct 13 14:29:49 2010108c108 < CONFIG_KALLSYMS_ALL=y ---> # CONFIG_KALLSYMS_ALL is not set8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------ 531 diff myconfig.009.boots myconfig.010.crashes 534 rm -r _dom0/ 535 mkdir _dom0/ 536 cp -p myconfig.009.boots _dom0/.config 537 make0 oldconfig 538 make0 539 scp -p _dom0/arch/x86/boot/bzImage BB:/boot/vmlinuz-test 540 rm -r _dom0/ && mkdir _dom0/ && cp -p myconfig.010.crashes _dom0/.config 541 make0 oldconfig && make0 542 scp -p _dom0/arch/x86/boot/bzImage BB:/boot/vmlinuz-test 8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------ (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1734000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000238000000->000000023a000000 (253952 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff81734000 (XEN) Init. ramdisk: ffffffff81734000->ffffffff81734000 (XEN) Phys-Mach map: ffffffff81734000->ffffffff81934000 (XEN) Start info: ffffffff81934000->ffffffff819344b4 (XEN) Page tables: ffffffff81935000->ffffffff81946000 (XEN) Boot stack: ffffffff81946000->ffffffff81947000 (XEN) TOTAL: ffffffff80000000->ffffffff81c00000 (XEN) ENTRY ADDRESS: ffffffff8154d200 (XEN) Dom0 has maximum 1 VCPUs (XEN) Scrubbing Free RAM: ......................................................................done. (XEN) trace.c:89:d32767 calc_tinfo_first_offset: NR_CPUs 128, offset_in_bytes 258, t_info_first_offset 65 (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 172kB init memory. mapping kernel into physical memory Xen: setup ISA identity maps <7>ALANW get_phys_to_machine pfn 000018C3<7> topidx 00000000<7> mididx 0000000C<7> idx 000000C3<7> returns 002398C3 about to get started... Linux version 2.6.32.24-xen0 (root@xenity) (gcc version 4.4.3 (Gentoo 4.4.3-r2 p1.2) ) #1 SMP Wed Oct 13 14:41:42 BST 2010 Command line: root=/dev/sda2 console=hvc0 earlyprintk=xen loglevel=10 initcall_debug debug KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD Centaur CentaurHauls released 0 pages of unused memory BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000000098c00 (usable) Xen: 0000000000098c00 - 0000000000100000 (reserved) Xen: 0000000000100000 - 0000000040000000 (usable) Xen: 00000000bf78e000 - 00000000bf790000 type 9 Xen: 00000000bf790000 - 00000000bf79e000 (ACPI data) Xen: 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS) Xen: 00000000bf7d0000 - 00000000bf7e0000 (reserved) Xen: 00000000bf7ec000 - 00000000c0000000 (reserved) Xen: 00000000e0000000 - 00000000f0000000 (reserved) Xen: 00000000fec00000 - 00000000fec01000 (reserved) Xen: 00000000fec8a000 - 00000000fec8b000 (reserved) Xen: 00000000fee00000 - 00000000fee01000 (reserved) Xen: 00000000ffc00000 - 0000000100000000 (reserved) Xen: 0000000240000000 - 00000002bf780000 (usable) bootconsole [xenboot0] enabled DMI present. AMI BIOS detected: BIOS may corrupt low RAM, working around it. e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) last_pfn = 0x2bf780 max_arch_pfn = 0x400000000 x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106 last_pfn = 0x40000 max_arch_pfn = 0x400000000 initial memory mapped : 0 - 20000000 init_memory_mapping: 0000000000000000-0000000040000000 0000000000 - 0040000000 page 4k kernel direct mapping tables up to 40000000 @ 100000-302000 init_memory_mapping: 0000000100000000-00000002bf780000 0100000000 - 02bf780000 page 4k kernel direct mapping tables up to 2bf780000 @ 1946000-2f4e000 ACPI: RSDP 00000000000fac10 00024 (v02 ACPIAM) ACPI: XSDT 00000000bf790100 0007C (v01 SMCI 20100528 MSFT 00000097) ACPI: FACP 00000000bf790290 000F4 (v03 052810 FACP1443 20100528 MSFT 00000097) ACPI: DSDT 00000000bf7906a0 0650A (v01 10006 10006000 00000000 INTL 20051117) ACPI: FACS 00000000bf79e000 00040 ACPI: APIC 00000000bf790390 0011E (v01 052810 APIC1443 20100528 MSFT 00000097) ACPI: MCFG 00000000bf7904b0 0003C (v01 052810 OEMMCFG 20100528 MSFT 00000097) ACPI: SLIT 00000000bf7904f0 00030 (v01 052810 OEMSLIT 20100528 MSFT 00000097) ACPI: OEMB 00000000bf79e040 0007D (v01 052810 OEMB1443 20100528 MSFT 00000097) ACPI: HPET 00000000bf79a6a0 00038 (v01 052810 OEMHPET 20100528 MSFT 00000097) ACPI: SSDT 00000000bf79ee90 00363 (v01 DpgPmm CpuPm 00000012 INTL 20051117) ACPI: EINJ 00000000bf79a6e0 00130 (v01 AMIER AMI_EINJ 20100528 MSFT 00000097) ACPI: BERT 00000000bf79a870 00030 (v01 AMIER AMI_BERT 20100528 MSFT 00000097) ACPI: ERST 00000000bf79a8a0 001B0 (v01 AMIER AMI_ERST 20100528 MSFT 00000097) ACPI: HEST 00000000bf79aa50 000A8 (v01 AMIER ABC_HEST 20100528 MSFT 00000097) ACPI: Local APIC address 0xfee00000 (9 early reservations) ==> bootmem [0000000000 - 02bf780000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] #1 [0001935000 - 0001946000] XEN PAGETABLES ==> [0001935000 - 0001946000] #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] #3 [0001000000 - 000160a280] TEXT DATA BSS ==> [0001000000 - 000160a280] #4 [0001734000 - 0001935000] XEN START INFO ==> [0001734000 - 0001935000] #5 [0240000000 - 02bf780000] XEN EXTRA ==> [0240000000 - 02bf780000] #6 [000160b000 - 000161521d] BRK ==> [000160b000 - 000161521d] #7 [0000100000 - 00002ee000] PGTABLE ==> [0000100000 - 00002ee000] #8 [0001946000 - 0001d44000] PGTABLE ==> [0001946000 - 0001d44000] found SMP MP-table at [ffff8800000ff780] ff780 Zone PFN ranges: DMA 0x00000010 -> 0x00001000 DMA32 0x00001000 -> 0x00100000 Normal 0x00100000 -> 0x002bf780 Movable zone start PFN for each node early_node_map[3] active PFN ranges 0: 0x00000010 -> 0x00000098 0: 0x00000100 -> 0x00040000 0: 0x00240000 -> 0x002bf780 On node 0 totalpages: 784136 DMA zone: 64 pages used for memmap DMA zone: 497 pages reserved DMA zone: 3415 pages, LIFO batch:0 DMA32 zone: 16320 pages used for memmap DMA32 zone: 241728 pages, LIFO batch:31 Normal zone: 28638 pages used for memmap Normal zone: 493474 pages, LIFO batch:31 8<------8<------8<------8<------8<------8<------8<------8<------8<------8<------ (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x16e4000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000238000000->000000023a000000 (253952 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff816e4000 (XEN) Init. ramdisk: ffffffff816e4000->ffffffff816e4000 (XEN) Phys-Mach map: ffffffff816e4000->ffffffff818e4000 (XEN) Start info: ffffffff818e4000->ffffffff818e44b4 (XEN) Page tables: ffffffff818e5000->ffffffff818f6000 (XEN) Boot stack: ffffffff818f6000->ffffffff818f7000 (XEN) TOTAL: ffffffff80000000->ffffffff81c00000 (XEN) ENTRY ADDRESS: ffffffff814fd200 (XEN) Dom0 has maximum 1 VCPUs (XEN) Scrubbing Free RAM: ......................................................................done. (XEN) trace.c:89:d32767 calc_tinfo_first_offset: NR_CPUs 128, offset_in_bytes 258, t_info_first_offset 65 (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 172kB init memory. mapping kernel into physical memory Xen: setup ISA identity maps <7>ALANW get_phys_to_machine pfn 000018C3<7> topidx 00000000<7> mididx 0000000C<7> idx 000000C3<7> returns 002398C3 about to get started... Linux version 2.6.32.24-xen0 (root@xenity) (gcc version 4.4.3 (Gentoo 4.4.3-r2 p1.2) ) #1 SMP Wed Oct 13 14:48:16 BST 2010 Command line: root=/dev/sda2 console=hvc0 earlyprintk=xen loglevel=10 initcall_debug debug KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD Centaur CentaurHauls released 0 pages of unused memory BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000000098c00 (usable) Xen: 0000000000098c00 - 0000000000100000 (reserved) Xen: 0000000000100000 - 0000000040000000 (usable) Xen: 00000000bf78e000 - 00000000bf790000 type 9 Xen: 00000000bf790000 - 00000000bf79e000 (ACPI data) Xen: 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS) Xen: 00000000bf7d0000 - 00000000bf7e0000 (reserved) Xen: 00000000bf7ec000 - 00000000c0000000 (reserved) Xen: 00000000e0000000 - 00000000f0000000 (reserved) Xen: 00000000fec00000 - 00000000fec01000 (reserved) Xen: 00000000fec8a000 - 00000000fec8b000 (reserved) Xen: 00000000fee00000 - 00000000fee01000 (reserved) Xen: 00000000ffc00000 - 0000000100000000 (reserved) Xen: 0000000240000000 - 00000002bf780000 (usable) bootconsole [xenboot0] enabled DMI present. AMI BIOS detected: BIOS may corrupt low RAM, working around it. e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) last_pfn = 0x2bf780 max_arch_pfn = 0x400000000 x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106 last_pfn = 0x40000 max_arch_pfn = 0x400000000 initial memory mapped : 0 - 20000000 init_memory_mapping: 0000000000000000-0000000040000000 0000000000 - 0040000000 page 4k kernel direct mapping tables up to 40000000 @ 100000-302000 init_memory_mapping: 0000000100000000-00000002bf780000 0100000000 - 02bf780000 page 4k kernel direct mapping tables up to 2bf780000 @ 18f6000-2efe000 (XEN) d0:v0: unhandled page fault (ec=0000) (XEN) Pagetable walk from ffffffff816f07b0: (XEN) L4[0x1ff] = 0000000239003067 0000000000001003 (XEN) L3[0x1fe] = 0000000239007067 0000000000001007 (XEN) L2[0x00b] = 0000000000000000 ffffffffffffffff (XEN) domain_crash_sync called from entry.S (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.0.2-rc1-pre x86_64 debug=n Tainted: C ]---- (XEN) CPU: 0 (XEN) RIP: e033:[<ffffffff8100c679>] (XEN) RFLAGS: 0000000000000206 EM: 1 CONTEXT: pv guest (XEN) rax: ffffffff816f0000 rbx: 00000000000018f6 rcx: 0000000000000118 (XEN) rdx: ffffffff81566000 rsi: ffffffffff400000 rdi: 00000000000018f6 (XEN) rbp: ffffffff81463bb8 rsp: ffffffff81463b50 r8: 8000000000000163 (XEN) r9: 000000000000000f r10: ffffffff81586130 r11: ffffffff81585d30 (XEN) r12: 00000000000000f6 r13: 000000000000000c r14: 0000000000000000 (XEN) r15: 0000000000000001 cr0: 000000008005003b cr4: 00000000000026f0 (XEN) cr3: 0000000239001000 cr2: ffffffff816f07b0 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff81463b50: (XEN) 0000000000000118 ffffffff81585d30 0000000000000000 ffffffff8100c679 (XEN) 000000010000e030 0000000000010006 ffffffff81463b98 000000000000e02b (XEN) 00003ffffffff032 80000000018f6063 00000000018f6000 00000000018f6000 (XEN) 8000000000000163 ffffffff81463bd8 ffffffff8100c954 ffffffff81463c08 (XEN) 80000000018f6063 ffffffff81463bf8 ffffffff8100ca31 0000000000000009 (XEN) 0000000000000000 ffffffff81463c48 ffffffff8100b8ab ffffffff81585d30 (XEN) ffffffff81586130 000000000000000f 8000000000000163 80000000018f6063 (XEN) ffffffffff400000 ffffffff81566000 0000000000000118 ffffffff81463ca8 (XEN) ffffffff8150f706 ffffffff814f40a0 0000000000000000 000009ff00000001 (XEN) ffffffffff400000 ffffffff81585d30 ffffffff81463d50 00000000018f6000 (XEN) 0000000240000000 00000002bf780000 00000002bf780000 ffffffff81463cb8 (XEN) ffffffff8150f7e2 ffffffff81463ce8 ffffffff81323321 0000000000000000 (XEN) ffff880001002048 00000002bf780000 0000000240000000 ffffffff81463d88 (XEN) ffffffff8152a0db ffffffff81463d98 ffffffff8103dc9e ffffffff81463d58 (XEN) 8000000000000163 ffff880001002000 0000000000000000 0000000000000000 (XEN) 0000000000000004 0000000581463d88 0000000000000000 ffffffff81585d30 (XEN) ffffffff81586130 0000000000000010 ffffffff81001880 00000002bf780000 (XEN) ffff8802bf780000 ffffffff813e37f4 ffff8802bf780000 ffffffff81463df8 (XEN) ffffffff8152a287 ffffffff81463df8 ffffffff81334a3c ffff880100000000 (XEN) 0000000000000000 ffffffff81463dc8 0000000040000000 ffffffff81463df8 (XEN) Domain 0 crashed: ''noreboot'' set - not rebooting. -- Alan J. Wylie http://www.wylie.me.uk/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Alan J. Wylie
2010-Oct-13 14:17 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
> Here''s one set of differences between .configs that makes the difference > between booting and crashing:> xenity jeremy-git-xen-test # diff myconfig.009.boots myconfig.010.crashes > 4c4 > < # Wed Oct 13 12:17:38 2010 > --- > > # Wed Oct 13 14:29:49 2010 > 108c108 > < CONFIG_KALLSYMS_ALL=y > --- > > # CONFIG_KALLSYMS_ALL is not setAnd another xenity jeremy-git-xen-test # diff myconfig.009.boots _dom0/.config 4c4 < # Wed Oct 13 12:17:38 2010 ---> # Wed Oct 13 15:08:07 20101626c1626 < CONFIG_DEBUG_SPINLOCK=y ---> # CONFIG_DEBUG_SPINLOCK is not setThank goodness for IPMI and serial over LAN. -- Alan J. Wylie http://www.wylie.me.uk/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Alan J. Wylie
2010-Oct-13 15:52 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
One last posting. I''ve turned on a load of debugging options, and have a kernel that boots very verbosely. config and log are at http://www.wylie.me.uk/tmp/config.20101013a and http://www.wylie.me.uk/tmp/log.20101013a (about 2000 lines each) Note that this is running on Serial over Lan on IPMI at a simulated 19k2 baud with synchronous console output - timing delays may also be having an effect. -- Alan J. Wylie http://www.wylie.me.uk/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Andreas Kinzler
2010-Oct-19 13:15 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On 12.10.2010 20:49, Jeremy Fitzhardinge wrote:>>> Bisected (by hand) to between >>> 69e50db2 (good) 2.6.32.21 "Merge commit ''v2.6.32.21'' into >>> xen/next-2.6.32" >>> and >>> dda56688 (bad) "Merge branch ''xen/next'' into >>> xen/next-2.6.32" >>> >>> ffffffff8100bd10 T get_phys_to_machine >>> ffffffff8100bd4c t pin_pagetable_pfn >> >> I am afflicted by this problem for a long while now. Should look very >> familiar to you. See >> http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00758.html >> No solution till now. > Is it not fixed by current xen/stable-2.6.32.x kernels?Jeremy, just tried the current 2472a9c snapshot. Still crashes. Alan, any news? Regards Andreas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Alan J. Wylie
2010-Oct-19 13:51 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
at 15:15 on Tue 19-Oct-2010 Andreas Kinzler (ml-xen-devel@hfp.de) wrote:> Jeremy, just tried the current 2472a9c snapshot. Still crashes.> Alan, any news?I''m afraid not. I think I''ve posted all the information I can come up with that might help, and I''m keeping an eye on Jeremy''s git repository, but there''s nothing much else I can do I''m afraid. Cheers Alan -- Alan J. Wylie http://www.wylie.me.uk/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gianni Tedesco
2010-Oct-19 14:29 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On Thu, 2010-10-07 at 10:57 +0100, Alan J. Wylie wrote:> System: Supermicro SM-SC825TQ-R720LPB, 8GB RAM > Motherboard: X8DTL > Processor: 1 x Intel XEON E5506 quad core > RAID controller: LSI MegaRAID SAS 8708 > > Bisected (by hand) to between > 69e50db2 (good) 2.6.32.21 "Merge commit ''v2.6.32.21'' into xen/next-2.6.32" > and > dda56688 (bad) "Merge branch ''xen/next'' into xen/next-2.6.32" > > I don''t know if it is of any relevance, but lshw hangs during DMI. > The end of the strace is: > > mmap(NULL, 4080, PROT_READ, MAP_SHARED, 3, 0xff000) = 0x7fc182228000 > munmap(0x7fc182228000, 4080) = 0 > mmap(NULL, 4096, PROT_READ, MAP_SHARED, 3, 0xff000) = 0x7fc182228000 > munmap(0x7fc182228000, 4096) = 0 > mmap(NULL, 4112, PROT_READ, MAP_SHARED, 3, 0xff000) = 0x7fc182227000 > ^C--- SIGINT (Interrupt) @ 0 (0) --- > > and XEN then outputs large numbers of the following message: > > (XEN) mm.c:860:d0 Error getting mfn 15b3 (pfn 21973) from L1 entry > 80000000015b3625 for l1e_owner=0, pg_owner=32753 > > This patch to LSHW stops it hanging, the output of this lshw can be > found later in this e-mail, along with grub.conf, /proc/cpuinfo, lshw, > dmidecode and the console output for a crash and a good boot. > > diff -Nau -r lshw-B.02.14/src/core/dmi.cc > lshw-B.02.14.patched/src/core/dmi.cc > --- lshw-B.02.14/src/core/dmi.cc 2009-02-12 22:53:09.000000000 +0000 > +++ lshw-B.02.14.patched/src/core/dmi.cc 2010-10-07 08:56:46.000000000 +0100 > @@ -1725,7 +1725,7 @@ > } > > fp -= 16; > - while (efi || (fp < 0xFFFFF)) > + while (efi || (fp < 0xFFFE0)) > { > fp += 16; > mmoffset = fp % getpagesize(); > > I''ve attempted to disassemble what I believe to be the crashing code: > > (XEN) RIP: e033:[<ffffffff8100bd47>] > > From System.map: > ffffffff8100bd10 T get_phys_to_machine > ffffffff8100bd4c t pin_pagetable_pfnI see this exact same crash however, for me, it happens immediately at boot, ie. xen crash starting dom0 in setup.S and reboot in 5 seconds. I have tried all sorts of config fiddling and nothing seems to get it to the stage of a printk from linux. Only the XCP kernel gives me a functioning dom0 on this machine. I don''t really know what to suspect here - in my case it''s possibly more than one issue. Gianni _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
sven
2010-Oct-19 14:58 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
Hello, I just wanted to report that I''m affected by this issue, too. (I subscribed to this list in the meantime; this is the first post I can reply-to in context) As it seems to be a moving target and not being bound to a specific config-option (As proven by Alan in previous posts as well as my personal experience), I suspected the build-env and tried several Distributions - Ubuntu 10.04/10, Debian Lenny and Fedora 13. Tried both an Athlon X2 and Intel i7. It always crashes. Regards, Sven _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gianni Tedesco
2010-Oct-19 15:45 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On Tue, 2010-10-19 at 15:58 +0100, sven wrote:> Hello, > > I just wanted to report that I''m affected by this issue, too. > (I subscribed to this list in the meantime; this is the first post I can > reply-to in context) > > As it seems to be a moving target and not being bound to a specific > config-option (As proven by Alan in previous posts as well as my > personal experience), I suspected the build-env and tried several > Distributions - Ubuntu 10.04/10, Debian Lenny and Fedora 13. > Tried both an Athlon X2 and Intel i7.ditto, I suspected a known bug in my gcc version which broke xchg because when I compiled with -O2 instead of -Os... the problem went away but then something else bad happened later (I forget the details, and it was too many config tweaks ago to get back to last time I had it working that well) it''s clearly one of those fun and subtle bugs :( Gianni _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
sven
2010-Oct-19 18:01 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On 10/19/2010 05:45 PM, Gianni Tedesco wrote:> ditto, I suspected a known bug in my gcc version which broke xchg > because when I compiled with -O2 instead of -Os... the problem went away > but then something else bad happened later (I forget the details, and it > was too many config tweaks ago to get back to last time I had it working > that well)Like disabling "Optimize for size" in the config? Just tried, didn''t make any difference.> it''s clearly one of those fun and subtle bugs :(*sigh* :( Regards, Sven p.s.: someone let me know if i should keep everybody on cc! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gianni Tedesco
2010-Oct-19 18:20 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On Tue, 2010-10-19 at 19:01 +0100, sven wrote:> On 10/19/2010 05:45 PM, Gianni Tedesco wrote: > > ditto, I suspected a known bug in my gcc version which broke xchg > > because when I compiled with -O2 instead of -Os... the problem went away > > but then something else bad happened later (I forget the details, and it > > was too many config tweaks ago to get back to last time I had it working > > that well) > > Like disabling "Optimize for size" in the config? > Just tried, didn''t make any difference.Well, I mean I still have"Optimize for size" disabled and it''s still broken.> > > it''s clearly one of those fun and subtle bugs :( > > *sigh* :(I am doing a little more digging, what I have found is that xen_build_dynamic_phys_to_machine() is building a valid looking p2m table, but later on we get some calls to get_phys_to_machine() which are outside the range of max_pfn (which Jeremy tells me is acceptable) but at that point max_pfn is zero. In other words, it looks like some important data structures are getting over-written with nonsense. I will have a think and get back to debugging this when I have a bit more time. In the mean time, can you provide me with some info about the machines you''re reproing this on? Mines a brand new dell power-edge xeon thing.> Regards, > Sven > > p.s.: someone let me know if i should keep everybody on cc!Please, that''s the convention! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
sven
2010-Oct-19 19:05 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On 10/19/2010 08:20 PM, Gianni Tedesco wrote:>> Like disabling "Optimize for size" in the config? >> Just tried, didn''t make any difference. > > Well, I mean I still have"Optimize for size" disabled and it''s still > broken.Ok. I meant - regardless how it is set, it fails :)> I am doing a little more digging, what I have found is that > xen_build_dynamic_phys_to_machine() is building a valid looking p2m > table, but later on we get some calls to get_phys_to_machine() which are > outside the range of max_pfn (which Jeremy tells me is acceptable) but > at that point max_pfn is zero.I have to admit that I do not understand (due to lack of any knowledge about the internals) what these functions are for..> In other words, it looks like some important data structures are getting > over-written with nonsense... but this (even) I do understand.> I will have a think and get back to debugging this when I have a bit > more time. > > In the mean time, can you provide me with some info about the machines > you''re reproing this on? Mines a brand new dell power-edge xeon thing.Sure, I''ll do all I can to help pest-controlling it. I''m already at home, off mind it is: #1 Athlon X2 5600+ on Asus AM2-VM [NForce 430 Chipset] (I''m not 100% sure about the Mainboard right now) - no addon-cards 4x1G RAM, also tried with 1x1G #2 Core i7 920 on Asus P6T-Deluxe [Intel X58 Chipset] - a (prehistoric) PCI VGA-Card 3x2G RAM So you think the problem only affects specific platforms? Regards, Sven>> p.s.: someone let me know if i should keep everybody on cc! > > Please, that''s the convention!Oh. This isn''t nntp, isn''t it? So, Alan & Jeremy, blame Gianni :-) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Andreas Kinzler
2010-Oct-19 23:31 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On 19.10.2010 17:45, Gianni Tedesco wrote:> ditto, I suspected a known bug in my gcc version which broke xchg > because when I compiled with -O2 instead of -Os... the problem went away > but then something else bad happened later (I forget the details, and it > was too many config tweaks ago to get back to last time I had it working > that well)Jeremy, one user earlier reported that he found out that for him there seems to be a relation between kernel size and crash status. He just added/removed some options that could never influence the "crash status" (like adding/removing netfilter modules). With all the experiences here, is may be useful to check for code paths related to kernel size. Regards Andreas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gianni Tedesco
2010-Oct-20 08:54 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On Wed, 2010-10-20 at 00:31 +0100, Andreas Kinzler wrote:> On 19.10.2010 17:45, Gianni Tedesco wrote: > > ditto, I suspected a known bug in my gcc version which broke xchg > > because when I compiled with -O2 instead of -Os... the problem went away > > but then something else bad happened later (I forget the details, and it > > was too many config tweaks ago to get back to last time I had it working > > that well) > > Jeremy, one user earlier reported that he found out that for him there > seems to be a relation between kernel size and crash status. He just > added/removed some options that could never influence the "crash status" > (like adding/removing netfilter modules). With all the experiences here, > is may be useful to check for code paths related to kernel size. > > Regards AndreasAh, well that certainly explains why CONFIG_KALLSYMS makes a difference. Gianni _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gianni Tedesco
2010-Oct-29 15:44 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On Wed, 2010-10-20 at 09:54 +0100, Gianni Tedesco wrote:> On Wed, 2010-10-20 at 00:31 +0100, Andreas Kinzler wrote: > > On 19.10.2010 17:45, Gianni Tedesco wrote: > > > ditto, I suspected a known bug in my gcc version which broke xchg > > > because when I compiled with -O2 instead of -Os... the problem went away > > > but then something else bad happened later (I forget the details, and it > > > was too many config tweaks ago to get back to last time I had it working > > > that well) > > > > Jeremy, one user earlier reported that he found out that for him there > > seems to be a relation between kernel size and crash status. He just > > added/removed some options that could never influence the "crash status" > > (like adding/removing netfilter modules). With all the experiences here, > > is may be useful to check for code paths related to kernel size. > > > > Regards AndreasI have dmesg output from 2.6.32.18-ge6b9b2c and the current broken version. http://pastebin.com/3m0DpDdW - 2.6.32.24-gd0054d6-dirty - broken http://pastebin.com/yC4CzLaZ - 2.6.32.18-ge6b9b2c - working In the panic you can see that %rax contains what the kernel thinks is xen_start_info (0xffffffff817d3000) and from the xen logs, that is correct.>From the kernel messages it looks like the e820 map is being calculatedincorrectly, leading to bad memory mappings being setup which somehow end up nuking the pagetable entry for xen start info. The last_pfn/max_arch_pfn end up being an order of magnitude larger even though both are booted with identical xen and kernel commandline params. Xen has dom0_mem=752M. Gianni _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-Oct-29 16:15 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On Fri, Oct 29, 2010 at 04:44:23PM +0100, Gianni Tedesco wrote:> On Wed, 2010-10-20 at 09:54 +0100, Gianni Tedesco wrote: > > On Wed, 2010-10-20 at 00:31 +0100, Andreas Kinzler wrote: > > > On 19.10.2010 17:45, Gianni Tedesco wrote: > > > > ditto, I suspected a known bug in my gcc version which broke xchg > > > > because when I compiled with -O2 instead of -Os... the problem went away > > > > but then something else bad happened later (I forget the details, and it > > > > was too many config tweaks ago to get back to last time I had it working > > > > that well) > > > > > > Jeremy, one user earlier reported that he found out that for him there > > > seems to be a relation between kernel size and crash status. He just > > > added/removed some options that could never influence the "crash status" > > > (like adding/removing netfilter modules). With all the experiences here, > > > is may be useful to check for code paths related to kernel size. > > > > > > Regards Andreas > > I have dmesg output from 2.6.32.18-ge6b9b2c and the current broken > version. > > http://pastebin.com/3m0DpDdW - 2.6.32.24-gd0054d6-dirty - brokenGianni pointed out to me that he spotted this: [ 0.000000] last_pfn = 0x2d0699 max_arch_pfn = 0x400000000 [ 0.000000] x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106 [ 0.000000] last_pfn = 0x2f000 max_arch_pfn = 0x400000000 I am not sure why "last_pfn" is being printed twice, but it could be Gianni test-patch. It looks as if the initial E820 is created with a max_pfn of 0x2d0699, which rougly translates to 8G of memory instead of the 752MB. There were a bunch of changes in arch/x86/xen/setup.c and mmu.c code that figures out the max_pfn. Actually, there is one (git commit 6c8e75f5e712e596ab138597e65aac426ff03382): HYPERVISOR_shared_info->arch.max_pfn = xen_max_p2m_pfn Which would set the this to the highest PFN. But that number should not have been used by the E820 calculation which uses nr_pages entry to clamp the E820. Oh wait, it does not - it actually still parses the E820, but marks the area above the nr_pages as "XEN EXTRA" (git commit 8d0d6d6d275d4514780ba3d350e57d48e3b5b5e1) so they should not figure in the last_pfn calculation and instead lay unused. But the ''initial memory mapping'' ignores that and still tries to setup mapping on _all_ E820_RAM regions, even if they are reserved from by the early memory allocator. This would imply that the page table is being actually put right in the area that is reserved by the early memory allocator. Hmm, so Gianni, I think if you shortcircuited the setup.c code to not parse the E820_RAM regions above the nr_pages that might do it. And also try to figure out who or what resets the last_pfn. Or in the code that sets the ''XEN EXTRA'', make it set that region of pages as E820_RESERVED and see what happens then.> http://pastebin.com/yC4CzLaZ - 2.6.32.18-ge6b9b2c - working > > In the panic you can see that %rax contains what the kernel thinks is > xen_start_info (0xffffffff817d3000) and from the xen logs, that is > correct. > > >From the kernel messages it looks like the e820 map is being calculated > incorrectly, leading to bad memory mappings being setup which somehow > end up nuking the pagetable entry for xen start info. The > last_pfn/max_arch_pfn end up being an order of magnitude larger even > though both are booted with identical xen and kernel commandline params. > Xen has dom0_mem=752M. > > Gianni >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Nov-01 13:37 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On 10/29/2010 12:15 PM, Konrad Rzeszutek Wilk wrote:> On Fri, Oct 29, 2010 at 04:44:23PM +0100, Gianni Tedesco wrote: >> On Wed, 2010-10-20 at 09:54 +0100, Gianni Tedesco wrote: >>> On Wed, 2010-10-20 at 00:31 +0100, Andreas Kinzler wrote: >>>> On 19.10.2010 17:45, Gianni Tedesco wrote: >>>>> ditto, I suspected a known bug in my gcc version which broke xchg >>>>> because when I compiled with -O2 instead of -Os... the problem went away >>>>> but then something else bad happened later (I forget the details, and it >>>>> was too many config tweaks ago to get back to last time I had it working >>>>> that well) >>>> Jeremy, one user earlier reported that he found out that for him there >>>> seems to be a relation between kernel size and crash status. He just >>>> added/removed some options that could never influence the "crash status" >>>> (like adding/removing netfilter modules). With all the experiences here, >>>> is may be useful to check for code paths related to kernel size. >>>> >>>> Regards Andreas >> I have dmesg output from 2.6.32.18-ge6b9b2c and the current broken >> version. >> >> http://pastebin.com/3m0DpDdW - 2.6.32.24-gd0054d6-dirty - broken > Gianni pointed out to me that he spotted this: > > [ 0.000000] last_pfn = 0x2d0699 max_arch_pfn = 0x400000000 > [ 0.000000] x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106 > [ 0.000000] last_pfn = 0x2f000 max_arch_pfn = 0x400000000 > > I am not sure why "last_pfn" is being printed twice, but it could be > Gianni test-patch. > > It looks as if the initial E820 is created with a max_pfn of > 0x2d0699, which rougly translates to 8G of memory instead of > the 752MB. > > There were a bunch of changes in arch/x86/xen/setup.c and mmu.c > code that figures out the max_pfn. Actually, there is one > (git commit 6c8e75f5e712e596ab138597e65aac426ff03382): > > HYPERVISOR_shared_info->arch.max_pfn = xen_max_p2m_pfnThat sets the extent that the toolstack will look at the P2M for migration; it has no direct effect on the domain itself.> Which would set the this to the highest PFN. But that number > should not have been used by the E820 calculation which uses > nr_pages entry to clamp the E820. Oh wait, it does not - it actually > still parses the E820, but marks the area above the nr_pages > as "XEN EXTRA" (git commit 8d0d6d6d275d4514780ba3d350e57d48e3b5b5e1) > so they should not figure in the last_pfn calculation and instead > lay unused. But the ''initial memory mapping'' ignores that and > still tries to setup mapping on _all_ E820_RAM regions, even > if they are reserved from by the early memory allocator. This would > imply that the page table is being actually put right in the > area that is reserved by the early memory allocator. > > Hmm, so Gianni, I think if you shortcircuited the setup.c code > to not parse the E820_RAM regions above the nr_pages that might > do it. And also try to figure out who or what resets the last_pfn. > > Or in the code that sets the ''XEN EXTRA'', make it set that region > of pages as E820_RESERVED and see what happens then.The way is this is supposed to work is: 1. Xen gives the domain N pages 2. There''s an E820 which describes M pages (M > N) 3. The kernel traverses the existing E820 and finds holes and adds the memory to a new E820_RAM region beyond M 4. Set up P2M for pages up to N 5. When the kernel maps all "RAM", the region from N-M is not present, and has no valid P2M mapping; in that case, xen_make_pte will return a non-present pte. The important part of making XEN EXTRA E820_RAM is that the kernel will allocate page structures for them, even if the pages are absent. Making it RESERVED will suppress that and make the exercise pointless. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-Nov-01 17:39 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
> >> http://pastebin.com/3m0DpDdW - 2.6.32.24-gd0054d6-dirty - broken.. snip..> The way is this is supposed to work is: > > 1. Xen gives the domain N pages > 2. There''s an E820 which describes M pages (M > N) > 3. The kernel traverses the existing E820 and finds holes and adds > the memory to a new E820_RAM region beyond M > 4. Set up P2M for pages up to N > 5. When the kernel maps all "RAM", the region from N-M is not > present, and has no valid P2M mapping; in that case, xen_make_pte > will return a non-present pte.Right, and somehow his machine/kernel is not doing this. His ''N'' ends up being ''M'' so the region N-M is added to the "RAM", and xen_make_pte I _think_ returns a non-present pte (or maybe it does present a present pte?) In the previous kernel (2.6.32.18), it does exactly what you described. Take a look at his http://pastebin.com/3m0DpDdW [ 0.000000] Xen: 0000000000000000 - 000000000009e000 (usable) [ 0.000000] Xen: 0000000000100000 - 000000002f000000 (usable) [ 0.000000] Xen: 00000000bf699000 - 00000000bf6af000 (reserved) [ 0.000000] Xen: 00000000bf6af000 - 00000000bf6ce000 (ACPI data) [ 0.000000] Xen: 00000000bf6ce000 - 00000000c0000000 (reserved) [ 0.000000] Xen: 00000000e0000000 - 00000000f0000000 (reserved) [ 0.000000] Xen: 00000000fe000000 - 0000000100000000 (reserved) [ 0.000000] Xen: 0000000240000000 - 00000002d0699000 (usable) He passes in dom0_mem=752M flag, so it should stop right at pfn 2f0000, but it continues on with 0x2d0699.> > The important part of making XEN EXTRA E820_RAM is that the kernel will > allocate page structures for them, even if the pages are absent. Making > it RESERVED will suppress that and make the exercise pointless.<nods> Happens in 2.6.32.18, but not 2.6.32.24 with his kernel. That region ends up being allocated. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Nov-01 17:46 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On 11/01/2010 01:39 PM, Konrad Rzeszutek Wilk wrote:>>>> http://pastebin.com/3m0DpDdW - 2.6.32.24-gd0054d6-dirty - broken > .. snip.. >> The way is this is supposed to work is: >> >> 1. Xen gives the domain N pages >> 2. There''s an E820 which describes M pages (M > N) >> 3. The kernel traverses the existing E820 and finds holes and adds >> the memory to a new E820_RAM region beyond M >> 4. Set up P2M for pages up to N >> 5. When the kernel maps all "RAM", the region from N-M is not >> present, and has no valid P2M mapping; in that case, xen_make_pte >> will return a non-present pte. > Right, and somehow his machine/kernel is not doing this. His ''N'' ends up being ''M'' so > the region N-M is added to the "RAM", and xen_make_pte I _think_ returns a non-present pte > (or maybe it does present a present pte?) In the previous kernel (2.6.32.18), it > does exactly what you described.I doubt it. On older kernels it would just truncate the max E820 address to N, not even respecting any holes, so N=M and all memory is properly mapped.> Take a look at his http://pastebin.com/3m0DpDdW > > [ 0.000000] Xen: 0000000000000000 - 000000000009e000 (usable) > [ 0.000000] Xen: 0000000000100000 - 000000002f000000 (usable) > [ 0.000000] Xen: 00000000bf699000 - 00000000bf6af000 (reserved) > [ 0.000000] Xen: 00000000bf6af000 - 00000000bf6ce000 (ACPI data) > [ 0.000000] Xen: 00000000bf6ce000 - 00000000c0000000 (reserved) > [ 0.000000] Xen: 00000000e0000000 - 00000000f0000000 (reserved) > [ 0.000000] Xen: 00000000fe000000 - 0000000100000000 (reserved) > [ 0.000000] Xen: 0000000240000000 - 00000002d0699000 (usable) > > He passes in dom0_mem=752M flag, so it should stop right at pfn 2f0000, > but it continues on with 0x2d0699.Yes. The current behaviour is that dom0_mem sets N, but the host E820 sets M, so there''s the possibility of ballooning dom0 up to full memory size (or at least up to 10N). If you set mem= on the kernel command line, you can trunate M.>> The important part of making XEN EXTRA E820_RAM is that the kernel will >> allocate page structures for them, even if the pages are absent. Making >> it RESERVED will suppress that and make the exercise pointless. > <nods> Happens in 2.6.32.18, but not 2.6.32.24 with his kernel. That region ends > up being allocated.Hm. Not sure about that. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-Nov-01 17:46 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On Mon, Nov 01, 2010 at 01:39:40PM -0400, Konrad Rzeszutek Wilk wrote:> > >> http://pastebin.com/3m0DpDdW - 2.6.32.24-gd0054d6-dirty - broken > .. snip.. > > The way is this is supposed to work is: > > > > 1. Xen gives the domain N pages > > 2. There''s an E820 which describes M pages (M > N) > > 3. The kernel traverses the existing E820 and finds holes and adds > > the memory to a new E820_RAM region beyond M > > 4. Set up P2M for pages up to N > > 5. When the kernel maps all "RAM", the region from N-M is not > > present, and has no valid P2M mapping; in that case, xen_make_pte > > will return a non-present pte. > > Right, and somehow his machine/kernel is not doing this. His ''N'' ends up being ''M'' so > the region N-M is added to the "RAM", and xen_make_pte I _think_ returns a non-present pte > (or maybe it does present a present pte?) In the previous kernel (2.6.32.18), it > does exactly what you described.Not that I am actually sure what is causing this. The interesting part is that he sees this twice: [ 0.000000] last_pfn = 0x2d0699 max_arch_pfn = 0x400000000 [ 0.000000] last_pfn = 0x2f000 max_arch_pfn = 0x400000000 And he mentioned on IRC to me that this was not due to any debugging patches. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Nov-01 18:16 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On 11/01/2010 01:46 PM, Konrad Rzeszutek Wilk wrote:> On Mon, Nov 01, 2010 at 01:39:40PM -0400, Konrad Rzeszutek Wilk wrote: >>>>> http://pastebin.com/3m0DpDdW - 2.6.32.24-gd0054d6-dirty - broken >> .. snip.. >>> The way is this is supposed to work is: >>> >>> 1. Xen gives the domain N pages >>> 2. There''s an E820 which describes M pages (M > N) >>> 3. The kernel traverses the existing E820 and finds holes and adds >>> the memory to a new E820_RAM region beyond M >>> 4. Set up P2M for pages up to N >>> 5. When the kernel maps all "RAM", the region from N-M is not >>> present, and has no valid P2M mapping; in that case, xen_make_pte >>> will return a non-present pte. >> Right, and somehow his machine/kernel is not doing this. His ''N'' ends up being ''M'' so >> the region N-M is added to the "RAM", and xen_make_pte I _think_ returns a non-present pte >> (or maybe it does present a present pte?) In the previous kernel (2.6.32.18), it >> does exactly what you described. > Not that I am actually sure what is causing this. The interesting part is that > he sees this twice: > > [ 0.000000] last_pfn = 0x2d0699 max_arch_pfn = 0x400000000 > [ 0.000000] last_pfn = 0x2f000 max_arch_pfn = 0x400000000 > > And he mentioned on IRC to me that this was not due to any debugging patches.That''s just printed by e820_end_pfn(), which is called a few times. Does it happen native? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gianni Tedesco
2010-Nov-01 18:19 UTC
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
On Mon, 2010-11-01 at 18:16 +0000, Jeremy Fitzhardinge wrote:> On 11/01/2010 01:46 PM, Konrad Rzeszutek Wilk wrote: > > On Mon, Nov 01, 2010 at 01:39:40PM -0400, Konrad Rzeszutek Wilk wrote: > >>>>> http://pastebin.com/3m0DpDdW - 2.6.32.24-gd0054d6-dirty - broken > >> .. snip.. > >>> The way is this is supposed to work is: > >>> > >>> 1. Xen gives the domain N pages > >>> 2. There''s an E820 which describes M pages (M > N) > >>> 3. The kernel traverses the existing E820 and finds holes and adds > >>> the memory to a new E820_RAM region beyond M > >>> 4. Set up P2M for pages up to N > >>> 5. When the kernel maps all "RAM", the region from N-M is not > >>> present, and has no valid P2M mapping; in that case, xen_make_pte > >>> will return a non-present pte. > >> Right, and somehow his machine/kernel is not doing this. His ''N'' ends up being ''M'' so > >> the region N-M is added to the "RAM", and xen_make_pte I _think_ returns a non-present pte > >> (or maybe it does present a present pte?) In the previous kernel (2.6.32.18), it > >> does exactly what you described. > > Not that I am actually sure what is causing this. The interesting part is that > > he sees this twice: > > > > [ 0.000000] last_pfn = 0x2d0699 max_arch_pfn = 0x400000000 > > [ 0.000000] last_pfn = 0x2f000 max_arch_pfn = 0x400000000 > > > > And he mentioned on IRC to me that this was not due to any debugging patches. > > That''s just printed by e820_end_pfn(), which is called a few times. > Does it happen native?It''s just called twice once for max mem and once for max_low_mem which are different for me (ie. correspond to N and M respectively). Not sure if it happens on bare metal Gianni _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel