From: "Chen, Tiejun" <tiejun.chen@intel.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 (resent)
Date: Fri, 08 May 2015 10:59:42 +0800 [thread overview]
Message-ID: <554C269E.3000606@intel.com> (raw)
In-Reply-To: <554BB5EB.1000602@callfortesting.org>
On 2015/5/8 2:58, Michael Dexter wrote:
>
> Hello all,
>
Are you running IGD passthrough with guest OS?
> On 5/6/15 7:47 PM, Chen, Tiejun wrote:
>> #1. Disable interrupt message generation
>> #2. Please add 'cpuidle=0 msi=1'
>
> With another try, get the same with the patched kernel:
What is your CPU? BDW? HSW? And what is your FreeBSD Linux version on
Dom0 side? I just think you can directly try the latest upstream Linux
as Dom0, because I see so many messages indicating GPU hang.
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer
elapsed... GPU hung
info: [drm] capturing error event; look for more information in sysctl
hw.dri.0.info.i915_error_state
info: [drm] Enabling RC6 states: RC6 off, RC6p off, RC6pp off
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer
elapsed... GPU hung
info: [drm] Enabling RC6 states: RC6 off, RC6p off, RC6pp off
(XEN) irq.c:380: Dom1 callback via changed to Direct Vector 0x93
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer
elapsed... GPU hung
info: [drm] Enabling RC6 states: RC6 off, RC6p off, RC6pp off
(XEN) irq.c:270: Dom1 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom1 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom1 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom1 PCI link 3 changed 5 -> 0
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer
elapsed... GPU hung
info: [drm] Enabling RC6 states: RC6 off, RC6p off, RC6pp off
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer
elapsed... GPU hung
info: [drm] Enabling RC6 states: RC6 off, RC6p off, RC6pp off
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer
elapsed... GPU hung
So maybe you need to upgrade DRM/I915 driver firstly.
>
> (XEN) ****************************************
> (XEN) Panic on CPU 2:
> (XEN) queue invalidate wait descriptor was not executed
> (XEN) ****************************************
>
> I had 'intel_iommu=off' are per a suggestion I found and removed it.
Yes, you should enable intel iommu if you want to use IOMMU.
Thanks
Tiejun
>
> See "intelpatch2.txt" for this output.
>
> "intel-no-xorg.txt" is the successful lifecycle of the same DomU without
> Xorg running for reference.
>
> Michael Dexter
next prev parent reply other threads:[~2015-05-08 2:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 16:46 FreeBSD Dom0 IOMMU issues (resent) Michael Dexter
2015-05-07 2:47 ` Chen, Tiejun
2015-05-07 7:48 ` Michael Dexter
2015-05-07 18:58 ` Michael Dexter
2015-05-08 2:59 ` Chen, Tiejun [this message]
2015-05-08 5:21 ` Michael Dexter
2015-05-11 6:01 ` Chen, Tiejun
2015-05-08 7:34 ` Michael Dexter
2015-05-08 7:54 ` Roger Pau Monné
2015-05-08 7:53 ` 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=554C269E.3000606@intel.com \
--to=tiejun.chen@intel.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.