Hi Joerg,

Ok it boots ok now, but plugging in a USB device in the 2.0 controller (0a.01.*) results in a flood of error messages about the usb controller not functioning.
When running same kernel with amd_iommu=off results in ...the device at least registering properly as usb device (altough trying to use it now resulted in an entirely new oops probably in the driver of the videograbber.)

--
Sander

Tuesday, August 10, 2010, 11:25:51 PM, you wrote:

quoted text
> On Tue, Aug 10, 2010 at 10:57:26PM +0200, Sander Eikelenboom wrote:
>> Hmmm the fun part seems to be .. that the usb devices on that usb2
>> controller seemed to work fine on Xen.

quoted text
> Hmm, thats weird. In this case these devices probably do not alias at
> all. But lets wait for the results when you test my patch.


quoted text
>>            +-0a.0-[0000:09-0a]----00.0-[0000:0a]--+-01.0
>>            |                                      +-01.1
>>            |                                      \-01.2

quoted text
> Yeah, device 09:00.0 is a PCIe-to-PCI bridge and the addtional USB
> controlers are behind that bridge as legacy PCI devices. Thats why the
> BIOS sets up the alias-entry. It should set up 09:00.0 instead of
> 0a:00.0 to make things work correctly.

quoted text
>         Joerg




-- 
Best regards,
 Sander                            mailto:linux@eikelenboom.it

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/