From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Wang Subject: Re: Xen BUG at pci_amd_iommu.c:33 Date: Fri, 17 Aug 2012 14:10:22 +0200 Message-ID: <502E34AE.9030105@amd.com> References: <1345203982.10161.11.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1345203982.10161.11.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: 684661@bugs.debian.org, xen-devel List-Id: xen-devel@lists.xenproject.org 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/bugreport.cgi?bug=684661 > > 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 > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >