[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] iommu hangs boot


  • To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Alexia Benington <alexbenington@xxxxxxxxx>
  • Date: Wed, 18 Feb 2009 12:00:34 -0500
  • Delivery-date: Wed, 18 Feb 2009 09:02:29 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Aesa5wmSOg/fEXPofQf1djbilTQcNfGISciYlgF/ro+OsJwbKCaTlVWoKlWpkC72BQ +M/NcWd9K3UJdLzzQor+61cea6OAQNk4XfD1XHPQj8Uv01J8XWN0VUc0zceMLmCjjhyF rIE/iR7szNimC5zvyRP73I+EYOt74jHADF8XQ=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi all,

There was a similar thread I started earlier, however as the title
didn't correctly reflect the symptoms. I created this after more
experiments.

Here's some background. I was able to get graphics passthrough to work
on Fedora 10 with Intel DQ45CB and an ATI gfx card inserted. I passed
through the integrated Intel gfx instead of ATI. BIOS was set to use
Intel gfx.

However, when I took out the ATI gfx, the iommu option seems to cause
the boot up to hang, as shown in "090218.1.log". Without iommu=1,
bootup seems normal. But of course passthrough won't work.
Interestingly, when I closed minicom and start it again, I have the
output as shown in "090218.2.log". It doesn't matter whether I'm
hiding any PCI devices from Dom0. Setting iommu=1 is sufficient to
cause the hang. Why is so?

Does anyone have any idea why the presence of ATI gfx seems to make
things work, and removing it causes the hanging?

Thanks and have a good day.

-Alex

Attachment: 090218.1.log
Description: Text Data

Attachment: 090218.2.log
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.