[Bug 1671360] [NEW] System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
Public bug reported: 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(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 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. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "kernel config, lspci, dmesg messages and other info I could get" https://bugs.launchpad.net/bugs/1671360/+attachment/4834330/+files/report.tgz -- 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
[Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
apport information ** Tags added: apport-collected zesty ** Description changed: 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(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 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 ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1671360/+attachment/4834867/+files/JournalErrors.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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
[Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
I've added appport info -- 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
[Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
The issue had nothing to do with upgrades, its the same problem on 16.10 as well as on 17.04. I've tested it on my system and on live ubuntu on usb. I've tried to use mainline kernel and the problem is still there. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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
[Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
I've found a workaround (requires compiling own kernel, tested on 4.11 and r4.11rc1): When configuring kernel (I used make menuconfig) disable following things: Everything under device drivers/gpio support, especially: memory mapped files/amd promontory support (GPIO_AMDPT) and pci gpio expanders / amd 8111 gpio driver (GPIO_AMD8111) but I've turned of everything to make sure nothing is using gpio. device drivers / pin controllers / amd gpio pin control (PINCTRL_AMD) Perhaps only one of them could be really necessary, but I didn't tested that. System boots normally, no problems with journald and no weird messages from dmesg. -- 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
[Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
> Maciej, do you have any suggestions if there is no previous OS installed? You may try to boot with those options: acpi=off quiet loglevel=3 (just acpi=off might be enough). That should get you through installation. -- 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
[Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
Huang YangWen: can you attach result of those command: ls -l /sys/bus/acpi/devices/ sudo lspci -vvnn I wonder what the differences between motherboards are. I suspect Gigabyte has something other boards don't have. -- 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
[Bug 1302988] [NEW] digikam hangs on 14.04
Public bug reported: Digikam stopped working for me at some point after upgrade last week. When it starts it displays startup screen and hangs. Run from terminal shows: Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started (digikam:6351): GLib-GObject-WARNING **: cannot register existing type 'GstObject' (digikam:6351): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed (digikam:6351): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed (digikam:6351): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed (digikam:6351): GStreamer-CRITICAL **: gst_plugin_feature_get_name: assertion 'GST_IS_PLUGIN_FEATURE (feature)' failed maciej at maciej-vaio ~> apt-cache policy digikam digikam: Installed: 4:3.5.0-0ubuntu10 Candidate: 4:3.5.0-0ubuntu10 Version table: *** 4:3.5.0-0ubuntu10 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: digikam 4:3.5.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 5 10:15:50 2014 InstallationDate: Installed on 2014-01-14 (80 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: digikam UpgradeStatus: Upgraded to trusty on 2014-02-03 (61 days ago) ** Affects: digikam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302988 Title: digikam hangs on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1302988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
