Bad news. Using 4.11-rc5 as a base and reverting the commit I previously mentioned (0be275e3a5607b23f5132121bca22a10ee23aa99) does yield a mostly functional kernel.
I say "mostly" because there is still a lone "unexpected IRQ trap" in dmesg when the pinctrl driver loads, though the system boots successfully... most of the time. Also, configuring pinctrl-amd as a module instead of built-in and loading it later on will still result in the same crash scenarios as before. So the code that the commit touches may be vaguely related to the problem, but it's certainly not the root cause. Still kinda seems like a BIOS bug to me, particularly since other motherboard vendors are not affected. Let's hope someone at Gigabyte does something about this soon. I just tested the F3e beta BIOS, made no difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
