All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 11 May 2015 14:01:31 +0800	[thread overview]
Message-ID: <555045BB.8080702@intel.com> (raw)
In-Reply-To: <554C47D4.9040604@callfortesting.org>

On 2015/5/8 13:21, Michael Dexter wrote:
> On 5/7/15 7:59 PM, Chen, Tiejun wrote:
>> Are you running IGD passthrough with guest OS?
>
> Only as far as the PVH Xen kernel is passing through all hardware to
> Dom0. Roger can elaborate as needed.
>
>> 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.
>
> My output has dmesg information for this purpose. Most output is from:
>
> CPU: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz (2790.93-MHz K8-class CPU)
> Lenovo ThinkPad T420
>
> The second system is:
>
> CPU: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz (2500.02-MHz K8-class CPU)
> Intel DQ67EP Mini-ITX board
>
> Both systems are recent FreeBSD 11 snapshots, the Dom0:

Please dump something by perform `cat /proc/cpuinfo`.

>
> FreeBSD 11.0-CURRENT #0 r282110: Mon Apr 27 20:49:15 UTC 2015
>
> The DomU:
>
> FreeBSD 11.0-CURRENT #0 r280862: Mon Mar 30 20:15:11 UTC 2015
>
> I have not tried GNU/Linux but could if you like. Is there a preferred
> distribution for use with Xen?
>
>> So maybe you need to upgrade DRM/I915 driver firstly.
>
> Any and all help from Intel at keeping the FreeBSD graphics drivers up
> to date is appreciated. FreeBSD 11 HEAD represents the latest drivers. I
> believe I have tried this under NVidia with similar results. I can run a

Do you mean you can see "... GPU hang" as well?

I just want to narrow down our scope because in any case GPU shouldn't 
constantly hang.

Thanks
Tiejun

> test if you like.
>
> All the best,
>
> Michael Dexter
>
>
>

  reply	other threads:[~2015-05-11  6:01 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
2015-05-08  5:21       ` Michael Dexter
2015-05-11  6:01         ` Chen, Tiejun [this message]
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=555045BB.8080702@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.