Tags Tags

Bug#684661: Xen BUG at pci_amd_iommu.c:33

August 17th, 2012 - 08:00 am ET by Ian Campbell | Report spam
Help Create a new topic
Hi Wei,

A Debian user has hit this message and reported it in
http://bugs.debian.org/cgi-bin/bugr...i?bugh4661

I think it is the BUG_ON in:
struct amd_iommu *find_iommu_for_device(int bdf)
{
BUG_ON ( bdf >= ivrs_bdf_entries );
return ivrs_mappings[bdf].iommu;
}

It looks like ivrs_bdf_entries comes from ACPI. Unfortunately the bug
report is a bit vague about things like stack traces etc so it's hard to
say where BDF came from.

Any ideas? I'll also follow up to the submitter to try and get some more
details.

Ian.


To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 1 replyReplies Make a reply

Similar topics

Replies

#1 Wei Wang
August 17th, 2012 - 08:30 am ET | Report spam
On 08/17/2012 01:46 PM, Ian Campbell wrote:
Hi Wei,

A Debian user has hit this message and reported it in
http://bugs.debian.org/cgi-bin/bugr...i?bugh4661

I think it is the BUG_ON in:
struct amd_iommu *find_iommu_for_device(int bdf)
{
BUG_ON ( bdf>= ivrs_bdf_entries );
return ivrs_mappings[bdf].iommu;
}

It looks like ivrs_bdf_entries comes from ACPI. Unfortunately the bug
report is a bit vague about things like stack traces etc so it's hard to
say where BDF came from.

Any ideas? I'll also follow up to the submitter to try and get some more
details.



It difficult to identify the issue from the description and I think a
full serial boot log would be great. Also using iommu=debug as boot
option is very helpful to get more information.

Thanks,
Wei

Ian.


_______________________________________________
Xen-devel mailing list

http://lists.xen.org/xen-devel





To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
email Follow the discussion Replies Reply to this message
Help Create a new topicReplies Make a reply
Search Make your own search