From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"jbeulich@suse.com" <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: Regression with Xen 4.4 when booting with AMD IOMMU on TA890FXE BIOSTAR
Date: Tue, 24 Dec 2013 17:20:55 -0600 [thread overview]
Message-ID: <52BA16D7.3090008@amd.com> (raw)
In-Reply-To: <20131220024312.GI25322@phenom.dumpdata.com>
On 12/19/2013 8:43 PM, Konrad Rzeszutek Wilk wrote:
>>> (XEN) AMD-Vi: per-device vector map logic is broken. Using per-device-global maps instead until a fix is found.
>>
>> Looks like IOAPIC definition is missing from IVRS. The one that's
>> listed (0000:00:00.1 variety 0x1 handle 0x6) is usually unused IIRC.
>> I'd expect an entry for the second one (that lives on the
>> southbridge), such as
>> AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x1 handle 0
>>
>> And page faults that you are seeing may also be related to this
>> since 0xa0 is 00:14.0.
>>
>> BIOS update might help with this problem (looks like Biostar has a
>> newer BIOS for this board) but I think this should be fixed so maybe
>> you want to keep this BIOS until a fix is developed.
>
> OK.
>>
>> You could try booting with iommu=no-intremap to work around this in
>> the meantime.
>
> That did make it boot. Thanks!
>
I can reproduce the issue also and I am looking into this. I will update
once I found the issue.
Suravee
next prev parent reply other threads:[~2013-12-24 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 18:25 Regression with Xen 4.4 when booting with AMD IOMMU on TA890FXE BIOSTAR Konrad Rzeszutek Wilk
2013-12-19 18:38 ` Andrew Cooper
2013-12-19 18:52 ` Konrad Rzeszutek Wilk
2013-12-19 21:17 ` Boris Ostrovsky
2013-12-20 2:43 ` Konrad Rzeszutek Wilk
2013-12-24 23:20 ` Suravee Suthikulpanit [this message]
2013-12-19 18:52 ` Sander Eikelenboom
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=52BA16D7.3090008@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@darnok.org \
--cc=xen-devel@lists.xenproject.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.