From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: i915 crashs in the pvops dom0 Date: Wed, 26 May 2010 12:07:46 -0400 Message-ID: <20100526160746.GA5188@phenom.dumpdata.com> References: <20100513114227.GY17817@reaktio.net> <20100514054859.GO17817@reaktio.net> <20100514055951.GR17817@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Lin, Ben Y" Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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. >