From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Michael Dexter" <editor@callfortesting.org>,
"Roger Pau Monné" <royger@FreeBSD.org>,
jbeulich@suse.com, yang.z.zhang@intel.com, kevin.tian@intel.com,
xen-devel@lists.xenproject.org
Subject: Re: FreeBSD Dom0 IOMMU issues
Date: Wed, 6 May 2015 17:50:53 +0100 [thread overview]
Message-ID: <554A466D.7080104@citrix.com> (raw)
In-Reply-To: <554A4166.9010703@callfortesting.org>
On 06/05/15 17:29, Michael Dexter wrote:
>
> Hello all,
>
> I have been working with Roger Pau Monné to bring FreeBSD Dom0 support
> to a production-ready state but we appear to have hit an IOMMU issue.
>
> Hardware: Lenovo ThinkPad T420 i7-2640M CPU @ 2.80GHz with 16GB RAM.
>
> I am attaching my console logs which first show my loader.conf file
> the DomU .cfg file and then DomU boot with Xorg starting.
>
> In the end I get:
>
> (XEN) ****************************************
> (XEN) Panic on CPU 2:
> (XEN) queue invalidate wait descriptor was not executed
> (XEN) ****************************************
>
> Please let me know if you want me to try any configuration changes.
One of the fault symptoms is the same as reported by Intel recently, but
no patches are currently available. (well - some are, but they are
being argued over).
Are you using a full debug Xen?
~Andrew
next prev parent reply other threads:[~2015-05-06 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 16:29 FreeBSD Dom0 IOMMU issues Michael Dexter
2015-05-06 16:50 ` Andrew Cooper [this message]
2015-05-06 17:10 ` Michael Dexter
2015-05-07 7:14 ` Roger Pau Monné
2015-05-07 1:37 ` Zhang, Yang Z
2015-05-07 6:36 ` Jan Beulich
2015-05-07 7:27 ` Roger Pau Monné
2015-05-07 8:05 ` Michael Dexter
2015-05-07 11:43 ` Jan Beulich
2015-05-07 19:39 ` Michael Dexter
2015-05-08 8:06 ` Jan Beulich
2015-05-08 8:13 ` Roger Pau Monné
2015-05-07 11:40 ` Jan Beulich
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=554A466D.7080104@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=editor@callfortesting.org \
--cc=jbeulich@suse.com \
--cc=kevin.tian@intel.com \
--cc=royger@FreeBSD.org \
--cc=xen-devel@lists.xenproject.org \
--cc=yang.z.zhang@intel.com \
/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.