Gigabyte AB350 and Radeon Pro WX2100 won't boot

[LCID Fire]

I am running a Ubuntu 16.04 on a Gigabyte AB350-Gaming 3 board. It runs fine with a Nvidia Quadro GPU. When I switch the Quadro with a Radeon Pro WX2100 the system stops booting (leads to kernel panics).
The failing functions are always acpi and irq related.
The only way to boot is then to add `acpi=off`.
---
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=75cd7f37-25a1-47ef-9e17-93134aa8e1d5
InstallationDate: Installed on 2017-09-01 (114 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
IwConfig:
 docker0 no wireless extensions.

 lo no wireless extensions.

 enp3s0 no wireless extensions.
Lsusb:
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming 3
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
 0 EFI VGA
 1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=ab3af405-8d7b-4e53-8b13-8adf988aa75a ro acpi=off
ProcVersionSignature: Ubuntu 4.13.0-21.24~16.04.1-generic 4.13.13
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-21-generic N/A
 linux-backports-modules-4.13.0-21-generic N/A
 linux-firmware 1.157.14
RfKill:

Tags: xenial
Uname: Linux 4.13.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F10
dmi.board.asset.tag: Default string
dmi.board.name: AB350-Gaming 3-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd12/01/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350-Gaming 3
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[LCID Fire (lcid-fire)]

Tried other acpi flags, but none boot.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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 1740019

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.

[LCID Fire (lcid-fire)]

apport information

[LCID Fire (lcid-fire)]

apport information

[LCID Fire (lcid-fire)]

apport information

[LCID Fire (lcid-fire)]

apport information

[LCID Fire (lcid-fire)]

apport information

[LCID Fire (lcid-fire)]

apport information

[LCID Fire (lcid-fire)]

apport information

[LCID Fire (lcid-fire)]

apport information

[LCID Fire (lcid-fire)]

apport information

[LCID Fire (lcid-fire)]

apport information

[LCID Fire (lcid-fire)]

apport information

[LCID Fire (lcid-fire)]

apport information

[Joseph Salisbury (jsalisbury)]

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.15 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.15-rc6/

[LCID Fire (lcid-fire)]

> Did this issue start happening after an update/upgrade?

No it is a clean install of Ubuntu 16.04.3

> Was there a prior kernel version where you were not having this particular problem?

Every kernel version I tried did not boot with ACPI active.

> Would it be possible for you to test the latest upstream kernel?
Done. Will attach a few photos I shot while booting (and crashing).

[LCID Fire (lcid-fire)]

Output (with postfilters applied) is available at https://imgur.com/a/BDOQR

[Kai-Heng Feng (kaihengfeng)]

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu

[LCID Fire (lcid-fire)]

> Please file an upstream bug

Done: https://bugs.freedesktop.org/show_bug.cgi?id=104472