System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
Medium
|
|||
linux (Ubuntu) |
Fix Released
|
Medium
|
Kai-Heng Feng | ||
Zesty |
Fix Released
|
Undecided
|
Kai-Heng Feng | ||
Artful |
Fix Released
|
Medium
|
Kai-Heng Feng |
Bug Description
[Impact]
Gigabyte AM4 boards users cannot boot Ubuntu successfully.
Commit linux-gpio/fixes babdc22b0ccf4ef
[Test Case]
All Gigabyte AM4 boards can reproduce the issue.
With the patch, the issue is resolved, per comment #170.
[Regression Potential]
Regression Potential is low. It limits to rather new AMD platform which has pinctrl-amd.
As the commit log says, use chained interrupt is not a good idea. Use regular interrupt is the correct way.
I also test the patch on an AMD laptop, where its touchpad depends on pinctrl-amd. No regression found.
Original bug report:
I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard,
and it has a load of problems, starting with not being able to boot normally.
During normal boot, on 16.10 as well as 17.04 beta:
system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07"
messages displayed.
Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings
1. add "acpi=off" to boot params
That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode.
2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option.
That gets me even further - system sees all cores now. Still only recovery mode though,
but its enough to get info for this bug report.
Some observed problems:
1. dmesg reports *a lot* of messages like this all the time:
[ 163.362068] ->handle_irq(): ffffffff87a7e090,
[ 163.362081] bad_chained_
[ 163.362089] ->handle_irq(): ffffffff87a7e090,
[ 163.362090] amd_gpio_
[ 163.362090] ->irq_data.chip(): ffffffff88587e20,
[ 163.362090] ioapic_
[ 163.362090] ->action(): ffffffff884601c0
[ 163.362091] IRQ_NOPROBE set
[ 163.362099] ->handle_irq(): ffffffff87a7e090,
[ 163.362099] amd_gpio_
[ 163.362100] ->irq_data.chip(): ffffffff88587e20,
[ 163.362100] ioapic_
[ 163.362101] ->action(): ffffffff884601c0
I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those.
2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs?
3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/
Phoronix tested ryzen using different motherboard, and it worked better (though not well),
so I suspect it is an issue with motherboard.
---
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2015-08-06 (581 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
Package: linux (not installed)
ProcEnviron:
LANGUAGE=en_US:en
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Tags: zesty
Uname: Linux 4.11.0-rc1-custom x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
UserGroups:
_MarkForUpload: True
CVE References
summary: |
- System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3 + System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) |
tags: | added: xenial yakkety |
tags: | added: regression-release |
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
status: | Incomplete → Confirmed |
tags: | added: kernel-da-key |
tags: | added: bitesize kernel-oops |
description: | updated |
Changed in linux (Ubuntu Artful): | |
assignee: | nobody → Kai-Heng Feng (kaihengfeng) |
Changed in linux (Ubuntu Zesty): | |
assignee: | nobody → Kai-Heng Feng (kaihengfeng) |
Changed in linux (Ubuntu Artful): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu Zesty): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Zesty): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu Zesty): | |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu Zesty): | |
status: | Fix Released → Fix Committed |
tags: | added: verification-needed-zesty |
tags: |
added: verification-done-zesty removed: verification-needed-zesty |
Changed in linux: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Changed in linux: | |
status: | Confirmed → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1671360
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.