AMD-Vi write error

Bug #1804589 reported by Yoshiba
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

AMD-Vi write error.
[ 0.777408] AMD-Vi: Unable to write to IOMMU perf counter.
[ 0.777529] pci 0000:00:00.2: can't derive routing for PCI INT A
[ 0.777530] pci 0000:00:00.2: PCI INT A: not connected
[ 0.778000] iommu: Adding device 0000:00:01.0 to group 0
[ 0.778231] iommu: Adding device 0000:00:01.2 to group 1
[ 0.778463] iommu: Adding device 0000:00:01.6 to group 2
[ 0.778690] iommu: Adding device 0000:00:08.0 to group 3
[ 0.778914] iommu: Adding device 0000:00:08.1 to group 4
[ 0.778940] iommu: Adding device 0000:00:08.2 to group 3
[ 0.779154] iommu: Adding device 0000:00:14.0 to group 5
[ 0.779176] iommu: Adding device 0000:00:14.3 to group 5
[ 0.779444] iommu: Adding device 0000:00:18.0 to group 6
[ 0.779474] iommu: Adding device 0000:00:18.1 to group 6
[ 0.779495] iommu: Adding device 0000:00:18.2 to group 6
[ 0.779516] iommu: Adding device 0000:00:18.3 to group 6
[ 0.779544] iommu: Adding device 0000:00:18.4 to group 6
[ 0.779566] iommu: Adding device 0000:00:18.5 to group 6
[ 0.779586] iommu: Adding device 0000:00:18.6 to group 6
[ 0.779606] iommu: Adding device 0000:00:18.7 to group 6
[ 0.779835] iommu: Adding device 0000:15:00.0 to group 7
[ 0.779869] iommu: Adding device 0000:15:00.1 to group 7
[ 0.779903] iommu: Adding device 0000:15:00.2 to group 7
[ 0.779933] iommu: Adding device 0000:16:04.0 to group 7
[ 0.779956] iommu: Adding device 0000:16:05.0 to group 7
[ 0.779977] iommu: Adding device 0000:16:06.0 to group 7
[ 0.779999] iommu: Adding device 0000:16:07.0 to group 7
[ 0.780031] iommu: Adding device 0000:1b:00.0 to group 7
[ 0.780058] iommu: Adding device 0000:1c:00.0 to group 7
[ 0.780296] iommu: Adding device 0000:2e:00.0 to group 8
[ 0.780592] iommu: Adding device 0000:38:00.0 to group 9
[ 0.780672] iommu: Using direct mapping for device 0000:38:00.0
[ 0.780767] iommu: Adding device 0000:38:00.1 to group 10
[ 0.780807] iommu: Adding device 0000:38:00.2 to group 10
[ 0.780847] iommu: Adding device 0000:38:00.3 to group 10
[ 0.780887] iommu: Adding device 0000:38:00.4 to group 10
[ 0.780934] iommu: Adding device 0000:38:00.6 to group 10
[ 0.780965] iommu: Adding device 0000:39:00.0 to group 3
[ 0.781307] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
[ 0.781308] AMD-Vi: Extended features (0x4f77ef22294ada):
[ 0.781308] PPR NX GT IA GA PC GA_vAPIC
[ 0.781311] AMD-Vi: Interrupt remapping enabled
[ 0.781311] AMD-Vi: virtual APIC enabled
[ 0.781534] AMD-Vi: Lazy IO/TLB flushing enabled

Revision history for this message
Yoshiba (yoshibatora) wrote :

dmesg and lpci info attched in below post.
https://bugs.launchpad.net/ubuntu/+bug/1804577

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1804589/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Yoshiba (yoshibatora)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1804589

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Yoshiba (yoshibatora) wrote :
tags: added: cosmic
removed: bot-comment
Revision history for this message
Yoshiba (yoshibatora) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc4

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Yoshiba (yoshibatora) wrote :

dmesg info with kernel 4.20.0-042000rc4-generic

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Yoshiba (yoshibatora) wrote :
Download full text (7.4 KiB)

The issue remains with mainline kernel v4.20-rc4, here is the warnings during the installation. kgd2kfd_probe failed error seems gone with the new kernel.
Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
    nor crypto modules. If that's on purpose, you may want to uninstall the
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
    integration and avoid this warning.
W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/am...

Read more...

Revision history for this message
Yoshiba (yoshibatora) wrote :
Revision history for this message
Yoshiba (yoshibatora) wrote :
Brad Figg (brad-figg)
tags: added: cscc
Revision history for this message
Paul Menzel (paulmenzel) wrote :

I am also seeing this with current Linux (5.7-rc7) on an MSI B350M MORTAR and a Dell OptiPlex 5055. Both are AMD Ryzen systems, so this seems to affect all of those.

The IOMMU subsystem maintainer responded to report this issue to the mainboard vendor, so they fix the firmware [1].

Everybody experiencing this, please contact the mainboard vendor to fix this. I already did, and the more contact them, the higher it will rise in their ticketing system.

[1]: https://lists.linuxfoundation.org/pipermail/iommu/2018-July/028925.html

Revision history for this message
Paul Menzel (paulmenzel) wrote :

It’d be great if Canonical also used their Dell and AMD contacts to get this fixed.

Revision history for this message
Paul Menzel (paulmenzel) wrote :

Just a note, on the Dell OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.20 05/31/2019 (AGESA SummitPI-AM4 1.0.0.7a) I am only seeing the interrupt warning. Performance counters are supported there.

    [ 0.870894] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
    [ 0.871377] pci 0000:00:00.2: can't derive routing for PCI INT A
    [ 0.871732] pci 0000:00:00.2: PCI INT A: not connected

Revision history for this message
cipriani (cipriani) wrote :

I've the same bug.... MOB MSI Tomahawk D450 Max and AMD Ryzen 3400G . 12/19/2020

[ 0.276768] pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
[ 0.276860] pci 0000:00:00.2: can't derive routing for PCI INT A
[ 0.276861] pci 0000:00:00.2: PCI INT A: not connected
[ 0.276889] pci 0000:00:01.0: Adding to iommu group 0
[ 0.276900] pci 0000:00:01.2: Adding to iommu group 1
[ 0.276921] pci 0000:00:08.0: Adding to iommu group 2
[ 0.276930] pci 0000:00:08.1: Adding to iommu group 3
[ 0.276939] pci 0000:00:08.2: Adding to iommu group 4
[ 0.276952] pci 0000:00:14.0: Adding to iommu group 5
[ 0.276958] pci 0000:00:14.3: Adding to iommu group 5
[ 0.276984] pci 0000:00:18.0: Adding to iommu group 6
[ 0.276989] pci 0000:00:18.1: Adding to iommu group 6
[ 0.276995] pci 0000:00:18.2: Adding to iommu group 6
[ 0.277001] pci 0000:00:18.3: Adding to iommu group 6
[ 0.277007] pci 0000:00:18.4: Adding to iommu group 6
[ 0.277013] pci 0000:00:18.5: Adding to iommu group 6
[ 0.277019] pci 0000:00:18.6: Adding to iommu group 6
[ 0.277025] pci 0000:00:18.7: Adding to iommu group 6
[ 0.277047] pci 0000:12:00.0: Adding to iommu group 7
[ 0.277061] pci 0000:12:00.1: Adding to iommu group 7
[ 0.277075] pci 0000:12:00.2: Adding to iommu group 7
[ 0.277079] pci 0000:20:00.0: Adding to iommu group 7
[ 0.277085] pci 0000:20:01.0: Adding to iommu group 7
[ 0.277089] pci 0000:20:04.0: Adding to iommu group 7
[ 0.277093] pci 0000:20:06.0: Adding to iommu group 7
[ 0.277096] pci 0000:20:07.0: Adding to iommu group 7
[ 0.277101] pci 0000:22:00.0: Adding to iommu group 7
[ 0.277107] pci 0000:27:00.0: Adding to iommu group 7
[ 0.277135] pci 0000:29:00.0: Adding to iommu group 8
[ 0.277166] pci 0000:29:00.1: Adding to iommu group 9
[ 0.277182] pci 0000:29:00.2: Adding to iommu group 9
[ 0.277198] pci 0000:29:00.3: Adding to iommu group 9
[ 0.277215] pci 0000:29:00.4: Adding to iommu group 9
[ 0.277232] pci 0000:29:00.6: Adding to iommu group 9
[ 0.277242] pci 0000:2a:00.0: Adding to iommu group 10
[ 0.279494] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
[ 0.279495] pci 0000:00:00.2: AMD-Vi: Extended features (0x4f77ef22294ada):

Revision history for this message
cipriani (cipriani) wrote :

Forgot the kernel version,sorry..

[ 0.000000] Linux version 5.8.0-34-generic (buildd@lcy01-amd64-015) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #37~20.04.2-Ubuntu SMP Thu Dec 17 14:53:00 UTC 2020 (Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=c606d48b-7691-4134-bfbe-6930d3b69320 ro quiet splash vt.handoff=7

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.