Hi @all, I tested it and I'm not sure that I did it right. The wiki link is somewhat outdated, because it relys on aptitude, which seems not to be installed with Zesty. Nevermind. I now have installed a kernel named
4.10.0-23-generic #25-Ubuntu SMP Fri Jun 9 09:39:09 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux It works flawless. Is this the proposed kernel to test? Any if yes, where do I have to add the needed 'verification-done-zesty' tag? Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: [Impact] Gigabyte AM4 boards users cannot boot Ubuntu successfully. Commit linux-gpio/fixes babdc22b0ccf4ef5a3075ce6e4afc26b7a279faf "pinctrl/amd: Use regular interrupt instead of chained" can fix the issue. [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_irq+0x0/0x40 [ 163.362089] ->handle_irq(): ffffffff87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): ffffffff88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): ffffffff884601c0 [ 163.362091] IRQ_NOPROBE set [ 163.362099] ->handle_irq(): ffffffff87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): ffffffff88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 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/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
