From: povder <povder@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>, xen-devel@lists.xen.org
Subject: Re: Xen 4.2.1 boot failure with IOMMU enabled
Date: Wed, 13 Feb 2013 19:21:02 +0100 [thread overview]
Message-ID: <CACvNfPwB4+5mJ1qaLjf55QTK+Nno7XDKHoFkJzPYt-xURi3Cdg@mail.gmail.com> (raw)
In-Reply-To: <511B5EE102000078000BDE8A@nat28.tlf.novell.com>
>> 2013/2/13 Jan Beulich <JBeulich@suse.com>:
>>> I wonder how native Linux with
>>> IOMMU enabled does in that situation...
>>>
Here is full boot log of latest centos stable kernel:
http://pastebin.com/raw.php?i=RnrMFXqf
I had to set amd_iommu=on and amd_iommu_dump (to dump ACPI table) -
undocumented kernel options.
Interesting part in my opinion:
calling pci_iommu_init+0x0/0x21 @ 1
AMD-Vi: device: 00:00.2 cap: 0040 seg: 0 flags: 3e info 1300
AMD-Vi: mmio-addr: 00000000f6000000
AMD-Vi: DEV_SELECT_RANGE_START devid: 00:00.0 flags: 00
AMD-Vi: DEV_RANGE_END devid: 00:00.2
AMD-Vi: DEV_SELECT devid: 00:04.0 flags: 00
AMD-Vi: DEV_SELECT devid: 06:00.0 flags: 00
AMD-Vi: DEV_SELECT devid: 00:06.0 flags: 00
AMD-Vi: DEV_SELECT devid: 05:00.0 flags: 00
AMD-Vi: DEV_SELECT devid: 00:07.0 flags: 00
AMD-Vi: DEV_SELECT devid: 04:00.0 flags: 00
AMD-Vi: DEV_SELECT devid: 00:0b.0 flags: 00
AMD-Vi: DEV_SELECT_RANGE_START devid: 03:00.0 flags: 00
AMD-Vi: DEV_RANGE_END devid: 03:00.1
AMD-Vi: DEV_SELECT devid: 00:0d.0 flags: 00
AMD-Vi: DEV_SELECT devid: 02:00.0 flags: 00
AMD-Vi: DEV_SELECT devid: 00:11.0 flags: 00
AMD-Vi: DEV_SELECT_RANGE_START devid: 00:12.0 flags: 00
AMD-Vi: DEV_RANGE_END devid: 00:12.2
AMD-Vi: DEV_SELECT_RANGE_START devid: 00:13.0 flags: 00
AMD-Vi: DEV_RANGE_END devid: 00:13.2
AMD-Vi: DEV_SELECT devid: 00:14.0 flags: d7
AMD-Vi: DEV_SELECT devid: 00:14.1 flags: 00
AMD-Vi: DEV_SELECT devid: 00:14.2 flags: 00
AMD-Vi: DEV_SELECT devid: 00:14.3 flags: 00
AMD-Vi: DEV_SELECT devid: 00:14.4 flags: 00
AMD-Vi: DEV_ALIAS_RANGE devid: 01:00.0 flags: 00 devid_to: 00:14.4
AMD-Vi: DEV_RANGE_END devid: 01:1f.7
AMD-Vi: DEV_SELECT devid: 00:14.5 flags: 00
AMD-Vi: DEV_SELECT_RANGE_START devid: 00:16.0 flags: 00
AMD-Vi: DEV_RANGE_END devid: 00:16.2
alloc irq_desc for 55 on node 0
alloc kstat_irqs on node 0
IOAPIC[1]: Set routing entry (7-31 -> 0x79 -> IRQ 55 Mode:1 Active:1)
pci 0000:00:00.2: PCI INT A -> GSI 55 (level, low) -> IRQ 55
alloc irq_desc for 56 on node 0
alloc kstat_irqs on node 0
pci 0000:00:00.2: irq 56 for MSI/MSI-X
AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40
AMD-Vi: Initialized for Passthrough Mode
AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40
initcall pci_iommu_init+0x0/0x21 returned 0 after 569797 usecs
I don't see 06:00.1 device in IOMMU enabling process on which Xen crashes.
lspci output: http://pastebin.com/raw.php?i=3wpKPQT9
next prev parent reply other threads:[~2013-02-13 18:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 3:20 Xen 4.2.1 boot failure with IOMMU enabled Boris Ostrovsky
2013-02-12 6:26 ` povder
2013-02-12 10:06 ` Jan Beulich
2013-02-12 10:55 ` povder
2013-02-12 11:03 ` Jan Beulich
2013-02-12 11:15 ` povder
2013-02-12 11:22 ` Jan Beulich
2013-02-12 11:29 ` Jan Beulich
2013-02-12 15:20 ` Boris Ostrovsky
2013-02-12 15:50 ` povder
2013-02-12 16:04 ` Jan Beulich
2013-02-12 17:44 ` povder
2013-02-12 18:23 ` povder
2013-02-12 18:40 ` povder
2013-02-13 8:05 ` Jan Beulich
2013-02-13 8:28 ` povder
2013-02-13 8:37 ` Jan Beulich
2013-02-13 18:21 ` povder [this message]
2013-02-14 11:03 ` Jan Beulich
2013-02-14 11:29 ` Jan Beulich
2013-02-14 14:55 ` Boris Ostrovsky
2013-02-15 8:21 ` Jan Beulich
2013-02-15 15:21 ` Boris Ostrovsky
-- strict thread matches above, loose matches on Subject: below --
2013-02-13 1:33 Boris Ostrovsky
2013-02-13 8:24 ` Jan Beulich
2013-02-11 17:31 povder
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=CACvNfPwB4+5mJ1qaLjf55QTK+Nno7XDKHoFkJzPYt-xURi3Cdg@mail.gmail.com \
--to=povder@gmail.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.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.