From: Clemens Ladisch <clemens-P6GI/4k7KOmELgA04lAiVw@public.gmane.org>
To: "Joerg Roedel" <jroedel-l3A5Bk7waGM@public.gmane.org>,
martin <haiden.tracking-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
bellamorte42-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
"Tomasz Goliński"
<tomaszg-FRiIMV821htubak7+UBa2Q@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 14:26:14 +0200 [thread overview]
Message-ID: <5703AEE6.4010304@ladisch.de> (raw)
In-Reply-To: <20160405101530.GA4203-l3A5Bk7waGM@public.gmane.org>
Joerg Roedel wrote:
> On Tue, Apr 05, 2016 at 12:02:07PM +0200, Clemens Ladisch wrote:
>> Joerg Roedel wrote:
>>> I have seen that before, can you please boot with 'amd_iommu_dump' on
>>> the kernel command line and send me dmesg after boot?
>>
>> Full dmesg: <https://bugzilla.kernel.org/attachment.cgi?id=211771>:
>> ...
>> [ 0.179504] pci 0000:04:00.0: [10b5:8112] type 01 class 0x060400
>> [ 0.179681] pci 0000:04:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
>> [ 0.179966] pci 0000:00:15.0: PCI bridge to [bus 04-05]
>> [ 0.180128] pci 0000:00:15.0: bridge window [io 0xc000-0xcfff]
>> [ 0.180216] pci 0000:05:04.0: [13f6:8788] type 00 class 0x040100
>> [ 0.180245] pci 0000:05:04.0: reg 0x10: [io 0xc000-0xc0ff]
>> [ 0.180390] pci 0000:05:04.0: supports D1 D2
>> [ 0.180478] pci 0000:04:00.0: PCI bridge to [bus 05]
>> [ 0.180641] pci 0000:04:00.0: bridge window [io 0xc000-0xcfff]
>> ...
>> [ 0.459076] AMD-Vi: device: 00:00.2 cap: 0040 seg: 0 flags: fe info 1300
>> [ 0.459238] AMD-Vi: mmio-addr: 00000000feb80000
>> [ 0.459430] AMD-Vi: DEV_SELECT_RANGE_START devid: 00:01.0 flags: 00
>> [ 0.459592] AMD-Vi: DEV_RANGE_END devid: ff:1f.6
>> [ 0.460268] AMD-Vi: DEV_ALIAS_RANGE devid: 03:00.0 flags: 00 devid_to: 00:14.4
>> [ 0.460555] AMD-Vi: DEV_RANGE_END devid: 03:1f.7
>> [ 0.460717] AMD-Vi: DEV_SPECIAL(HPET[0]) devid: 00:14.0
>> [ 0.460876] AMD-Vi: DEV_SPECIAL(IOAPIC[5]) devid: 00:14.0
>> [ 0.542806] iommu: Adding device 0000:00:02.0 to group 0
>> ...
>> [ 0.547889] iommu: Adding device 0000:00:15.0 to group 9
>> ...
>> [ 0.549907] iommu: Adding device 0000:04:00.0 to group 9
>> [ 0.550071] iommu: Adding device 0000:05:04.0 to group 9
>> [ 0.550229] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
>> [ 0.550387] AMD-Vi: Extended features: PreF PPR GT IA
>> [ 0.550804] AMD-Vi: Lazy IO/TLB flushing enabled
>> ...
>> [ 124.474883] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x0000000000100000 flags=0x0050]
>
> Hmm, with this IVRS table it should've never worked.
It did work before 4.4. Is it possible that the IOMMU, or some feature,
got enabled by default?
Martin/Tomasz, could we get the amd_iommu_dump dmesg output for an
earlier kernel?
> Did you do a BIOS update in-between?
None of the three reporters reported this.
Switching between 4.4 and 4.3 makes the problem (dis)appear.
The problem must be connected with the kernel code.
> Or maybe some change to the sound driver makes it misbehave and use
> a wrong pci request-id?
The driver did not change at all, and the sound device is a plain PCI
chip. The various sound card models use completely different PCIe/PCI
bridges (PEX8112 and ASM1083).
Regards,
Clemens
next prev parent reply other threads:[~2016-04-05 12:26 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 [this message]
[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
[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=5703AEE6.4010304@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 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.