* Xen-unstable boot panic due to changeset 26517 AMD, IOMMU: Clean up old entries in remapping tables when creating new one
@ 2013-02-05 21:19 Sander Eikelenboom
2013-02-06 10:23 ` Jan Beulich
0 siblings, 1 reply; 9+ messages in thread
From: Sander Eikelenboom @ 2013-02-05 21:19 UTC (permalink / raw)
To: Jan Beulich; +Cc: Boris Ostrovsky, xen-devel
[-- Attachment #1: Type: text/plain, Size: 130 bytes --]
Hi Jan,
Boot of xen-unstable is broken due to changeset 26517 on a AMD 890-FX motherboard.
The serial log is attached.
--
Sander
[-- Attachment #2: serial.log --]
[-- Type: application/octet-stream, Size: 13988 bytes --]
__ __ _ _ _____ _ _ _
\ \/ /___ _ __ | || | |___ / _ _ _ __ ___| |_ __ _| |__ | | ___
\ // _ \ '_ \ | || |_ |_ \ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
/ \ __/ | | | |__ _| ___) |__| |_| | | | \__ \ || (_| | |_) | | __/
/_/\_\___|_| |_| |_|(_)____/ \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
(XEN) Xen version 4.3-unstable (root@dyndns.org) (gcc (Debian 4.4.5-8) 4.4.5) debug=y Tue Feb 5 19:52:11 CET 2013
(XEN) Latest ChangeSet: Tue Feb 05 15:47:41 2013 +0000 26520:6c1b12c884b4
(XEN) Bootloader: GRUB 1.98+20100804-14+squeeze1
(XEN) Command line: dom0_mem=1024M,max:1024M loglvl=all loglvl_guest=all console_timestamps vga=gfx-1280x1024x32 cpuidle cpufreq=xen noreboot debug lapic=debug apic_verbosity=debug apic=debug iommu=on,verbose,debug,amd-iommu-debug com1=38400,8n1 console=vga,com1
(XEN) Video information:
(XEN) VGA is graphics mode 1280x1024, 32 bpp
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 2 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009f000 (usable)
(XEN) 000000000009f000 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000aff90000 (usable)
(XEN) 00000000aff90000 - 00000000aff9e000 (ACPI data)
(XEN) 00000000aff9e000 - 00000000affe0000 (ACPI NVS)
(XEN) 00000000affe0000 - 00000000b0000000 (reserved)
(XEN) 00000000ffe00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000250000000 (usable)
(XEN) ACPI: RSDP 000FB100, 0014 (r0 ACPIAM)
(XEN) ACPI: RSDT AFF90000, 0048 (r1 MSI OEMSLIC 20100913 MSFT 97)
(XEN) ACPI: FACP AFF90200, 0084 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) ACPI: DSDT AFF905E0, 9427 (r1 A7640 A7640100 100 INTL 20051117)
(XEN) ACPI: FACS AFF9E000, 0040
(XEN) ACPI: APIC AFF90390, 0088 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) ACPI: MCFG AFF90420, 003C (r1 7640MS OEMMCFG 20100913 MSFT 97)
(XEN) ACPI: SLIC AFF90460, 0176 (r1 MSI OEMSLIC 20100913 MSFT 97)
(XEN) ACPI: OEMB AFF9E040, 0072 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) ACPI: SRAT AFF9A5E0, 0108 (r3 AMD FAM_F_10 2 AMD 1)
(XEN) ACPI: HPET AFF9A6F0, 0038 (r1 7640MS OEMHPET 20100913 MSFT 97)
(XEN) ACPI: IVRS AFF9A730, 00F8 (r1 AMD RD890S 202031 AMD 0)
(XEN) ACPI: SSDT AFF9A830, 0DA4 (r1 A M I POWERNOW 1 AMD 1)
(XEN) System RAM: 8191MB (8387772kB)
(XEN) SRAT: PXM 0 -> APIC 0 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 1 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 2 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 3 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 4 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 5 -> Node 0
(XEN) SRAT: Node 0 PXM 0 0-a0000
(XEN) SRAT: Node 0 PXM 0 100000-b0000000
(XEN) SRAT: Node 0 PXM 0 100000000-250000000
(XEN) NUMA: Allocated memnodemap from 24d8d0000 - 24d8d3000
(XEN) NUMA: Using 8 for the hash shift.
(XEN) Domain heap initialised
(XEN) vesafb: framebuffer at 0xfb000000, mapped to 0xffff82c000081000, using 6144k, total 14336k
(XEN) vesafb: mode is 1280x1024x32, linelength=5120, font 8x16
(XEN) vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
(XEN) found SMP MP-table at 000ff780
(XEN) DMI present.
(XEN) APIC boot state is 'xapic'
(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[aff9e00c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
(XEN) Processor #4 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
(XEN) Processor #5 0:10 APIC version 16
(XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
(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 low 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: 0x8300 base: 0xfed00000
(XEN) Table is not found!
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 6 CPUs (0 hotplug CPUs)
(XEN) mapped APIC to ffff82c3ffdfb000 (fee00000)
(XEN) mapped IOAPIC to ffff82c3ffdfa000 (fec00000)
(XEN) mapped IOAPIC to ffff82c3ffdf9000 (fec20000)
(XEN) IRQ limits: 56 GSI, 1112 MSI/MSI-X
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3200.199 MHz processor.
(XEN) Initing memory sharing.
(XEN) AMD Fam10h machine check reporting enabled
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff
(XEN) PCI: Not using MCFG for segment 0000 bus 00-ff
(XEN) AMD-Vi: Found MSI capability block at 0x54
(XEN) AMD-Vi: ACPI Table:
(XEN) AMD-Vi: Signature IVRS
(XEN) AMD-Vi: Length 0xf8
(XEN) AMD-Vi: Revision 0x1
(XEN) AMD-Vi: CheckSum 0x50
(XEN) AMD-Vi: OEM_Id AMD
(XEN) AMD-Vi: OEM_Table_Id RD890S
(XEN) AMD-Vi: OEM_Revision 0x202031
(XEN) AMD-Vi: Creator_Id AMD
(XEN) AMD-Vi: Creator_Revision 0
(XEN) AMD-Vi: IVRS Block:
(XEN) AMD-Vi: Type 0x10
(XEN) AMD-Vi: Flags 0x3e
(XEN) AMD-Vi: Length 0xc8
(XEN) AMD-Vi: Dev_Id 0x2
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x3
(XEN) AMD-Vi: Dev_Id 0
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: Dev_Id Range: 0 -> 0x2
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x10
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xb00
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x18
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x900
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x43
(XEN) AMD-Vi: Dev_Id 0xa08
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: Dev_Id Range: 0xa08 -> 0xaff
(XEN) AMD-Vi: Dev_Id Alias: 0xa00
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x28
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x800
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x30
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x700
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x50
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x600
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x58
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x3
(XEN) AMD-Vi: Dev_Id 0x500
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x500 -> 0x501
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x68
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x400
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x88
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x3
(XEN) AMD-Vi: Dev_Id 0x90
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x90 -> 0x92
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x3
(XEN) AMD-Vi: Dev_Id 0x98
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x98 -> 0x9a
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa0
(XEN) AMD-Vi: Flags 0xd7
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa1
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa2
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa3
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa4
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x43
(XEN) AMD-Vi: Dev_Id 0x300
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x300 -> 0x3ff
(XEN) AMD-Vi: Dev_Id Alias: 0xa4
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa5
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa8
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa9
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x100
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x3
(XEN) AMD-Vi: Dev_Id 0xb0
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: Dev_Id Range: 0xb0 -> 0xb2
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0
(XEN) AMD-Vi: Dev_Id 0
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x48
(XEN) AMD-Vi: Dev_Id 0
(XEN) AMD-Vi: Flags 0xd7
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x48
(XEN) AMD-Vi: Dev_Id 0
(XEN) AMD-Vi: Flags 0
(XEN) AMD-Vi: IOMMU 0 Enabled.
(XEN) AMD-Vi: Enabling per-device vector maps
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Getting VERSION: 80050010
(XEN) Getting VERSION: 80050010
(XEN) Getting ID: 0
(XEN) Getting LVT0: 700
(XEN) Getting LVT1: 400
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 0x4 after: 0
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) init IO_APIC IRQs
(XEN) IO-APIC (apicid-pin) 6-0----[ Xen-4.3-unstable x86_64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e008:[<ffff82c4c014fa1a>] amd_iommu_ioapic_update_ire+0x25e/0x574
(XEN) RFLAGS: 0000000000010016 CONTEXT: hypervisor
(XEN) rax: 0000000000000001 rbx: 0000000000000013 rcx: 0000000000000060
(XEN) rdx: 0000000000000000 rsi: ffff82c3fffff000 rdi: ffff82c4c02e8028
(XEN) rbp: ffff82c4c02bfcf8 rsp: ffff82c4c02bfc38 r8: 0000000000000001
(XEN) r9: ffff82c4c025ff20 r10: 000000000000000f r11: 0000000000000001
(XEN) r12: 0000000000000000 r13: 0000000001000000 r14: 0000000000000012
(XEN) r15: ffff83024d8b5d80 cr0: 000000008005003b cr4: 00000000000006f0
(XEN) cr3: 00000000afc70000 cr2: 0000000000000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008
(XEN) Xen stack trace from rsp=ffff82c4c02bfc38:
(XEN) ffff82c4c02bfd48 0000000000000000 0000000000000001 0000000000000012
(XEN) ffff82c4c02bfc78 ffff82c4011680c3 0000000000000000 00000001c02bfcc8
(XEN) ffff82c4c02bfcb8 ffff82c4c0168bd4 ffff82c4c02766e8 ffff830200000000
(XEN) 0000001300000001 0000000000205000 0100000000010000 ffff82c400000030
(XEN) 0000000000010000 0000000000000000 0000000000000001 0000000000000001
(XEN) 0100000000000930 0000000000000000 ffff82c4c0162584 0000000000000000
(XEN) ffff82c4c02bfd08 ffff82c4c0141487 ffff82c4c02bfd18 ffff82c4c016259b
(XEN) ffff82c4c02bfd48 ffff82c4c0161951 0000000000000246 0000000000000002
(XEN) 0000000000000000 ffff82c4c025cf20 ffff82c4c02bfe28 ffff82c4c0292174
(XEN) 0000000000000000 ffff82c4c025cf20 ffff82c4c025cf20 0000000000000000
(XEN) 0000000100000000 ffff82c4c02bfde8 0000000000000000 ffff82c400000000
(XEN) 0000000000000001 0000000000000001 0000000000000000 0000000000000000
(XEN) ffff83024d8c8080 0000000000000000 0000000000000000 00000000000000f0
(XEN) ffff82c3ffdfb000 00000000ffffffff 0100000000000930 ffff82c4c01554c3
(XEN) ffff83024d8ccfe0 ffff82c4c0311d40 ffff83000008efb0 ffff83024d8ccfe0
(XEN) 0000000000000002 0000000000000002 ffff82c4c02bfe48 ffff82c4c02998f1
(XEN) ffff82c4c02b8000 ffff82c4c02b8000 ffff82c4c02bff08 ffff82c4c0298d46
(XEN) 0000000000000000 0000000000000000 ffff83000008ec50 00000000013bd000
(XEN) 0000000000000000 ffff82c4c02f8d14 ffff83000008efb0 00000000ffffffff
(XEN) ffff830000000005 ffff83000008ee90 ffff83000008efb0 ffff82c4ffffffff
(XEN) Xen call trace:
(XEN) [<ffff82c4c014fa1a>] amd_iommu_ioapic_update_ire+0x25e/0x574
(XEN) [<ffff82c4c0141487>] iommu_update_ire_from_apic+0x34/0x36
(XEN) [<ffff82c4c016259b>] io_apic_write+0x17/0x6d
(XEN) [<ffff82c4c0161951>] __ioapic_write_entry+0x45/0x67
(XEN) [<ffff82c4c0292174>] setup_IO_APIC+0xa76/0x1223
(XEN) [<ffff82c4c02998f1>] smp_prepare_cpus+0x1c0/0x1cf
(XEN) [<ffff82c4c0298d46>] __start_xen+0x2807/0x2c2b
(XEN)
(XEN) Pagetable walk from 0000000000000000:
(XEN) L4[0x000] = 000000024d8bc063 ffffffffffffffff
(XEN) L3[0x000] = 000000024d8bb063 ffffffffffffffff
(XEN) L2[0x000] = 000000024d8ba063 ffffffffffffffff
(XEN) L1[0x000] = 0000000000000000 ffffffffffffffff
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) FATAL PAGE FAULT
(XEN) [error_code=0000]
(XEN) Faulting linear address: 0000000000000000
(XEN) ****************************************
(XEN)
(XEN) Manual reset required ('noreboot' specified)
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Xen-unstable boot panic due to changeset 26517 AMD, IOMMU: Clean up old entries in remapping tables when creating new one
2013-02-05 21:19 Xen-unstable boot panic due to changeset 26517 AMD, IOMMU: Clean up old entries in remapping tables when creating new one Sander Eikelenboom
@ 2013-02-06 10:23 ` Jan Beulich
2013-02-06 11:24 ` Sander Eikelenboom
0 siblings, 1 reply; 9+ messages in thread
From: Jan Beulich @ 2013-02-06 10:23 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Boris Ostrovsky, xen-devel
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
>>> On 05.02.13 at 22:19, Sander Eikelenboom <linux@eikelenboom.it> wrote:
> Boot of xen-unstable is broken due to changeset 26517 on a AMD 890-FX
> motherboard.
> The serial log is attached.
Yeah, we were afraid of that. Unfortunately the log you provided,
while very detailed, doesn't really make clear to me what is going
wrong. In particular, considering there is a NULL pointer there
(which I can only guess is the new pin_setup pointer), I would
have expected it to crash earlier. Hence I'm attaching a patch
which closes a hole in the logic, but is unlikely to address your
problem. The added debugging output should help, but please
also make available the xen-syms image in case the patch - as
expected - doesn't help and that system of yours still crashes.
Jan
[-- Attachment #2: AMD-IOMMU-IVHD-special-debug.patch --]
[-- Type: text/plain, Size: 4216 bytes --]
--- a/xen/drivers/passthrough/amd/iommu_acpi.c
+++ b/xen/drivers/passthrough/amd/iommu_acpi.c
@@ -354,9 +354,8 @@ static int __init parse_ivmd_block(const
base = start_addr & PAGE_MASK;
limit = (start_addr + mem_length - 1) & PAGE_MASK;
- AMD_IOMMU_DEBUG("IVMD Block: Type %#x\n",ivmd_block->header.type);
- AMD_IOMMU_DEBUG(" Start_Addr_Phys %#lx\n", start_addr);
- AMD_IOMMU_DEBUG(" Mem_Length %#lx\n", mem_length);
+ AMD_IOMMU_DEBUG("IVMD Block: type %#x phys %#lx len %#lx\n",
+ ivmd_block->header.type, start_addr, mem_length);
if ( ivmd_block->header.flags & ACPI_IVMD_EXCLUSION_RANGE )
iw = ir = IOMMU_CONTROL_ENABLED;
@@ -551,8 +550,8 @@ static u16 __init parse_ivhd_device_alia
return 0;
}
- AMD_IOMMU_DEBUG(" Dev_Id Range: %#x -> %#x\n", first_bdf, last_bdf);
- AMD_IOMMU_DEBUG(" Dev_Id Alias: %#x\n", alias_id);
+ AMD_IOMMU_DEBUG(" Dev_Id Range: %#x -> %#x alias %#x\n",
+ first_bdf, last_bdf, alias_id);
for ( bdf = first_bdf; bdf <= last_bdf; bdf++ )
add_ivrs_mapping_entry(bdf, alias_id, range->alias.header.data_setting,
@@ -654,6 +653,9 @@ static u16 __init parse_ivhd_device_spec
return 0;
}
+ AMD_IOMMU_DEBUG("IVHD Special: %04x:%02x:%02x.%u variety %#x handle %#x\n",
+ seg, PCI_BUS(bdf), PCI_SLOT(bdf), PCI_FUNC(bdf),
+ special->variety, special->handle);
add_ivrs_mapping_entry(bdf, bdf, special->header.data_setting, iommu);
switch ( special->variety )
@@ -758,10 +760,9 @@ static int __init parse_ivhd_block(const
{
ivhd_device = (const void *)((const u8 *)ivhd_block + block_length);
- AMD_IOMMU_DEBUG( "IVHD Device Entry:\n");
- AMD_IOMMU_DEBUG( " Type %#x\n", ivhd_device->header.type);
- AMD_IOMMU_DEBUG( " Dev_Id %#x\n", ivhd_device->header.id);
- AMD_IOMMU_DEBUG( " Flags %#x\n", ivhd_device->header.data_setting);
+ AMD_IOMMU_DEBUG("IVHD Device Entry: type %#x id %#x flags %#x\n",
+ ivhd_device->header.type, ivhd_device->header.id,
+ ivhd_device->header.data_setting);
switch ( ivhd_device->header.type )
{
@@ -890,6 +891,7 @@ static int __init parse_ivrs_table(struc
{
const struct acpi_ivrs_header *ivrs_block;
unsigned long length;
+ unsigned int apic;
int error = 0;
BUG_ON(!table);
@@ -903,11 +905,9 @@ static int __init parse_ivrs_table(struc
{
ivrs_block = (struct acpi_ivrs_header *)((u8 *)table + length);
- AMD_IOMMU_DEBUG("IVRS Block:\n");
- AMD_IOMMU_DEBUG(" Type %#x\n", ivrs_block->type);
- AMD_IOMMU_DEBUG(" Flags %#x\n", ivrs_block->flags);
- AMD_IOMMU_DEBUG(" Length %#x\n", ivrs_block->length);
- AMD_IOMMU_DEBUG(" Dev_Id %#x\n", ivrs_block->device_id);
+ AMD_IOMMU_DEBUG("IVRS Block: type %#x flags %#x len %#x id %#x\n",
+ ivrs_block->type, ivrs_block->flags,
+ ivrs_block->length, ivrs_block->device_id);
if ( table->length < (length + ivrs_block->length) )
{
@@ -922,6 +922,29 @@ static int __init parse_ivrs_table(struc
length += ivrs_block->length;
}
+ /* Each IO-APIC must have been mentioned in the table. */
+ for ( apic = 0; !error && apic < nr_ioapics; ++apic )
+ {
+ if ( !nr_ioapic_entries[apic] ||
+ ioapic_sbdf[IO_APIC_ID(apic)].pin_setup )
+ continue;
+
+ printk(XENLOG_ERR "IVHD Error: no information for IO-APIC %#x\n",
+ IO_APIC_ID(apic));
+ if ( amd_iommu_perdev_intremap )
+ error = -ENXIO;
+ else
+ {
+ ioapic_sbdf[IO_APIC_ID(apic)].pin_setup = xzalloc_array(
+ unsigned long, BITS_TO_LONGS(nr_ioapic_entries[apic]));
+ if ( !ioapic_sbdf[IO_APIC_ID(apic)].pin_setup )
+ {
+ printk(XENLOG_ERR "IVHD Error: Out of memory\n");
+ error = -ENOMEM;
+ }
+ }
+ }
+
return error;
}
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Xen-unstable boot panic due to changeset 26517 AMD, IOMMU: Clean up old entries in remapping tables when creating new one
2013-02-06 10:23 ` Jan Beulich
@ 2013-02-06 11:24 ` Sander Eikelenboom
2013-02-06 12:52 ` Jan Beulich
0 siblings, 1 reply; 9+ messages in thread
From: Sander Eikelenboom @ 2013-02-06 11:24 UTC (permalink / raw)
To: Jan Beulich; +Cc: Boris Ostrovsky, xen-devel
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
Wednesday, February 6, 2013, 11:23:29 AM, you wrote:
>>>> On 05.02.13 at 22:19, Sander Eikelenboom <linux@eikelenboom.it> wrote:
>> Boot of xen-unstable is broken due to changeset 26517 on a AMD 890-FX
>> motherboard.
>> The serial log is attached.
> Yeah, we were afraid of that. Unfortunately the log you provided,
> while very detailed, doesn't really make clear to me what is going
> wrong. In particular, considering there is a NULL pointer there
> (which I can only guess is the new pin_setup pointer), I would
> have expected it to crash earlier. Hence I'm attaching a patch
> which closes a hole in the logic, but is unlikely to address your
> problem. The added debugging output should help, but please
> also make available the xen-syms image in case the patch - as
> expected - doesn't help and that system of yours still crashes.
> Jan
Hmm with the patch it does boot, but disables the I/O virtualization.
Output of xl-dmesg attached, do you still need a xen-sums of the situation without the debug patch (where it does crash) ?
--
Sander
[-- Attachment #2: xl-dmesg.txt --]
[-- Type: text/plain, Size: 37599 bytes --]
__ __ _ _ _____ _ _ _
\ \/ /___ _ __ | || | |___ / _ _ _ __ ___| |_ __ _| |__ | | ___
\ // _ \ '_ \ | || |_ |_ \ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
/ \ __/ | | | |__ _| ___) |__| |_| | | | \__ \ || (_| | |_) | | __/
/_/\_\___|_| |_| |_|(_)____/ \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
(XEN) Xen version 4.3-unstable (root@dyndns.org) (gcc (Debian 4.4.5-8) 4.4.5) debug=y Wed Feb 6 11:55:18 CET 2013
(XEN) Latest ChangeSet: Tue Feb 05 15:47:41 2013 +0000 26520:6c1b12c884b4
(XEN) Bootloader: GRUB 1.98+20100804-14+squeeze1
(XEN) Command line: dom0_mem=1024M,max:1024M loglvl=all loglvl_guest=all console_timestamps vga=gfx-1280x1024x32 cpuidle cpufreq=xen noreboot debug lapic=debug apic_verbosity=debug apic=debug iommu=on,verbose,debug,amd-iommu-debug com1=38400,8n1 console=vga,com1
(XEN) Video information:
(XEN) VGA is graphics mode 1280x1024, 32 bpp
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 2 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009f000 (usable)
(XEN) 000000000009f000 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000aff90000 (usable)
(XEN) 00000000aff90000 - 00000000aff9e000 (ACPI data)
(XEN) 00000000aff9e000 - 00000000affe0000 (ACPI NVS)
(XEN) 00000000affe0000 - 00000000b0000000 (reserved)
(XEN) 00000000ffe00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000250000000 (usable)
(XEN) ACPI: RSDP 000FB100, 0014 (r0 ACPIAM)
(XEN) ACPI: RSDT AFF90000, 0048 (r1 MSI OEMSLIC 20100913 MSFT 97)
(XEN) ACPI: FACP AFF90200, 0084 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) ACPI: DSDT AFF905E0, 9427 (r1 A7640 A7640100 100 INTL 20051117)
(XEN) ACPI: FACS AFF9E000, 0040
(XEN) ACPI: APIC AFF90390, 0088 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) ACPI: MCFG AFF90420, 003C (r1 7640MS OEMMCFG 20100913 MSFT 97)
(XEN) ACPI: SLIC AFF90460, 0176 (r1 MSI OEMSLIC 20100913 MSFT 97)
(XEN) ACPI: OEMB AFF9E040, 0072 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) ACPI: SRAT AFF9A5E0, 0108 (r3 AMD FAM_F_10 2 AMD 1)
(XEN) ACPI: HPET AFF9A6F0, 0038 (r1 7640MS OEMHPET 20100913 MSFT 97)
(XEN) ACPI: IVRS AFF9A730, 00F8 (r1 AMD RD890S 202031 AMD 0)
(XEN) ACPI: SSDT AFF9A830, 0DA4 (r1 A M I POWERNOW 1 AMD 1)
(XEN) System RAM: 8191MB (8387772kB)
(XEN) SRAT: PXM 0 -> APIC 0 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 1 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 2 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 3 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 4 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 5 -> Node 0
(XEN) SRAT: Node 0 PXM 0 0-a0000
(XEN) SRAT: Node 0 PXM 0 100000-b0000000
(XEN) SRAT: Node 0 PXM 0 100000000-250000000
(XEN) NUMA: Allocated memnodemap from 24d8d0000 - 24d8d3000
(XEN) NUMA: Using 8 for the hash shift.
(XEN) Domain heap initialised
(XEN) vesafb: framebuffer at 0xfb000000, mapped to 0xffff82c000081000, using 6144k, total 14336k
(XEN) vesafb: mode is 1280x1024x32, linelength=5120, font 8x16
(XEN) vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
(XEN) found SMP MP-table at 000ff780
(XEN) DMI present.
(XEN) APIC boot state is 'xapic'
(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[aff9e00c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
(XEN) Processor #4 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
(XEN) Processor #5 0:10 APIC version 16
(XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
(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 low 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: 0x8300 base: 0xfed00000
(XEN) Table is not found!
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 6 CPUs (0 hotplug CPUs)
(XEN) mapped APIC to ffff82c3ffdfb000 (fee00000)
(XEN) mapped IOAPIC to ffff82c3ffdfa000 (fec00000)
(XEN) mapped IOAPIC to ffff82c3ffdf9000 (fec20000)
(XEN) IRQ limits: 56 GSI, 1112 MSI/MSI-X
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3200.187 MHz processor.
(XEN) Initing memory sharing.
(XEN) AMD Fam10h machine check reporting enabled
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff
(XEN) PCI: Not using MCFG for segment 0000 bus 00-ff
(XEN) AMD-Vi: Found MSI capability block at 0x54
(XEN) AMD-Vi: ACPI Table:
(XEN) AMD-Vi: Signature IVRS
(XEN) AMD-Vi: Length 0xf8
(XEN) AMD-Vi: Revision 0x1
(XEN) AMD-Vi: CheckSum 0x50
(XEN) AMD-Vi: OEM_Id AMD
(XEN) AMD-Vi: OEM_Table_Id RD890S
(XEN) AMD-Vi: OEM_Revision 0x202031
(XEN) AMD-Vi: Creator_Id AMD
(XEN) AMD-Vi: Creator_Revision 0
(XEN) AMD-Vi: IVRS Block: type 0x10 flags 0x3e len 0xc8 id 0x2
(XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0 -> 0x2
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x10 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xb00 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x18 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x900 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x43 id 0xa08 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0xa08 -> 0xaff alias 0xa00
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x28 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x800 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x30 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x700 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x50 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x600 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x58 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x500 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x500 -> 0x501
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x68 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x400 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x88 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x90 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x90 -> 0x92
(XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x98 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x98 -> 0x9a
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa0 flags 0xd7
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa1 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa2 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa3 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa4 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x43 id 0x300 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x300 -> 0x3ff alias 0xa4
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa5 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa8 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa9 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x100 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0xb0 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0xb0 -> 0xb2
(XEN) AMD-Vi: IVHD Device Entry: type 0 id 0 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0xd7
(XEN) AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x2 handle 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0
(XEN) AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x7
(XEN) IVHD Error: no information for IO-APIC 0x6
(XEN) AMD-Vi: Error initialization
(XEN) I/O virtualisation disabled
(XEN) Getting VERSION: 80050010
(XEN) Getting VERSION: 80050010
(XEN) Getting ID: 0
(XEN) Getting LVT0: 700
(XEN) Getting LVT1: 400
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 0x4 after: 0
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) init IO_APIC IRQs
(XEN) IO-APIC (apicid-pin) 6-0, 6-16, 6-17, 6-18, 6-19, 6-20, 6-21, 6-22, 6-23, 7-0, 7-1, 7-2, 7-3, 7-4, 7-5, 7-6, 7-7, 7-8, 7-9, 7-10, 7-11, 7-12, 7-13, 7-14, 7-15, 7-16, 7-17, 7-18, 7-19, 7-20, 7-21, 7-22, 7-23, 7-24, 7-25, 7-26, 7-27, 7-28, 7-29, 7-30, 7-31 not connected.
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) number of MP IRQ sources: 15.
(XEN) number of IO-APIC #6 registers: 24.
(XEN) number of IO-APIC #7 registers: 32.
(XEN) testing the IO APIC.......................
(XEN) IO APIC #6......
(XEN) .... register #00: 06000000
(XEN) ....... : physical APIC id: 06
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 00178021
(XEN) ....... : max redirection entries: 0017
(XEN) ....... : PRQ implemented: 1
(XEN) ....... : IO APIC version: 0021
(XEN) .... register #02: 06000000
(XEN) ....... : arbitration: 06
(XEN) .... register #03: 07000000
(XEN) ....... : Boot DT : 0
(XEN) .... IRQ redirection table:
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
(XEN) 00 000 00 1 0 0 0 0 0 0 00
(XEN) 01 001 01 0 0 0 0 0 1 1 28
(XEN) 02 001 01 0 0 0 0 0 1 1 F0
(XEN) 03 001 01 0 0 0 0 0 1 1 30
(XEN) 04 001 01 0 0 0 0 0 1 1 F1
(XEN) 05 001 01 0 0 0 0 0 1 1 38
(XEN) 06 001 01 0 0 0 0 0 1 1 40
(XEN) 07 001 01 0 0 0 0 0 1 1 48
(XEN) 08 001 01 0 0 0 0 0 1 1 50
(XEN) 09 001 01 1 1 0 1 0 1 1 58
(XEN) 0a 001 01 0 0 0 0 0 1 1 60
(XEN) 0b 001 01 0 0 0 0 0 1 1 68
(XEN) 0c 001 01 0 0 0 0 0 1 1 70
(XEN) 0d 001 01 0 0 0 0 0 1 1 78
(XEN) 0e 001 01 0 0 0 0 0 1 1 88
(XEN) 0f 001 01 0 0 0 0 0 1 1 90
(XEN) 10 000 00 1 0 0 0 0 0 0 00
(XEN) 11 000 00 1 0 0 0 0 0 0 00
(XEN) 12 000 00 1 0 0 0 0 0 0 00
(XEN) 13 000 00 1 0 0 0 0 0 0 00
(XEN) 14 000 00 1 0 0 0 0 0 0 00
(XEN) 15 000 00 1 0 0 0 0 0 0 00
(XEN) 16 000 00 1 0 0 0 0 0 0 00
(XEN) 17 000 00 1 0 0 0 0 0 0 00
(XEN) IO APIC #7......
(XEN) .... register #00: 07000000
(XEN) ....... : physical APIC id: 07
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 001F8021
(XEN) ....... : max redirection entries: 001F
(XEN) ....... : PRQ implemented: 1
(XEN) ....... : IO APIC version: 0021
(XEN) .... register #02: 00000000
(XEN) ....... : arbitration: 00
(XEN) .... IRQ redirection table:
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
(XEN) 00 000 00 1 0 0 0 0 0 0 00
(XEN) 01 000 00 1 0 0 0 0 0 0 00
(XEN) 02 000 00 1 0 0 0 0 0 0 00
(XEN) 03 000 00 1 0 0 0 0 0 0 00
(XEN) 04 000 00 1 0 0 0 0 0 0 00
(XEN) 05 000 00 1 0 0 0 0 0 0 00
(XEN) 06 000 00 1 0 0 0 0 0 0 00
(XEN) 07 000 00 1 0 0 0 0 0 0 00
(XEN) 08 000 00 1 0 0 0 0 0 0 00
(XEN) 09 000 00 1 0 0 0 0 0 0 00
(XEN) 0a 000 00 1 0 0 0 0 0 0 00
(XEN) 0b 000 00 1 0 0 0 0 0 0 00
(XEN) 0c 000 00 1 0 0 0 0 0 0 00
(XEN) 0d 000 00 1 0 0 0 0 0 0 00
(XEN) 0e 000 00 1 0 0 0 0 0 0 00
(XEN) 0f 000 00 1 0 0 0 0 0 0 00
(XEN) 10 000 00 1 0 0 0 0 0 0 00
(XEN) 11 000 00 1 0 0 0 0 0 0 00
(XEN) 12 000 00 1 0 0 0 0 0 0 00
(XEN) 13 000 00 1 0 0 0 0 0 0 00
(XEN) 14 000 00 1 0 0 0 0 0 0 00
(XEN) 15 000 00 1 0 0 0 0 0 0 00
(XEN) 16 000 00 1 0 0 0 0 0 0 00
(XEN) 17 000 00 1 0 0 0 0 0 0 00
(XEN) 18 000 00 1 0 0 0 0 0 0 00
(XEN) 19 000 00 1 0 0 0 0 0 0 00
(XEN) 1a 000 00 1 0 0 0 0 0 0 00
(XEN) 1b 000 00 1 0 0 0 0 0 0 00
(XEN) 1c 000 00 1 0 0 0 0 0 0 00
(XEN) 1d 000 00 1 0 0 0 0 0 0 00
(XEN) 1e 000 00 1 0 0 0 0 0 0 00
(XEN) 1f 000 00 1 0 0 0 0 0 0 00
(XEN) Using vector-based indexing
(XEN) IRQ to pin mappings:
(XEN) IRQ240 -> 0:2
(XEN) IRQ40 -> 0:1
(XEN) IRQ48 -> 0:3
(XEN) IRQ241 -> 0:4
(XEN) IRQ56 -> 0:5
(XEN) IRQ64 -> 0:6
(XEN) IRQ72 -> 0:7
(XEN) IRQ80 -> 0:8
(XEN) IRQ88 -> 0:9
(XEN) IRQ96 -> 0:10
(XEN) IRQ104 -> 0:11
(XEN) IRQ112 -> 0:12
(XEN) IRQ120 -> 0:13
(XEN) IRQ136 -> 0:14
(XEN) IRQ144 -> 0:15
(XEN) .................................... done.
(XEN) Using local APIC timer interrupts.
(XEN) calibrating APIC timer ...
(XEN) ..... CPU clock speed is 3200.1736 MHz.
(XEN) ..... host bus clock speed is 200.0107 MHz.
(XEN) ..... bus_scale = 0xccd7
(XEN) [2013-02-06 11:07:16] Platform timer is 14.318MHz HPET
(XEN) [2013-02-06 11:07:16] Allocated console ring of 64 KiB.
(XEN) [2013-02-06 11:07:16] HVM: ASIDs enabled.
(XEN) [2013-02-06 11:07:16] SVM: Supported advanced features:
(XEN) [2013-02-06 11:07:16] - Nested Page Tables (NPT)
(XEN) [2013-02-06 11:07:16] - Last Branch Record (LBR) Virtualisation
(XEN) [2013-02-06 11:07:16] - Next-RIP Saved on #VMEXIT
(XEN) [2013-02-06 11:07:16] - Pause-Intercept Filter
(XEN) [2013-02-06 11:07:16] HVM: SVM enabled
(XEN) [2013-02-06 11:07:16] HVM: Hardware Assisted Paging (HAP) detected
(XEN) [2013-02-06 11:07:16] HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) [2013-02-06 11:07:15] masked ExtINT on CPU#1
(XEN) [2013-02-06 11:07:16] microcode: CPU1 collect_cpu_info: patch_id=0x10000bf
(XEN) [2013-02-06 11:07:15] masked ExtINT on CPU#2
(XEN) [2013-02-06 11:07:16] microcode: CPU2 collect_cpu_info: patch_id=0x10000bf
(XEN) [2013-02-06 11:07:15] masked ExtINT on CPU#3
(XEN) [2013-02-06 11:07:16] microcode: CPU3 collect_cpu_info: patch_id=0x10000bf
(XEN) [2013-02-06 11:07:15] masked ExtINT on CPU#4
(XEN) [2013-02-06 11:07:16] microcode: CPU4 collect_cpu_info: patch_id=0x10000bf
(XEN) [2013-02-06 11:07:15] masked ExtINT on CPU#5
(XEN) [2013-02-06 11:07:16] Brought up 6 CPUs
(XEN) [2013-02-06 11:07:16] microcode: CPU5 collect_cpu_info: patch_id=0x10000bf
(XEN) [2013-02-06 11:07:16] HPET: 3 timers (3 will be used for broadcast)
(XEN) [2013-02-06 11:07:16] ACPI sleep modes: S3
(XEN) [2013-02-06 11:07:16] MCA: Use hw thresholding to adjust polling frequency
(XEN) [2013-02-06 11:07:16] mcheck_poll: Machine check polling timer started.
(XEN) [2013-02-06 11:07:16] Xenoprofile: Failed to setup IBS LVT offset, IBSCTL = 0xffffffff
(XEN) [2013-02-06 11:07:16] *** LOADING DOMAIN 0 ***
(XEN) [2013-02-06 11:07:16] elf_parse_binary: phdr: paddr=0x1000000 memsz=0xdc4000
(XEN) [2013-02-06 11:07:16] elf_parse_binary: phdr: paddr=0x1e00000 memsz=0xe50f0
(XEN) [2013-02-06 11:07:17] elf_parse_binary: phdr: paddr=0x1ee6000 memsz=0x13dc0
(XEN) [2013-02-06 11:07:17] elf_parse_binary: phdr: paddr=0x1efa000 memsz=0xe22000
(XEN) [2013-02-06 11:07:17] elf_parse_binary: memory: 0x1000000 -> 0x2d1c000
(XEN) [2013-02-06 11:07:17] elf_xen_parse_note: GUEST_OS = "linux"
(XEN) [2013-02-06 11:07:17] elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) [2013-02-06 11:07:17] elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) [2013-02-06 11:07:17] elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) [2013-02-06 11:07:17] elf_xen_parse_note: ENTRY = 0xffffffff81efa210
(XEN) [2013-02-06 11:07:17] elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
(XEN) [2013-02-06 11:07:17] elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
(XEN) [2013-02-06 11:07:17] elf_xen_parse_note: PAE_MODE = "yes"
(XEN) [2013-02-06 11:07:17] elf_xen_parse_note: LOADER = "generic"
(XEN) [2013-02-06 11:07:17] elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) [2013-02-06 11:07:17] elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) [2013-02-06 11:07:17] elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
(XEN) [2013-02-06 11:07:17] elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) [2013-02-06 11:07:17] elf_xen_addr_calc_check: addresses:
(XEN) [2013-02-06 11:07:17] virt_base = 0xffffffff80000000
(XEN) [2013-02-06 11:07:17] elf_paddr_offset = 0x0
(XEN) [2013-02-06 11:07:17] virt_offset = 0xffffffff80000000
(XEN) [2013-02-06 11:07:17] virt_kstart = 0xffffffff81000000
(XEN) [2013-02-06 11:07:17] virt_kend = 0xffffffff82d1c000
(XEN) [2013-02-06 11:07:17] virt_entry = 0xffffffff81efa210
(XEN) [2013-02-06 11:07:17] p2m_base = 0xffffffffffffffff
(XEN) [2013-02-06 11:07:17] Xen kernel: 64-bit, lsb, compat32
(XEN) [2013-02-06 11:07:17] Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2d1c000
(XEN) [2013-02-06 11:07:17] PHYSICAL MEMORY ARRANGEMENT:
(XEN) [2013-02-06 11:07:17] Dom0 alloc.: 0000000240000000->0000000244000000 (242516 pages to be allocated)
(XEN) [2013-02-06 11:07:17] Init. ramdisk: 000000024f354000->000000024ffffc00
(XEN) [2013-02-06 11:07:17] VIRTUAL MEMORY ARRANGEMENT:
(XEN) [2013-02-06 11:07:17] Loaded kernel: ffffffff81000000->ffffffff82d1c000
(XEN) [2013-02-06 11:07:17] Init. ramdisk: ffffffff82d1c000->ffffffff839c7c00
(XEN) [2013-02-06 11:07:17] Phys-Mach map: ffffffff839c8000->ffffffff83bc8000
(XEN) [2013-02-06 11:07:17] Start info: ffffffff83bc8000->ffffffff83bc84b4
(XEN) [2013-02-06 11:07:17] Page tables: ffffffff83bc9000->ffffffff83bec000
(XEN) [2013-02-06 11:07:17] Boot stack: ffffffff83bec000->ffffffff83bed000
(XEN) [2013-02-06 11:07:17] TOTAL: ffffffff80000000->ffffffff84000000
(XEN) [2013-02-06 11:07:17] ENTRY ADDRESS: ffffffff81efa210
(XEN) [2013-02-06 11:07:17] Dom0 has maximum 6 VCPUs
(XEN) [2013-02-06 11:07:17] elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81dc4000
(XEN) [2013-02-06 11:07:17] elf_load_binary: phdr 1 at 0xffffffff81e00000 -> 0xffffffff81ee50f0
(XEN) [2013-02-06 11:07:17] elf_load_binary: phdr 2 at 0xffffffff81ee6000 -> 0xffffffff81ef9dc0
(XEN) [2013-02-06 11:07:17] elf_load_binary: phdr 3 at 0xffffffff81efa000 -> 0xffffffff81fb3000
(XEN) [2013-02-06 11:07:17] Scrubbing Free RAM: .......................................................................done.
(XEN) [2013-02-06 11:07:19] Initial low memory virq threshold set at 0x4000 pages.
(XEN) [2013-02-06 11:07:19] Std. Loglevel: All
(XEN) [2013-02-06 11:07:19] Guest Loglevel: All
(XEN) [2013-02-06 11:07:19] Xen is relinquishing VGA console.
(XEN) [2013-02-06 11:07:19] *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) [2013-02-06 11:07:19] Freed 252kB init memory.
(XEN) [2013-02-06 11:07:19] IOAPIC[0]: Set PCI routing entry (6-9 -> 0x58 -> IRQ 9 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:19] traps.c:2495:d0 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:07:19] PCI add device 0000:00:00.0
(XEN) [2013-02-06 11:07:19] PCI add device 0000:00:00.2
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:02.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:03.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:05.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:06.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:0a.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:0b.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:0d.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:11.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:12.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:12.2
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:13.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:13.2
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:14.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:14.1
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:14.2
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:14.3
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:14.4
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:14.5
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:15.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:16.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:16.2
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:18.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:18.1
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:18.2
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:18.3
(XEN) [2013-02-06 11:07:20] PCI add device 0000:00:18.4
(XEN) [2013-02-06 11:07:20] PCI add device 0000:0b:00.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:09:00.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:0a:01.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:0a:01.1
(XEN) [2013-02-06 11:07:20] PCI add device 0000:0a:01.2
(XEN) [2013-02-06 11:07:20] PCI add device 0000:08:00.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:07:00.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:06:00.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:05:00.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:05:00.1
(XEN) [2013-02-06 11:07:20] PCI add device 0000:04:00.0
(XEN) [2013-02-06 11:07:20] PCI add device 0000:03:06.0
(XEN) [2013-02-06 11:07:20] IOAPIC[0]: Set PCI routing entry (6-8 -> 0x50 -> IRQ 8 Mode:0 Active:0)
(XEN) [2013-02-06 11:07:20] IOAPIC[0]: Set PCI routing entry (6-13 -> 0x78 -> IRQ 13 Mode:0 Active:0)
(XEN) [2013-02-06 11:07:20] IOAPIC[1]: Set PCI routing entry (7-28 -> 0xb0 -> IRQ 52 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:20] IOAPIC[1]: Set PCI routing entry (7-29 -> 0xb8 -> IRQ 53 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:20] IOAPIC[1]: Set PCI routing entry (7-30 -> 0xc0 -> IRQ 54 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:20] IOAPIC[0]: Set PCI routing entry (6-16 -> 0xc8 -> IRQ 16 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:20] IOAPIC[0]: Set PCI routing entry (6-18 -> 0xd0 -> IRQ 18 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:20] IOAPIC[0]: Set PCI routing entry (6-17 -> 0xd8 -> IRQ 17 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:20] IOAPIC[1]: Set PCI routing entry (7-5 -> 0x21 -> IRQ 29 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:20] IOAPIC[1]: Set PCI routing entry (7-6 -> 0x29 -> IRQ 30 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:20] IOAPIC[1]: Set PCI routing entry (7-7 -> 0x31 -> IRQ 31 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:20] IOAPIC[1]: Set PCI routing entry (7-16 -> 0x39 -> IRQ 40 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:21] IOAPIC[0]: Set PCI routing entry (6-22 -> 0x81 -> IRQ 22 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:21] IOAPIC[1]: Set PCI routing entry (7-9 -> 0x89 -> IRQ 33 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:21] IOAPIC[1]: Set PCI routing entry (7-8 -> 0x91 -> IRQ 32 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:21] IOAPIC[1]: Set PCI routing entry (7-23 -> 0x99 -> IRQ 47 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:21] IOAPIC[0]: Set PCI routing entry (6-19 -> 0xa1 -> IRQ 19 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:22] IOAPIC[1]: Set PCI routing entry (7-22 -> 0xb1 -> IRQ 46 Mode:1 Active:1)
(XEN) [2013-02-06 11:07:22] IOAPIC[1]: Set PCI routing entry (7-27 -> 0xc1 -> IRQ 51 Mode:1 Active:1)
(XEN) [2013-02-06 11:09:05] traps.c:2495:d1 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:09:11] traps.c:2495:d2 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:09:17] traps.c:2495:d3 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:09:24] traps.c:2495:d4 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:09:29] traps.c:2495:d5 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:09:31] grant_table.c:289:d0 Increased maptrack size to 2 frames
(XEN) [2013-02-06 11:09:34] traps.c:2495:d6 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:09:41] traps.c:2495:d7 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:09:47] traps.c:2495:d8 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:09:53] traps.c:2495:d9 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:10:00] traps.c:2495:d10 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:10:06] grant_table.c:289:d0 Increased maptrack size to 3 frames
(XEN) [2013-02-06 11:10:06] traps.c:2495:d11 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:10:13] traps.c:2495:d12 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:10:19] traps.c:2495:d13 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:10:28] traps.c:2495:d14 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000ffff.
(XEN) [2013-02-06 11:10:29] grant_table.c:289:d0 Increased maptrack size to 4 frames
(XEN) [2013-02-06 11:10:38] pt_irq_create_bind failed (-3) for dom15
(XEN) [2013-02-06 11:10:38] pt_irq_create_bind failed (-3) for dom15
(XEN) [2013-02-06 11:10:38] HVM15: HVM Loader
(XEN) [2013-02-06 11:10:38] HVM15: Detected Xen v4.3-unstable
(XEN) [2013-02-06 11:10:38] HVM15: Xenbus rings @0xfeffc000, event channel 5
(XEN) [2013-02-06 11:10:38] HVM15: System requested SeaBIOS
(XEN) [2013-02-06 11:10:38] HVM15: CPU speed is 3200 MHz
(XEN) [2013-02-06 11:10:38] irq.c:270: Dom15 PCI link 0 changed 0 -> 5
(XEN) [2013-02-06 11:10:38] HVM15: PCI-ISA link 0 routed to IRQ5
(XEN) [2013-02-06 11:10:38] irq.c:270: Dom15 PCI link 1 changed 0 -> 10
(XEN) [2013-02-06 11:10:38] HVM15: PCI-ISA link 1 routed to IRQ10
(XEN) [2013-02-06 11:10:38] irq.c:270: Dom15 PCI link 2 changed 0 -> 11
(XEN) [2013-02-06 11:10:38] HVM15: PCI-ISA link 2 routed to IRQ11
(XEN) [2013-02-06 11:10:38] irq.c:270: Dom15 PCI link 3 changed 0 -> 5
(XEN) [2013-02-06 11:10:38] HVM15: PCI-ISA link 3 routed to IRQ5
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 01:2 INTD->IRQ5
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 01:3 INTA->IRQ10
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 03:0 INTA->IRQ5
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 04:0 INTA->IRQ5
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 05:0 INTA->IRQ10
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 06:0 INTA->IRQ11
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 02:0 bar 10 size lx: 02000000
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 03:0 bar 14 size lx: 01000000
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 06:0 bar 10 size lx: 00200000
(XEN) [2013-02-06 11:10:38] memory_map:add: dom15 gfn=f3000 mfn=f9a00 nr=200
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 04:0 bar 10 size lx: 00020000
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 04:0 bar 30 size lx: 00020000
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 02:0 bar 30 size lx: 00010000
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 05:0 bar 10 size lx: 00002000
(XEN) [2013-02-06 11:10:38] memory_map:add: dom15 gfn=f3250 mfn=f98fe nr=1
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 02:0 bar 14 size lx: 00001000
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 03:0 bar 10 size lx: 00000100
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 04:0 bar 14 size lx: 00000040
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 01:2 bar 20 size lx: 00000020
(XEN) [2013-02-06 11:10:38] HVM15: pci dev 01:1 bar 20 size lx: 00000010
(XEN) [2013-02-06 11:10:38] HVM15: Multiprocessor initialisation:
(XEN) [2013-02-06 11:10:38] HVM15: - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) [2013-02-06 11:10:38] HVM15: - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) [2013-02-06 11:10:38] HVM15: - CPU2 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) [2013-02-06 11:10:38] HVM15: Testing HVM environment:
(XEN) [2013-02-06 11:10:38] HVM15: - REP INSB across page boundaries ... passed
(XEN) [2013-02-06 11:10:38] HVM15: - GS base MSRs and SWAPGS ... passed
(XEN) [2013-02-06 11:10:38] HVM15: Passed 2 of 2 tests
(XEN) [2013-02-06 11:10:38] HVM15: Writing SMBIOS tables ...
(XEN) [2013-02-06 11:10:38] HVM15: Loading SeaBIOS ...
(XEN) [2013-02-06 11:10:38] HVM15: Creating MP tables ...
(XEN) [2013-02-06 11:10:38] HVM15: Loading ACPI ...
(XEN) [2013-02-06 11:10:38] HVM15: vm86 TSS at fc00a080
(XEN) [2013-02-06 11:10:38] HVM15: BIOS map:
(XEN) [2013-02-06 11:10:38] HVM15: 10000-100d3: Scratch space
(XEN) [2013-02-06 11:10:38] HVM15: e0000-fffff: Main BIOS
(XEN) [2013-02-06 11:10:38] HVM15: E820 table:
(XEN) [2013-02-06 11:10:38] HVM15: [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) [2013-02-06 11:10:38] HVM15: HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) [2013-02-06 11:10:38] HVM15: [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) [2013-02-06 11:10:38] HVM15: [02]: 00000000:00100000 - 00000000:2f800000: RAM
(XEN) [2013-02-06 11:10:38] HVM15: HOLE: 00000000:2f800000 - 00000000:fc000000
(XEN) [2013-02-06 11:10:38] HVM15: [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) [2013-02-06 11:10:38] HVM15: Invoking SeaBIOS ...
(XEN) [2013-02-06 11:10:38] HVM15: SeaBIOS (version rel-1.7.1-88-g4bd8aeb-20130127_204611-serveerstertje)
(XEN) [2013-02-06 11:10:38] HVM15:
(XEN) [2013-02-06 11:10:38] HVM15: Found Xen hypervisor signature at 40000000
(XEN) [2013-02-06 11:10:38] HVM15: xen: copy e820...
(XEN) [2013-02-06 11:10:38] HVM15: Ram Size=0x2f800000 (0x0000000000000000 high)
(XEN) [2013-02-06 11:10:38] HVM15: Relocating low data from 0x000e2af0 to 0x000ef780 (size 2164)
(XEN) [2013-02-06 11:10:38] HVM15: Relocating init from 0x000e3364 to 0x2f7e2400 (size 56028)
(XEN) [2013-02-06 11:10:38] HVM15: CPU Mhz=3199
(XEN) [2013-02-06 11:10:38] HVM15: Found 10 PCI devices (max PCI bus is 00)
(XEN) [2013-02-06 11:10:38] HVM15: Allocated Xen hypercall page at 2f7ff000
(XEN) [2013-02-06 11:10:38] HVM15: Detected Xen v4.3-unstable
(XEN) [2013-02-06 11:10:38] HVM15: Found 3 cpu(s) max supported 3 cpu(s)
(XEN) [2013-02-06 11:10:38] HVM15: xen: copy BIOS tables...
(XEN) [2013-02-06 11:10:38] HVM15: Copying SMBIOS entry point from 0x00010010 to 0x000fdb10
(XEN) [2013-02-06 11:10:38] HVM15: Copying MPTABLE from 0xfc001190/fc0011a0 to 0x000fda00
(XEN) [2013-02-06 11:10:38] HVM15: Copying PIR from 0x00010030 to 0x000fd980
(XEN) [2013-02-06 11:10:38] HVM15: Copying ACPI RSDP from 0x000100b0 to 0x000fd950
(XEN) [2013-02-06 11:10:38] HVM15: Scan for VGA option rom
(XEN) [2013-02-06 11:10:38] HVM15: Running option rom at c000:0003
(XEN) [2013-02-06 11:10:38] stdvga.c:147:d15 entering stdvga and caching modes
(XEN) [2013-02-06 11:10:38] HVM15: Turning on vga text mode console
(XEN) [2013-02-06 11:10:38] HVM15: SeaBIOS (version rel-1.7.1-88-g4bd8aeb-20130127_204611-serveerstertje)
(XEN) [2013-02-06 11:10:38] HVM15: Machine UUID 323468fc-14f4-4f6e-b324-b2fbb9342b90
(XEN) [2013-02-06 11:10:38] HVM15: UHCI init on dev 00:01.2 (io=c140)
(XEN) [2013-02-06 11:10:38] HVM15: Found 1 lpt ports
(XEN) [2013-02-06 11:10:38] HVM15: Found 1 serial ports
(XEN) [2013-02-06 11:10:38] HVM15: Searching bootorder for: /pci@i0cf8/isa@1/fdc@03f0/floppy@0
(XEN) [2013-02-06 11:10:38] HVM15: ATA controller 1 at 1f0/3f4/c160 (irq 14 dev 9)
(XEN) [2013-02-06 11:10:38] HVM15: ATA controller 2 at 170/374/c168 (irq 15 dev 9)
(XEN) [2013-02-06 11:10:38] HVM15: ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (10240 MiBytes)
(XEN) [2013-02-06 11:10:38] HVM15: Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
(XEN) [2013-02-06 11:10:38] HVM15: ata0-1: QEMU HARDDISK ATA-7 Hard-Disk (300 GiBytes)
(XEN) [2013-02-06 11:10:38] HVM15: Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1
(XEN) [2013-02-06 11:10:38] HVM15: DVD/CD [ata1-0: QEMU DVD-ROM ATAPI-4 DVD/CD]
(XEN) [2013-02-06 11:10:38] HVM15: Searching bootorder for: /pci@i0cf8/*@1,1/drive@1/disk@0
(XEN) [2013-02-06 11:10:38] HVM15: PS2 keyboard initialized
(XEN) [2013-02-06 11:10:38] HVM15: All threads complete.
(XEN) [2013-02-06 11:10:38] HVM15: Scan for option roms
(XEN) [2013-02-06 11:10:38] HVM15: Running option rom at c900:0003
(XEN) [2013-02-06 11:10:38] HVM15: pmm call arg1=1
(XEN) [2013-02-06 11:10:38] HVM15: pmm call arg1=0
(XEN) [2013-02-06 11:10:38] HVM15: pmm call arg1=1
(XEN) [2013-02-06 11:10:38] HVM15: pmm call arg1=0
(XEN) [2013-02-06 11:10:38] HVM15: Searching bootorder for: /pci@i0cf8/*@4
(XEN) [2013-02-06 11:10:38] HVM15:
(XEN) [2013-02-06 11:10:38] HVM15: Press F12 for boot menu.
(XEN) [2013-02-06 11:10:38] HVM15:
(XEN) [2013-02-06 11:10:41] HVM15: Searching bootorder for: HALT
(XEN) [2013-02-06 11:10:41] HVM15: drive 0x000fd8d0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=20971520
(XEN) [2013-02-06 11:10:41] HVM15:
(XEN) [2013-02-06 11:10:41] HVM15: drive 0x000fd8a0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=62914560
(XEN) [2013-02-06 11:10:41] HVM15: 0
(XEN) [2013-02-06 11:10:41] HVM15: Space available for UMB: 000ca000-000ee800
(XEN) [2013-02-06 11:10:41] HVM15: Returned 61440 bytes of ZoneHigh
(XEN) [2013-02-06 11:10:41] HVM15: e820 map has 6 items:
(XEN) [2013-02-06 11:10:41] HVM15: 0: 0000000000000000 - 000000000009fc00 = 1 RAM
(XEN) [2013-02-06 11:10:41] HVM15: 1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
(XEN) [2013-02-06 11:10:41] HVM15: 2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
(XEN) [2013-02-06 11:10:41] HVM15: 3: 0000000000100000 - 000000002f7ff000 = 1 RAM
(XEN) [2013-02-06 11:10:41] HVM15: 4: 000000002f7ff000 - 000000002f800000 = 2 RESERVED
(XEN) [2013-02-06 11:10:41] HVM15: 5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
(XEN) [2013-02-06 11:10:41] HVM15: enter handle_19:
(XEN) [2013-02-06 11:10:41] HVM15: NULL
(XEN) [2013-02-06 11:10:41] HVM15: Booting from Hard Disk...
(XEN) [2013-02-06 11:10:41] HVM15: Booting from 0000:7c00
(XEN) [2013-02-06 11:10:41] grant_table.c:289:d0 Increased maptrack size to 5 frames
(XEN) [2013-02-06 11:10:57] irq.c:375: Dom15 callback via changed to Direct Vector 0xf3
(XEN) [2013-02-06 11:11:00] memory_map:remove: dom15 gfn=f3250 mfn=f98fe nr=1
(XEN) [2013-02-06 11:11:00] memory_map:add: dom15 gfn=f3250 mfn=f98fe nr=1
(XEN) [2013-02-06 11:11:00] memory_map:remove: dom15 gfn=f3250 mfn=f98fe nr=1
(XEN) [2013-02-06 11:11:00] memory_map:add: dom15 gfn=f3250 mfn=f98fe nr=1
(XEN) [2013-02-06 11:11:00] memory_map:remove: dom15 gfn=f3250 mfn=f98fe nr=1
(XEN) [2013-02-06 11:11:00] memory_map:add: dom15 gfn=f3250 mfn=f98fe nr=1
(XEN) [2013-02-06 11:11:00] memory_map:remove: dom15 gfn=f3250 mfn=f98fe nr=1
(XEN) [2013-02-06 11:11:00] memory_map:add: dom15 gfn=f3250 mfn=f98fe nr=1
(XEN) [2013-02-06 11:11:00] memory_map:remove: dom15 gfn=f3250 mfn=f98fe nr=1
(XEN) [2013-02-06 11:11:00] memory_map:add: dom15 gfn=f3250 mfn=f98fe nr=1
(XEN) [2013-02-06 11:11:00] memory_map:remove: dom15 gfn=f3250 mfn=f98fe nr=1
(XEN) [2013-02-06 11:11:00] memory_map:add: dom15 gfn=f3250 mfn=f98fe nr=1
(XEN) [2013-02-06 11:11:00] memory_map:remove: dom15 gfn=f3000 mfn=f9a00 nr=200
(XEN) [2013-02-06 11:11:00] memory_map:add: dom15 gfn=f3000 mfn=f9a00 nr=200
(XEN) [2013-02-06 11:11:00] memory_map:remove: dom15 gfn=f3000 mfn=f9a00 nr=200
(XEN) [2013-02-06 11:11:00] memory_map:add: dom15 gfn=f3000 mfn=f9a00 nr=200
(XEN) [2013-02-06 11:11:00] memory_map:remove: dom15 gfn=f3000 mfn=f9a00 nr=200
(XEN) [2013-02-06 11:11:00] memory_map:add: dom15 gfn=f3000 mfn=f9a00 nr=200
(XEN) [2013-02-06 11:11:00] memory_map:remove: dom15 gfn=f3000 mfn=f9a00 nr=200
(XEN) [2013-02-06 11:11:00] memory_map:add: dom15 gfn=f3000 mfn=f9a00 nr=200
(XEN) [2013-02-06 11:11:00] memory_map:remove: dom15 gfn=f3000 mfn=f9a00 nr=200
(XEN) [2013-02-06 11:11:00] memory_map:add: dom15 gfn=f3000 mfn=f9a00 nr=200
(XEN) [2013-02-06 11:11:00] memory_map:remove: dom15 gfn=f3000 mfn=f9a00 nr=200
(XEN) [2013-02-06 11:11:00] memory_map:add: dom15 gfn=f3000 mfn=f9a00 nr=200
(XEN) [2013-02-06 11:11:00] irq.c:270: Dom15 PCI link 0 changed 5 -> 0
(XEN) [2013-02-06 11:11:00] irq.c:270: Dom15 PCI link 1 changed 10 -> 0
(XEN) [2013-02-06 11:11:00] irq.c:270: Dom15 PCI link 2 changed 11 -> 0
(XEN) [2013-02-06 11:11:00] irq.c:270: Dom15 PCI link 3 changed 5 -> 0
(XEN) [2013-02-06 11:11:02] pt_irq_create_bind failed (-3) for dom15
(XEN) [2013-02-06 11:11:02] pt_irq_create_bind failed (-3) for dom15
(XEN) [2013-02-06 11:11:02] pt_irq_create_bind failed (-3) for dom15
(XEN) [2013-02-06 11:11:02] pt_irq_create_bind failed (-3) for dom15
(XEN) [2013-02-06 11:11:37] grant_table.c:289:d0 Increased maptrack size to 6 frames
(XEN) [2013-02-06 11:12:40] grant_table.c:289:d0 Increased maptrack size to 7 frames
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Xen-unstable boot panic due to changeset 26517 AMD, IOMMU: Clean up old entries in remapping tables when creating new one
2013-02-06 11:24 ` Sander Eikelenboom
@ 2013-02-06 12:52 ` Jan Beulich
2013-02-06 13:39 ` Sander Eikelenboom
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Jan Beulich @ 2013-02-06 12:52 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Boris Ostrovsky, xen-devel
>>> On 06.02.13 at 12:24, Sander Eikelenboom <linux@eikelenboom.it> wrote:
> Hmm with the patch it does boot, but disables the I/O virtualization.
Good. While, as said before, I still don't understand why it didn't
crash earlier without that patch, I'm glad it's fixed. Will post the
patch for inclusion momentarily.
> Output of xl-dmesg attached, do you still need a xen-sums of the situation
> without the debug patch (where it does crash) ?
And you can't expect much else with broken ACPI tables:
(XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0xd7
(XEN) AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x2 handle 0
This is a HPET entry.
(XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0
(XEN) AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x7
And this is an entry for IO-APIC #2 (ID 7), whereas FADT says
(XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
so the IOMMU table is lacking an entry for the first IO-APIC, and
without that we can't set up per-device interrupt remapping (in
which case we choose to disable the IOMMU altogether, albeit it
had been questioned whether that isn't making a bad situation
worse in some cases).
If you want the IOMMU back (at the price of re-opening the
security issue described in XSA-36), you'd have to pass
"iommu=amd-iommu-perdev-intremap" to the hypervisor.
Jan
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Xen-unstable boot panic due to changeset 26517 AMD, IOMMU: Clean up old entries in remapping tables when creating new one
2013-02-06 12:52 ` Jan Beulich
@ 2013-02-06 13:39 ` Sander Eikelenboom
2013-02-06 21:34 ` Sander Eikelenboom
2013-02-08 20:14 ` Suravee Suthikulanit
2 siblings, 0 replies; 9+ messages in thread
From: Sander Eikelenboom @ 2013-02-06 13:39 UTC (permalink / raw)
To: Jan Beulich; +Cc: Boris Ostrovsky, xen-devel
Wednesday, February 6, 2013, 1:52:38 PM, you wrote:
>>>> On 06.02.13 at 12:24, Sander Eikelenboom <linux@eikelenboom.it> wrote:
>> Hmm with the patch it does boot, but disables the I/O virtualization.
> Good. While, as said before, I still don't understand why it didn't
> crash earlier without that patch, I'm glad it's fixed. Will post the
> patch for inclusion momentarily.
>> Output of xl-dmesg attached, do you still need a xen-sums of the situation
>> without the debug patch (where it does crash) ?
> And you can't expect much else with broken ACPI tables:
Hmm yeah it seems anything that has to remotely depend on anything bios related is pretty doomed, on both intel and AMD.
And support/willingness to correct things, is limited, not to say non-existent.
> (XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0xd7
> (XEN) AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x2 handle 0
> This is a HPET entry.
> (XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0
> (XEN) AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x7
> And this is an entry for IO-APIC #2 (ID 7), whereas FADT says
> (XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
> (XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
> (XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
> so the IOMMU table is lacking an entry for the first IO-APIC, and
> without that we can't set up per-device interrupt remapping (in
> which case we choose to disable the IOMMU altogether, albeit it
> had been questioned whether that isn't making a bad situation
> worse in some cases).
> If you want the IOMMU back (at the price of re-opening the
> security issue described in XSA-36), you'd have to pass
> "iommu=amd-iommu-perdev-intremap" to the hypervisor.
Will try some newer bios, although i tried that in the past and it resulted in a non-booting system.
But perhaps things have changed for the better.
Thanks so far !
--
Sander
> Jan
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Xen-unstable boot panic due to changeset 26517 AMD, IOMMU: Clean up old entries in remapping tables when creating new one
2013-02-06 12:52 ` Jan Beulich
2013-02-06 13:39 ` Sander Eikelenboom
@ 2013-02-06 21:34 ` Sander Eikelenboom
2013-02-08 20:14 ` Suravee Suthikulanit
2 siblings, 0 replies; 9+ messages in thread
From: Sander Eikelenboom @ 2013-02-06 21:34 UTC (permalink / raw)
To: Jan Beulich; +Cc: Boris Ostrovsky, xen-devel
Wednesday, February 6, 2013, 1:52:38 PM, you wrote:
>>>> On 06.02.13 at 12:24, Sander Eikelenboom <linux@eikelenboom.it> wrote:
>> Hmm with the patch it does boot, but disables the I/O virtualization.
> Good. While, as said before, I still don't understand why it didn't
> crash earlier without that patch, I'm glad it's fixed. Will post the
> patch for inclusion momentarily.
>> Output of xl-dmesg attached, do you still need a xen-sums of the situation
>> without the debug patch (where it does crash) ?
> And you can't expect much else with broken ACPI tables:
> (XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0xd7
> (XEN) AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x2 handle 0
> This is a HPET entry.
> (XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0
> (XEN) AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x7
> And this is an entry for IO-APIC #2 (ID 7), whereas FADT says
> (XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
> (XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
> (XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
> so the IOMMU table is lacking an entry for the first IO-APIC, and
> without that we can't set up per-device interrupt remapping (in
> which case we choose to disable the IOMMU altogether, albeit it
> had been questioned whether that isn't making a bad situation
> worse in some cases).
> If you want the IOMMU back (at the price of re-opening the
> security issue described in XSA-36), you'd have to pass
> "iommu=amd-iommu-perdev-intremap" to the hypervisor.
Just for the record (the list), that should be iommu=no-amd-iommu-perdev-intremap
> Jan
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Xen-unstable boot panic due to changeset 26517 AMD, IOMMU: Clean up old entries in remapping tables when creating new one
2013-02-06 12:52 ` Jan Beulich
2013-02-06 13:39 ` Sander Eikelenboom
2013-02-06 21:34 ` Sander Eikelenboom
@ 2013-02-08 20:14 ` Suravee Suthikulanit
2013-02-08 20:34 ` Sander Eikelenboom
2013-02-12 8:50 ` Jan Beulich
2 siblings, 2 replies; 9+ messages in thread
From: Suravee Suthikulanit @ 2013-02-08 20:14 UTC (permalink / raw)
To: xen-devel, JBeulich; +Cc: linux, boris.ostrovsky, Hurwitz, Sherry
On 2/6/2013 6:52 AM, Jan Beulich wrote:
>>>> On 06.02.13 at 12:24, Sander Eikelenboom <linux@eikelenboom.it> wrote:
>> Hmm with the patch it does boot, but disables the I/O virtualization.
> Good. While, as said before, I still don't understand why it didn't
> crash earlier without that patch, I'm glad it's fixed. Will post the
> patch for inclusion momentarily.
>
>> Output of xl-dmesg attached, do you still need a xen-sums of the situation
>> without the debug patch (where it does crash) ?
> And you can't expect much else with broken ACPI tables:
>
> (XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0xd7
> (XEN) AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x2 handle 0
>
> This is a HPET entry.
>
> (XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0
> (XEN) AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x7
>
> And this is an entry for IO-APIC #2 (ID 7), whereas FADT says
>
> (XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
> (XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
> (XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
>
> so the IOMMU table is lacking an entry for the first IO-APIC, and
> without that we can't set up per-device interrupt remapping (in
> which case we choose to disable the IOMMU altogether, albeit it
> had been questioned whether that isn't making a bad situation
> worse in some cases).
>
> If you want the IOMMU back (at the price of re-opening the
> security issue described in XSA-36), you'd have to pass
> "iommu=amd-iommu-perdev-intremap" to the hypervisor.
>
> Jan
Jan,
It seems that all the recent issues with the AMD IOMMU regarding IOAPIC are
mainly caused by mismatch information from IVRS and MADT. Xen sets up "nr_ioapics"
by checking the number of IOAPICs reported in MADT, while the amd/iommu_acpi.c
code uses information from the IVHD entries of the IVRS to initialize IOMMU.
Most of the issues we are seeing are often triggered when platform BIOS decides
to disable one of the two IOAPICs in the RD890s configuration. I am trying to
summarize the cases here:
CASE1: BIOS disable the IOAPIC in the southbridge (SB8X0 chipset)
This is the case we are seeing here with the AMD 890-FX motherboard.
Here, the MADT is reporting 2 IOAPICs as shown by the message:
(XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
However, when Xen tries to setup the IOMMU interrupt remapping table using IVHD
entries, there is only one IOAPIC (IOAPIC 1 with apic_id 7).
(XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0
(XEN) AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x7
(XEN) IVHD Error: no information for IO-APIC 0x6
(XEN) AMD-Vi: Error initialization
In this case, if we should be able to look at the IVHD to correlate IOAPIC ID (0 or 1)
from the "handle" field and map it back to the BDF to setup the remapping table.
CASE2: BIOS disable the IOAPIC in the I/O bridge (RD890s chipset)
This happens in the case when we were testing the per-device interrupt remapping
table patch. (I think this is the issue you might be seeing in one of the Xen test system.)
In this case, the MADT reports 1 IOAPIC while the IVRS contains two IVHD entries with both
entries have the "hahandle" set to "0". Unfortunately, in this case, there is no obvious
workaround, and the current solution is to disable IOMMU.
I am working with some of the BIOS engineers and vendors to try to issue root-cause
and provide BIOS update.
Jan, Sander:
Could you please provide the system information:
1. Motherboard vendor
2. BIOS version
Thank you,
Suravee
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Xen-unstable boot panic due to changeset 26517 AMD, IOMMU: Clean up old entries in remapping tables when creating new one
2013-02-08 20:14 ` Suravee Suthikulanit
@ 2013-02-08 20:34 ` Sander Eikelenboom
2013-02-12 8:50 ` Jan Beulich
1 sibling, 0 replies; 9+ messages in thread
From: Sander Eikelenboom @ 2013-02-08 20:34 UTC (permalink / raw)
To: Suravee Suthikulanit
Cc: boris.ostrovsky, Hurwitz, Sherry, JBeulich, xen-devel
Friday, February 8, 2013, 9:14:35 PM, you wrote:
> On 2/6/2013 6:52 AM, Jan Beulich wrote:
>>>>> On 06.02.13 at 12:24, Sander Eikelenboom <linux@eikelenboom.it> wrote:
>>> Hmm with the patch it does boot, but disables the I/O virtualization.
>> Good. While, as said before, I still don't understand why it didn't
>> crash earlier without that patch, I'm glad it's fixed. Will post the
>> patch for inclusion momentarily.
>>
>>> Output of xl-dmesg attached, do you still need a xen-sums of the situation
>>> without the debug patch (where it does crash) ?
>> And you can't expect much else with broken ACPI tables:
>>
>> (XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0xd7
>> (XEN) AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x2 handle 0
>>
>> This is a HPET entry.
>>
>> (XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0
>> (XEN) AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x7
>>
>> And this is an entry for IO-APIC #2 (ID 7), whereas FADT says
>>
>> (XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
>> (XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
>> (XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
>> (XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
>>
>> so the IOMMU table is lacking an entry for the first IO-APIC, and
>> without that we can't set up per-device interrupt remapping (in
>> which case we choose to disable the IOMMU altogether, albeit it
>> had been questioned whether that isn't making a bad situation
>> worse in some cases).
>>
>> If you want the IOMMU back (at the price of re-opening the
>> security issue described in XSA-36), you'd have to pass
>> "iommu=amd-iommu-perdev-intremap" to the hypervisor.
>>
>> Jan
> Jan,
> It seems that all the recent issues with the AMD IOMMU regarding IOAPIC are
> mainly caused by mismatch information from IVRS and MADT. Xen sets up "nr_ioapics"
> by checking the number of IOAPICs reported in MADT, while the amd/iommu_acpi.c
> code uses information from the IVHD entries of the IVRS to initialize IOMMU.
> Most of the issues we are seeing are often triggered when platform BIOS decides
> to disable one of the two IOAPICs in the RD890s configuration. I am trying to
> summarize the cases here:
> CASE1: BIOS disable the IOAPIC in the southbridge (SB8X0 chipset)
> This is the case we are seeing here with the AMD 890-FX motherboard.
> Here, the MADT is reporting 2 IOAPICs as shown by the message:
> (XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
> (XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
> (XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
> However, when Xen tries to setup the IOMMU interrupt remapping table using IVHD
> entries, there is only one IOAPIC (IOAPIC 1 with apic_id 7).
> (XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0
> (XEN) AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x7
> (XEN) IVHD Error: no information for IO-APIC 0x6
> (XEN) AMD-Vi: Error initialization
> In this case, if we should be able to look at the IVHD to correlate IOAPIC ID (0 or 1)
> from the "handle" field and map it back to the BDF to setup the remapping table.
> CASE2: BIOS disable the IOAPIC in the I/O bridge (RD890s chipset)
> This happens in the case when we were testing the per-device interrupt remapping
> table patch. (I think this is the issue you might be seeing in one of the Xen test system.)
> In this case, the MADT reports 1 IOAPIC while the IVRS contains two IVHD entries with both
> entries have the "hahandle" set to "0". Unfortunately, in this case, there is no obvious
> workaround, and the current solution is to disable IOMMU.
> I am working with some of the BIOS engineers and vendors to try to issue root-cause
> and provide BIOS update.
> Jan, Sander:
> Could you please provide the system information:
> 1. Motherboard vendor
> 2. BIOS version
Suravee,
1. My motherboard is a "890FXA-GD70" from MSI (http://www.msi.com/product/mb/890FXA-GD70.html)
2. As for the bios version:
- I'm currently running 1.8 beta1, it's a beta bios. It boots and works, but has the problem you described above.
- I have tried all newer bioses up to the latest bios (1.15), but with these bioses the system halts during boot when the iommu option in the bios is enabled.
With xen it halts right after the "(XEN) IVHD Error: no information for IO-APIC 0x6", so it could be another problem initializing the iommu i'm afraid.
It also halts while trying to boot a baremetal linux kernel.
When the iommu is disabled it boots fine.
I hope a more direct approach of the bios engineers has some result, customer support most of the time have no clue and react like a firewall, bouncing and dropping all the packets :-(
Thanks for trying and picking it up !
--
Sander
> Thank you,
> Suravee
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Xen-unstable boot panic due to changeset 26517 AMD, IOMMU: Clean up old entries in remapping tables when creating new one
2013-02-08 20:14 ` Suravee Suthikulanit
2013-02-08 20:34 ` Sander Eikelenboom
@ 2013-02-12 8:50 ` Jan Beulich
1 sibling, 0 replies; 9+ messages in thread
From: Jan Beulich @ 2013-02-12 8:50 UTC (permalink / raw)
To: Suravee Suthikulanit; +Cc: linux, boris.ostrovsky, xen-devel, Sherry Hurwitz
>>> On 08.02.13 at 21:14, Suravee Suthikulanit <suravee.suthikulpanit@amd.com> wrote:
> CASE1: BIOS disable the IOAPIC in the southbridge (SB8X0 chipset)
> This is the case we are seeing here with the AMD 890-FX motherboard.
> Here, the MADT is reporting 2 IOAPICs as shown by the message:
>
> (XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
> (XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
> (XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
>
> However, when Xen tries to setup the IOMMU interrupt remapping table using
> IVHD
> entries, there is only one IOAPIC (IOAPIC 1 with apic_id 7).
>
> (XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0
> (XEN) AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x7
> (XEN) IVHD Error: no information for IO-APIC 0x6
> (XEN) AMD-Vi: Error initialization
But you realize that it's the _first_ IO-APIC that has no
representation in IVRS? And it can only reasonably be the 2nd
that the BIOS might choose to disable (or else legacy interrupts,
including the timer, wouldn't work).
> In this case, if we should be able to look at the IVHD to correlate IOAPIC
> ID (0 or 1)
> from the "handle" field and map it back to the BDF to setup the remapping
> table.
I don't currently see how you would figure out the BDF for the
IO-APIC. Care to explain?
Jan
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2013-02-12 8:50 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-02-05 21:19 Xen-unstable boot panic due to changeset 26517 AMD, IOMMU: Clean up old entries in remapping tables when creating new one Sander Eikelenboom
2013-02-06 10:23 ` Jan Beulich
2013-02-06 11:24 ` Sander Eikelenboom
2013-02-06 12:52 ` Jan Beulich
2013-02-06 13:39 ` Sander Eikelenboom
2013-02-06 21:34 ` Sander Eikelenboom
2013-02-08 20:14 ` Suravee Suthikulanit
2013-02-08 20:34 ` Sander Eikelenboom
2013-02-12 8:50 ` Jan Beulich
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.