All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Lin, Ben Y" <ben.y.lin@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: i915 crashs in the pvops dom0
Date: Wed, 26 May 2010 12:07:46 -0400	[thread overview]
Message-ID: <20100526160746.GA5188@phenom.dumpdata.com> (raw)
In-Reply-To: <CE59C043D0EC3349B2BF41C0EC72229B1E854839@shsmsx501.ccr.corp.intel.com>

On Fri, May 14, 2010 at 02:03:25PM +0800, Lin, Ben Y wrote:
> I didn't try this branch, but I tried the xen/next, it still has such issue.

Not all of the bugs are fixed. But one thing I want you to try is to
have CONFIG_DMAR enabled in your .config and see if that makes a
difference.

The reason behind that is the the intel-agp.c code has this:

  18 /*
  19  * If we have Intel graphics, we're not going to have anything
other than
  20  * an Intel IOMMU. So make the correct use of the PCI DMA API
contingent
  21  * on the Intel IOMMU support (CONFIG_DMAR).
  22  * Only newer chipsets need to bother with this, of course.
  23  */
  24 #ifdef CONFIG_DMAR
  25 #define USE_PCI_DMA_API 1
  26 #endif
  27 

And we end up setting CONFIG_DMAR the newer DMA API is used. See if that works.

Eiter way, can you give me these details:
 - lspci -vvv
 - Xorg.log
 - the full console log? 

> 
> Could you tell me which configuration should be workable? For example, xen version + branch for pvops dom0 + graphics driver release version.
> 

      parent reply	other threads:[~2010-05-26 16:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13  6:21 i915 crashs in the pvops dom0 Lin, Ben Y
2010-05-13 11:42 ` Pasi Kärkkäinen
2010-05-14  2:27   ` Lin, Ben Y
2010-05-14  5:48     ` Pasi Kärkkäinen
2010-05-14  5:55       ` Lin, Ben Y
2010-05-14  5:59         ` Pasi Kärkkäinen
2010-05-14  6:03           ` Lin, Ben Y
2010-05-14  6:39             ` Pasi Kärkkäinen
2010-05-26 16:07             ` Konrad Rzeszutek Wilk [this message]

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=20100526160746.GA5188@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=ben.y.lin@intel.com \
    --cc=xen-devel@lists.xensource.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.