From: "Eric Houby" <ehouby@yahoo.com>
To: 'Ian Campbell' <Ian.Campbell@citrix.com>,
'Jan Beulich' <JBeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [TestDay] Xen crash on boot
Date: Tue, 21 Jan 2014 03:39:20 -0700 [thread overview]
Message-ID: <000001cf1695$0c960450$25c20cf0$@yahoo.com> (raw)
In-Reply-To: <1390297542.20516.90.camel@kazak.uk.xensource.com>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
> -----Original Message-----
> From: Ian Campbell [mailto:Ian.Campbell@citrix.com]
> Sent: Tuesday, January 21, 2014 2:46 AM
> To: Jan Beulich
> Cc: ehouby@yahoo.com; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] [TestDay] Xen crash on boot
>
> On Tue, 2014-01-21 at 09:32 +0000, Jan Beulich wrote:
> > >>> On 20.01.14 at 20:06, Eric Houby <ehouby@yahoo.com> wrote:
> > > Testing the xen 4.4 RC2 RPMs on Fedora 20 caused xen to crash at boot.
> > > Screen shot of the crash is attached. Hardware is a Gigabyte
> > > GA-890FXA-UD5. Adding iommu=no-amd-iommu-perdev-intremap to
> xen
> > > command line allows the system to boot as expected.
> >
> > For analyzing this we need a full serial log
>
> See http://wiki.xen.org/wiki/Xen_Serial_Console for how to configure such a
> thing.
>
> > (with "iommu=debug" in
> > place on the Xen command line), not just a screen shot.
> >
> > Jan
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
>
Xen console logs are attached.
Thanks,
Eric
[-- Attachment #2: xen44crash.txt --]
[-- Type: text/plain, Size: 13136 bytes --]
astar login: (XEN) Domain 0 shutdown: rebooting machine.
Xen 4.4-rc2-0.rc2.1.fc20
(XEN) Xen version 4.4-rc2 (mockbuild@[unknown]) (gcc (GCC) 4.8.2 20131212 (Red Hat 4.8.2-7)) debug=y Thu Jan 16 19:37:57 UTC 2014
(XEN) Latest ChangeSet:
(XEN) Bootloader: GRUB 2.00
(XEN) Command line: placeholder dom0_mem=2048M,max:2048M dom0_max_vcpus=2 dom0_vcpus_pin loglvl=all guest_loglvl=all iommu=debug,verbose com1=38400,8n1,pci console=com1
(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 3 MBR signatures
(XEN) Found 3 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 0000000000097000 (usable)
(XEN) 000000000009f800 - 00000000000a0000 (reserved)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000afcf0000 (usable)
(XEN) 00000000afcf0000 - 00000000afcf1000 (ACPI NVS)
(XEN) 00000000afcf1000 - 00000000afd00000 (ACPI data)
(XEN) 00000000afd00000 - 00000000afe00000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fec00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000250000000 (usable)
(XEN) ACPI: RSDP 000F6080, 0014 (r0 GBT )
(XEN) ACPI: RSDT AFCF1000, 0040 (r1 GBT GBTUACPI 42302E31 GBTU 1010101)
(XEN) ACPI: FACP AFCF1080, 0074 (r1 GBT GBTUACPI 42302E31 GBTU 1010101)
(XEN) ACPI: DSDT AFCF1100, 7BE1 (r1 GBT GBTUACPI 1000 MSFT 3000000)
(XEN) ACPI: FACS AFCF0000, 0040
(XEN) ACPI: HPET AFCF8DC0, 0038 (r1 GBT GBTUACPI 42302E31 GBTU 98)
(XEN) ACPI: MCFG AFCF8E00, 003C (r1 GBT GBTUACPI 42302E31 GBTU 1010101)
(XEN) ACPI: MATS AFCF8E40, 0034 (r1 GBT 0 0)
(XEN) ACPI: TAMG AFCF8EB0, 048A (r1 GBT GBT B0 5455312E BG 53450101)
(XEN) ACPI: APIC AFCF8D00, 00BC (r1 GBT GBTUACPI 42302E31 GBTU 1010101)
(XEN) ACPI: IVRS AFCF93B0, 00D8 (r1 AMD RD890S 202031 AMD 0)
(XEN) System RAM: 8188MB (8385052kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-0000000250000000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000f4670
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x808
(XEN) ACPI: SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
(XEN) ACPI: wakeup_vec[afcf000c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
(XEN) Processor #1 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
(XEN) Processor #3 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
(XEN) Processor #4 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
(XEN) Processor #5 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23
(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 1 I/O APICs
(XEN) ACPI: HPET id: 0x10b9a201 base: 0xfed00000
(XEN) ERST table was not found
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 8 CPUs (2 hotplug CPUs)
(XEN) IRQ limits: 24 GSI, 1144 MSI/MSI-X
(XEN) XSM Framework v1.0.0 initialized
(XEN) Flask: No policy file found. Disabling Flask.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2812.987 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: MCFG area at e0000000 reserved in E820
(XEN) PCI: 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 0xd8
(XEN) AMD-Vi: Revision 0x1
(XEN) AMD-Vi: CheckSum 0x6f
(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 0xa8 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 0x3 id 0x100 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x100 -> 0x101
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x20 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x200 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x28 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x30 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x38 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x500 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x48 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 0x700 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x700 -> 0x701
(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 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 0 id 0 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x43 id 0x800 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x800 -> 0x8ff alias 0xa4
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa5 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 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 0x2
(XEN) AMD-Vi: IOMMU 0 Enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
(XEN) ...trying to set up timer (IRQ0) through the 8259A ... failed.
(XEN) ...trying to set up timer as Virtual Wire IRQ... works.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 64 KiB.
(XEN) HVM: ASIDs enabled.
(XEN) SVM: Supported advanced features:
(XEN) - Nested Page Tables (NPT)
(XEN) - Last Branch Record (LBR) Virtualisation
(XEN) - Next-RIP Saved on #VMEXIT
(XEN) - Pause-Intercept Filter
(XEN) HVM: SVM enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) HVM: PVH mode not supported on this platform
(XEN) microcode: CPU1 collect_cpu_info: patch_id=0x10000bf
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0xa0, fault address = 0xfdf8010140, flags = 0x8
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0xa0, fault address = 0xfdf8010140, flags = 0x8
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0xa0, fault address = 0xfdf8010140, flags = 0x8
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0xa0, fault address = 0xfdf8010140, flags = 0x8
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0xa0, fault address = 0xfdf8010140, flags = 0x8
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0xa0, fault address = 0xfdf8010140, flags = 0x8
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0xa0, fault address = 0xfdf8010140, flags = 0x8
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0xa0, fault address = 0xfdf8010140, flags = 0x8
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0xa0, fault address = 0xfdf8010140, flags = 0x8
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0xa0, fault address = 0xfdf8010140, flags = 0x8
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0xa0, fault address = 0xfdf8010140, flags = 0x8
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0xa0, fault address = 0xfdf8010140, flags = 0x8
(XEN) spurious 8259A interrupt: IRQ7.
(XEN) CPU2: No irq handler for vector e7 (IRQ -2147483648)
(XEN) microcode: CPU2 collect_cpu_info: patch_id=0x10000bf
(XEN) CPU3: No irq handler for vector e7 (IRQ -2147483648)
(XEN) microcode: CPU3 collect_cpu_info: patch_id=0x10000bf
(XEN) CPU4: No irq handler for vector e7 (IRQ -2147483648)
(XEN) microcode: CPU4 collect_cpu_info: patch_id=0x10000bf
(XEN) CPU5: No irq handler for vector e7 (IRQ -2147483648)
(XEN) Brought up 6 CPUs
(XEN) microcode: CPU5 collect_cpu_info: patch_id=0x10000bf
(XEN) Assertion 'get_rte_index(rte) == offset' failed at iommu_intr.c:188
(XEN) ----[ Xen-4.4-rc2 x86_64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e008:[<ffff82d080152dd0>] amd_iommu_ioapic_update_ire+0x41d/0x5b4
(XEN) RFLAGS: 0000000000010002 CONTEXT: hypervisor
(XEN) rax: 0000000000000000 rbx: 0000000000000015 rcx: ffff830247340000
(XEN) rdx: 0000000000000000 rsi: 0000000000000000 rdi: ffff830247366004
(XEN) rbp: ffff82d0802e7d98 rsp: ffff82d0802e7ce8 r8: 0000000000000004
(XEN) r9: ffff82d080287161 r10: 000000000000000f r11: ffff82d080287960
(XEN) r12: 0000000000000000 r13: 0000000000000001 r14: 0000000000000014
(XEN) r15: 0000000000205000 cr0: 000000008005003b cr4: 00000000000006f0
(XEN) cr3: 00000000afa98000 cr2: 0000000000000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008
(XEN) Xen stack trace from rsp=ffff82d0802e7ce8:
(XEN) ffff82d000000001 0000000000000086 ffff830200000001 0000000000000046
(XEN) ffff830247340070 0000000000010000 0000000000000000 0000000000000000
(XEN) 000182d000000014 ffff83024d02b600 0000000147380000 0000000000000000
(XEN) 0000000200000001 ffff83024d0253c0 ffff82d0802e7da8 0100000000010000
(XEN) 0000000000000001 ffff83024733d430 0000000000000004 ffff82cffffff010
(XEN) ffff82cffffff000 0000000001000000 ffff82d0802e7da8 ffff82d080144f76
(XEN) ffff82d0802e7df8 ffff82d080175f4b 0000000000000296 ffff830247380000
(XEN) 0000000000000008 0000000000000002 0000000000000000 ffff82d080284ec0
(XEN) ffff82d080284ec0 ffff830247380000 ffff82d0802e7e38 ffff82d080176fca
(XEN) ffff82d0802e7e58 0000000000000008 ffff8302473c9820 0000000000000008
(XEN) ffff82d0802891e0 ffff830000086fb0 ffff82d0802e7e48 ffff82d0802bed37
(XEN) ffff82d0802e7f08 ffff82d0802be41d 0000000000000000 0000000000100000
(XEN) ffff83000177fc58 ffff830000086fb0 ffff82d0802d7488 0000000001281000
(XEN) 0000000000250000 0000000000000000 ffff83000000000c ffff830000086d50
(XEN) 0000000000000005 ffff830000086ef0 0000000800000000 000000010000006e
(XEN) 0000000000000003 00000000000002f8 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 ffff82d0801000b5 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN) [<ffff82d080152dd0>] amd_iommu_ioapic_update_ire+0x41d/0x5b4
(XEN) [<ffff82d080144f76>] iommu_update_ire_from_apic+0x28/0x2a
(XEN) [<ffff82d080175f4b>] set_ioapic_affinity_irq+0xa8/0x1e0
(XEN) [<ffff82d080176fca>] setup_ioapic_dest+0x89/0xc3
(XEN) [<ffff82d0802bed37>] smp_cpus_done+0x51/0x61
(XEN) [<ffff82d0802be41d>] __start_xen+0x261a/0x2938
(XEN) [<ffff82d0801000b5>] __high_start+0xa1/0xa3
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Assertion 'get_rte_index(rte) == offset' failed at iommu_intr.c:188
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-01-21 10:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 19:06 [TestDay] Xen crash on boot Eric Houby
2014-01-21 9:31 ` [TestDay] Xen crash on boot in get_rte_index without no-amd-iommu-perdev-intremap Ian Campbell
2014-01-21 15:17 ` Eric Houby
2014-01-22 9:11 ` Jan Beulich
2014-01-21 9:32 ` [TestDay] Xen crash on boot Jan Beulich
2014-01-21 9:45 ` Ian Campbell
2014-01-21 10:39 ` Eric Houby [this message]
2014-01-21 21:38 ` Konrad Rzeszutek Wilk
2014-01-22 8:30 ` Jan Beulich
2014-01-23 5:40 ` Eric Houby
2014-01-23 11:16 ` Jan Beulich
2014-01-24 0:47 ` Eric Houby
2014-01-24 1:44 ` Andrew Cooper
2014-01-24 4:50 ` Eric Houby
2014-01-24 9:27 ` Jan Beulich
2014-01-24 8:34 ` Jan Beulich
2014-01-24 13:24 ` Jan Beulich
2014-01-26 1:10 ` Eric Houby
2014-02-06 16:44 ` Eric Houby
2014-02-06 16:51 ` Jan Beulich
2014-01-26 0:46 ` Eric Houby
2014-01-24 9:01 ` Jan Beulich
2014-01-26 0:59 ` Eric Houby
2014-01-27 17:14 ` George Dunlap
2014-01-27 17:30 ` Processed: " xen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001cf1695$0c960450$25c20cf0$@yahoo.com' \
--to=ehouby@yahoo.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.