From: Clemens Ladisch <clemens-P6GI/4k7KOmELgA04lAiVw@public.gmane.org>
To: Tomasz Golinski <tomaszg-FRiIMV821htubak7+UBa2Q@public.gmane.org>,
Joerg Roedel <jroedel-l3A5Bk7waGM@public.gmane.org>,
martin <haiden.tracking-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
bellamorte42-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: AMD-Vi regression with PCIe/PCI bridges in 4.4
Date: Tue, 5 Apr 2016 15:15:10 +0200 [thread overview]
Message-ID: <5703BA5E.3060005@ladisch.de> (raw)
In-Reply-To: <5703B1F3.6000505-FRiIMV821htubak7+UBa2Q@public.gmane.org>
Tomasz Golinski wrote:
> On 05.04.2016 14:26, Clemens Ladisch wrote:
>> Martin/Tomasz, could we get the amd_iommu_dump dmesg output for an
>> earlier kernel?
>
> It's for 4.1.15.
> ...
> [ 0.486934] AMD-Vi: DEV_SPECIAL(IOAPIC[5]) devid: 00:14.0
> [ 0.569054] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
All those "iommu: Adding device x to group y" messages from 4.4 are
missing.
Apparently, something caused the IOMMU to be enabled. Tomasz, could you
please compare the configurations (/lib/modules/(version)/build/.config)
with "diff -u" or something like that?
Regards,
Clemens
next prev parent reply other threads:[~2016-04-05 13:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 6:59 AMD-Vi regression with PCIe/PCI bridges in 4.4 Clemens Ladisch
[not found] ` <5700BF69.2080102-P6GI/4k7KOmELgA04lAiVw@public.gmane.org>
2016-04-04 10:51 ` Joerg Roedel
2016-04-05 10:02 ` Clemens Ladisch
[not found] ` <57038D1F.7040205-P6GI/4k7KOmELgA04lAiVw@public.gmane.org>
2016-04-05 10:15 ` Joerg Roedel
[not found] ` <20160405101530.GA4203-l3A5Bk7waGM@public.gmane.org>
2016-04-05 12:26 ` Clemens Ladisch
[not found] ` <5703AEE6.4010304-P6GI/4k7KOmELgA04lAiVw@public.gmane.org>
2016-04-05 12:39 ` Tomasz Golinski
[not found] ` <5703B1F3.6000505-FRiIMV821htubak7+UBa2Q@public.gmane.org>
2016-04-05 12:49 ` Joerg Roedel
2016-04-05 13:15 ` Clemens Ladisch [this message]
[not found] ` <5703BA5E.3060005-P6GI/4k7KOmELgA04lAiVw@public.gmane.org>
2016-04-05 13:19 ` Joerg Roedel
[not found] ` <20160405131928.GJ17838-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-04-05 14:06 ` Tomasz Golinski
2016-04-06 7:06 ` Martin Haiden
[not found] ` <1459926391.2346.6.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-06 15:47 ` Joerg Roedel
[not found] ` <20160406154729.GD4203-l3A5Bk7waGM@public.gmane.org>
2016-04-06 15:52 ` Tomasz Golinski
[not found] ` <570530D9.6010109-FRiIMV821htubak7+UBa2Q@public.gmane.org>
2016-04-08 13:23 ` Joerg Roedel
[not found] ` <20160408132355.GE4203-l3A5Bk7waGM@public.gmane.org>
2016-04-08 15:39 ` Tomasz Golinski
[not found] ` <5707D0BD.3070905-FRiIMV821htubak7+UBa2Q@public.gmane.org>
2016-04-08 19:01 ` Joerg Roedel
[not found] ` <20160408190111.GF4203-l3A5Bk7waGM@public.gmane.org>
2016-04-08 20:17 ` Tomasz Golinski
[not found] ` <570811BF.8040504-FRiIMV821htubak7+UBa2Q@public.gmane.org>
2016-04-11 14:08 ` Joerg Roedel
2016-04-06 19:15 ` Martin Haiden
2016-04-06 19:55 ` Clemens Ladisch
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=5703BA5E.3060005@ladisch.de \
--to=clemens-p6gi/4k7komelga04laivw@public.gmane.org \
--cc=bellamorte42-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=haiden.tracking-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jroedel-l3A5Bk7waGM@public.gmane.org \
--cc=tomaszg-FRiIMV821htubak7+UBa2Q@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox