Comment 70 for bug 1747463

Revision history for this message
calcatinge (calcatinge) wrote :

I have the same issue, but with a Ryzen 7 1700 with the following setups:

Setup 1:
Motherboard: Gigabyte B450 Aorus M (Latest BIOS installed)
RAM: 32 GB DDR4 Crucial 3000 Mhz
GPU1: Sapphire Radeon RX 580 Nitro+ Special Edition 8GB GDDR5
GPU2: Asus Mining Radeon RX 470 4G GDDR5
SSD: 240 GB WD Green

Setup 2:
Motherboard: ASRock AB350M Pro4 (Latest BIOS installed)
RAM: 32 GB DDR4 Crucial 3000 Mhz
GPU1: Sapphire Radeon RX 580 Nitro+ Special Edition 8GB GDDR5
GPU2: Sapphire Radeon RX 550 2G GDDR5
SSD: 240 GB WD Green

The issue first started after installing the second GPU on each of the systems. I can't even boot the system, as the errors appear right after BIOS initialization.

The errors are like:

[exerpt]
AMD-Vi: Completion-Wait loop timed out
AMD-Vi: Completion-Wait loop timed out
AMD-Vi: Completion-Wait loop timed out

...

AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x0000000174bb7560]

Entering emergecy mode. Exit the shell to continue.
Type "journalctl" to view system logs.

....

AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x0000000174bb75d0]
AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x0000000174bb7700]
AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x0000000174bb7630]
AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x0000000174bb7660]
AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x0000000174bb7690]
AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x0000000174bb76c0]
AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x0000000174bb76f0]

...

AMD-Vi: Completion-Wait loop timed out
AMD-Vi: Event logged [IO_PAGE_FAULT device=23:00.3 domain=0x000 address=0x00000000fffd3990 flags=0x0070]

...

Buffer I/O error on dev dm-0, logical block 104857472, async page read
Buffer I/O error on dev dm-0, logical block 104857473, async page read
Buffer I/O error on dev dm-0, logical block 104857474, async page read
Buffer I/O error on dev dm-0, logical block 104857475, async page read
Buffer I/O error on dev dm-0, logical block 104857476, async page read
Buffer I/O error on dev dm-0, logical block 104857477, async page read

.....

After some research I discovered that it is a IOMMU issue.
I turned IOMMU off on both motherboards, and I managed to boot the system.
I am an architect and I use blender for GPU rendering (this is the idea of having two), but the AMDGPU-Pro driver from the AMD's website (the only one that Blender uses for GPU rendering, as it can't use the open one) affects the way Gnome works on Xorg. It affects in the way that it doesn't start at all, it keeps restarting to the GDM screen...

Any ideas?

Thanks.