From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>,
Jan Beulich <jbeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen-unstable-staging: Xen BUG at iommu_map.c:455
Date: Wed, 01 Apr 2015 00:38:34 +0100 [thread overview]
Message-ID: <551B2FFA.6080001@citrix.com> (raw)
In-Reply-To: <1864736142.20150331231153@eikelenboom.it>
On 31/03/2015 22:11, Sander Eikelenboom wrote:
> Hi all,
>
> I just tested xen-unstable staging (changeset: git:0522407-dirty)
>
> with revert of commit 1aeb1156fa43fe2cd2b5003995b20466cd19a622
> (due to an already reported but not yet resolved issue)
>
> and build with qemu xen from git://xenbits.xen.org/staging/qemu-upstream-unstable.git
> (to include the pci command register patch from Jan)
>
>
> and now came across this new splat when starting an HVM with PCI passtrhough:
Wow - you are getting all the fun bugs at the moment!
Nothing has changed in the AMD IOMMU driver for a while, but the
BUG_ON() is particularly unhelpful at identifying what went wrong.
As a first pass triage, can you rerun with
diff --git a/xen/drivers/passthrough/amd/iommu_map.c
b/xen/drivers/passthrough/amd/iommu_map.c
index 495ff5c..f15c324 100644
--- a/xen/drivers/passthrough/amd/iommu_map.c
+++ b/xen/drivers/passthrough/amd/iommu_map.c
@@ -451,8 +451,9 @@ static int iommu_pde_from_gfn(struct domain *d,
unsigned long pfn,
table = hd->arch.root_table;
level = hd->arch.paging_mode;
- BUG_ON( table == NULL || level < IOMMU_PAGING_MODE_LEVEL_1 ||
- level > IOMMU_PAGING_MODE_LEVEL_6 );
+ BUG_ON(table == NULL);
+ BUG_ON(level < IOMMU_PAGING_MODE_LEVEL_1);
+ BUG_ON(level > IOMMU_PAGING_MODE_LEVEL_6);
next_table_mfn = page_to_mfn(table);
which will help identify which of the conditions is failing.
Can you please also provide the full serial log, including iommu=debug?
~Andrew
next prev parent reply other threads:[~2015-03-31 23:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 21:11 Xen-unstable-staging: Xen BUG at iommu_map.c:455 Sander Eikelenboom
2015-03-31 23:38 ` Andrew Cooper [this message]
2015-04-01 0:17 ` Sander Eikelenboom
2015-04-01 19:22 ` Sander Eikelenboom
2015-04-10 10:24 ` Sander Eikelenboom
2015-04-10 18:55 ` Andrew Cooper
2015-04-10 19:27 ` Sander Eikelenboom
2015-04-11 14:11 ` Sander Eikelenboom
2015-04-11 14:21 ` Andrew Cooper
2015-04-11 16:21 ` Sander Eikelenboom
2015-04-11 16:32 ` Andrew Cooper
2015-04-11 16:38 ` Andrew Cooper
2015-04-11 17:25 ` Sander Eikelenboom
2015-04-11 17:35 ` Andrew Cooper
2015-04-11 17:42 ` Sander Eikelenboom
2015-04-11 18:25 ` Andrew Cooper
2015-04-11 19:33 ` Sander Eikelenboom
2015-04-11 20:22 ` Andrew Cooper
2015-04-11 21:05 ` Sander Eikelenboom
2015-04-11 21:35 ` Andrew Cooper
2015-04-12 15:15 ` Sander Eikelenboom
2015-04-12 16:10 ` Sander Eikelenboom
2015-04-15 19:06 ` Konrad Rzeszutek Wilk
2015-04-16 9:28 ` Tim Deegan
2015-04-20 16:11 ` Jan Beulich
2015-04-20 16:14 ` Sander Eikelenboom
2015-04-20 18:50 ` Sander Eikelenboom
2015-04-21 8:11 ` Jan Beulich
2015-04-21 8:24 ` Sander Eikelenboom
2015-04-21 8:42 ` Jan Beulich
2015-04-21 8:55 ` Sander Eikelenboom
2015-05-05 15:10 ` Jan Beulich
2015-05-05 15:17 ` Tim Deegan
2015-05-05 15:31 ` Jan Beulich
2015-05-07 10:32 ` Tim Deegan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=551B2FFA.6080001@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.