Launchpad has imported 28 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=194825.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2017-03-09T11:15:45+00:00 fiedzia wrote: Created attachment 255151 kernel config 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 to: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/3 ------------------------------------------------------------------------ On 2017-03-09T11:17:14+00:00 fiedzia wrote: Created attachment 255153 lspci_vv_nn Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/4 ------------------------------------------------------------------------ On 2017-03-09T11:17:58+00:00 fiedzia wrote: Created attachment 255155 dmidecode Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/5 ------------------------------------------------------------------------ On 2017-03-09T11:18:41+00:00 fiedzia wrote: Created attachment 255157 find_sys_bus_acpi Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/6 ------------------------------------------------------------------------ On 2017-03-09T11:19:23+00:00 fiedzia wrote: Created attachment 255159 content of /sys/bus/acpi/devices/AMDI0040 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/7 ------------------------------------------------------------------------ On 2017-03-10T09:25:21+00:00 fiedzia wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/13 ------------------------------------------------------------------------ On 2017-03-13T09:04:55+00:00 fiedzia wrote: >tested on 4.11 and r4.11rc1 Should be "tested on 4.10 and r4.11rc" Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/28 ------------------------------------------------------------------------ On 2017-05-09T21:02:38+00:00 jonnyboysmithy wrote: Link to what appears to be the same bug over at the ubuntu launchpad site: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360 (its linked there to here, but not vice versa, so doing it above^ ) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/144 ------------------------------------------------------------------------ On 2017-05-16T04:07:46+00:00 mtanski wrote: This appears to impact all of Gigabyte's AMD AM4 motherboards. I have attempted to contact the vendor on their forums here: http://forum.gigabyte.us/thread/886/am4-beta-bios- thread?page=47&scrollTo=4429 . Promised to look into it, but haven't heard back. Offered to fix it myself in upstream in a PM if given enough info. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/157 ------------------------------------------------------------------------ On 2017-05-17T15:44:54+00:00 dfk_7677 wrote: Knowing that kernel 4.4 boots normally (Ubuntu 16.04) and 4.8 is the first not booting (Ubuntu 16.10+), can't we assume that the problem is in the commits for 4.8 after 16/09/15? https://github.com/torvalds/linux/commits/v4.8/drivers/pinctrl/pinctrl-amd.c https://github.com/torvalds/linux/commits/v4.4/drivers/pinctrl/pinctrl-amd.c Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/163 ------------------------------------------------------------------------ On 2017-06-02T06:30:56+00:00 adebeus wrote: I'm getting a similar error on an Acer E5-553G laptop (AMD Excavator, not Ryzen). It doesn't prevent the system from booting but does make the ELAN touchpad stop working shortly after boot, with similar dmesg output (though seemingly on a smaller volume - the bad_chained_irq errors take awhile to page through with less, but don't come anywhere near filling a 400MB file, and stop completely after the touchpad switches off). This occurs with all recent kernel versions I've tried (4.9.30, 4.10.17, 4.11.3) except 4.12-rc2, which doesn't get this error but also doesn't recognize the touchpad at all. With 4.12-rc3, it is back to the same behavior as the 4.11.3 kernel. The only kernel I have found that works is the Ubuntu 4.4 kernel. The stock 4.4.70 kernel gets the same error, but if I replace the pinctrl- amd.c file with the version from the Ubuntu 16.04 kernel, it works fine. I haven't tried using the Ubuntu 4.4 pinctrl-amd.c file with newer kernels, but presume that it would be incompatible. I did look at the Ubuntu 17.04 kernel tree (4.10) on github and noticed that there's no difference between that pinctrl-amd.c and the upstream one, so it looks like Ubuntu has only fixed this issue in the 4.4 kernel series. I have not yet tried updating the BIOS since Acer only provides the update as a Windows EXE. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/190 ------------------------------------------------------------------------ On 2017-06-02T06:33:07+00:00 adebeus wrote: I should also note that I'm using OpenRC and not systemd, which might be why I'm able to complete the boot process. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/191 ------------------------------------------------------------------------ On 2017-07-10T06:10:37+00:00 rootexpression wrote: Using Gigabyte X370 K7 (this issue exists on all gigabyte B350 and X370 boards as far as I know). I get this issue, and am completely unable to boot in Ubuntu 16.04, and have found reports of the same issue on 17.04. I can however install and boot in Manjaro (arch) just fine. The system runs fine mostly, but has what appears to be a memory leak related to vector 7 and xorg (a conflict possibly?). Issue persists in kernel 4.12 RC7 on arch base. Found this: https://bugzilla.proxmox.com/show_bug.cgi?id=1366 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/227 ------------------------------------------------------------------------ On 2017-07-10T06:13:16+00:00 rootexpression wrote: I should note that at Gigabyte, they were able to get Ubuntu 16.04 to boot, and supposedly install on the F4 bios. I could not replicate their results. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/228 ------------------------------------------------------------------------ On 2017-07-15T23:16:03+00:00 edisonalvaringo wrote: I get this irq 7: nobody cared (try booting with the "irqpoll" option) Jul 15 19:17:29 linux-x5uw kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.12.0-2.g2399a91-default #1 Jul 15 19:17:29 linux-x5uw kernel: Hardware name: Gigabyte Technology Co., Ltd. AB350-Gaming/AB350-Gaming-CF, BIOS F5 06/19/2017 Jul 15 19:17:29 linux-x5uw kernel: Call Trace: Jul 15 19:17:29 linux-x5uw kernel: <IRQ> Jul 15 19:17:29 linux-x5uw kernel: dump_stack+0x5c/0x84 Jul 15 19:17:29 linux-x5uw kernel: __report_bad_irq+0x30/0xc0 Jul 15 19:17:29 linux-x5uw kernel: note_interrupt+0x23e/0x290 Jul 15 19:17:29 linux-x5uw kernel: handle_irq_event_percpu+0x41/0x50 Jul 15 19:17:29 linux-x5uw kernel: handle_irq_event+0x37/0x60 Jul 15 19:17:29 linux-x5uw kernel: handle_fasteoi_irq+0x95/0x160 Jul 15 19:17:29 linux-x5uw kernel: handle_irq+0x19/0x30 Jul 15 19:17:29 linux-x5uw kernel: do_IRQ+0x41/0xc0 Jul 15 19:17:29 linux-x5uw kernel: common_interrupt+0x8c/0x8c Jul 15 19:17:29 linux-x5uw kernel: </IRQ> Jul 15 19:17:29 linux-x5uw kernel: RIP: 0010:native_safe_halt+0x2/0x10 Jul 15 19:17:29 linux-x5uw kernel: RSP: 0018:ffffffffa8e03df8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffc8 Jul 15 19:17:29 linux-x5uw kernel: RAX: 0000000000000000 RBX: ffff9cea5661a000 RCX: 0000000000000034 Jul 15 19:17:29 linux-x5uw kernel: RDX: 4ec4ec4ec4ec4ec5 RSI: ffffffffa8ed9cc0 RDI: ffff9cea5661a064 Jul 15 19:17:29 linux-x5uw kernel: RBP: ffff9cea5661a064 R08: cccccccccccccccd R09: 0000000000000008 Jul 15 19:17:29 linux-x5uw kernel: R10: 000000000000000a R11: 000000000000000a R12: 0000000000000001 Jul 15 19:17:29 linux-x5uw kernel: R13: 0000000000000001 R14: 0000000000000001 R15: 00000004118ee7d0 Jul 15 19:17:29 linux-x5uw kernel: acpi_safe_halt.part.5+0xa/0x20 Jul 15 19:17:29 linux-x5uw kernel: acpi_idle_enter+0xf6/0x290 Jul 15 19:17:29 linux-x5uw kernel: cpuidle_enter_state+0xef/0x2e0 Jul 15 19:17:29 linux-x5uw kernel: do_idle+0x184/0x1e0 Jul 15 19:17:29 linux-x5uw kernel: cpu_startup_entry+0x5d/0x60 Jul 15 19:17:29 linux-x5uw kernel: start_kernel+0x422/0x42a Jul 15 19:17:29 linux-x5uw kernel: ? early_idt_handler_array+0x120/0x120 Jul 15 19:17:29 linux-x5uw kernel: x86_64_start_kernel+0x12c/0x13b Jul 15 19:17:29 linux-x5uw kernel: secondary_startup_64+0x9f/0x9f Jul 15 19:17:29 linux-x5uw kernel: handlers: Jul 15 19:17:29 linux-x5uw kernel: [<ffffffffc0604030>] amd_gpio_irq_handler [pinctrl_amd] Jul 15 19:17:29 linux-x5uw kernel: Disabling IRQ #7 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/229 ------------------------------------------------------------------------ On 2017-07-16T03:17:04+00:00 rootexpression wrote: (In reply to edisonalvaringo from comment #14) > I get this > > irq 7: nobody cared (try booting with the "irqpoll" option) > Jul 15 19:17:29 linux-x5uw kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted > 4.12.0-2.g2399a91-default #1 > Jul 15 19:17:29 linux-x5uw kernel: Hardware name: Gigabyte Technology Co., > Ltd. AB350-Gaming/AB350-Gaming-CF, BIOS F5 06/19/2017 > Jul 15 19:17:29 linux-x5uw kernel: Call Trace: > Jul 15 19:17:29 linux-x5uw kernel: <IRQ> > Jul 15 19:17:29 linux-x5uw kernel: dump_stack+0x5c/0x84 > Jul 15 19:17:29 linux-x5uw kernel: __report_bad_irq+0x30/0xc0 > Jul 15 19:17:29 linux-x5uw kernel: note_interrupt+0x23e/0x290 > Jul 15 19:17:29 linux-x5uw kernel: handle_irq_event_percpu+0x41/0x50 > Jul 15 19:17:29 linux-x5uw kernel: handle_irq_event+0x37/0x60 > Jul 15 19:17:29 linux-x5uw kernel: handle_fasteoi_irq+0x95/0x160 > Jul 15 19:17:29 linux-x5uw kernel: handle_irq+0x19/0x30 > Jul 15 19:17:29 linux-x5uw kernel: do_IRQ+0x41/0xc0 > Jul 15 19:17:29 linux-x5uw kernel: common_interrupt+0x8c/0x8c > Jul 15 19:17:29 linux-x5uw kernel: </IRQ> > Jul 15 19:17:29 linux-x5uw kernel: RIP: 0010:native_safe_halt+0x2/0x10 > Jul 15 19:17:29 linux-x5uw kernel: RSP: 0018:ffffffffa8e03df8 EFLAGS: > 00000246 ORIG_RAX: ffffffffffffffc8 > Jul 15 19:17:29 linux-x5uw kernel: RAX: 0000000000000000 RBX: > ffff9cea5661a000 RCX: 0000000000000034 > Jul 15 19:17:29 linux-x5uw kernel: RDX: 4ec4ec4ec4ec4ec5 RSI: > ffffffffa8ed9cc0 RDI: ffff9cea5661a064 > Jul 15 19:17:29 linux-x5uw kernel: RBP: ffff9cea5661a064 R08: > cccccccccccccccd R09: 0000000000000008 > Jul 15 19:17:29 linux-x5uw kernel: R10: 000000000000000a R11: > 000000000000000a R12: 0000000000000001 > Jul 15 19:17:29 linux-x5uw kernel: R13: 0000000000000001 R14: > 0000000000000001 R15: 00000004118ee7d0 > Jul 15 19:17:29 linux-x5uw kernel: acpi_safe_halt.part.5+0xa/0x20 > Jul 15 19:17:29 linux-x5uw kernel: acpi_idle_enter+0xf6/0x290 > Jul 15 19:17:29 linux-x5uw kernel: cpuidle_enter_state+0xef/0x2e0 > Jul 15 19:17:29 linux-x5uw kernel: do_idle+0x184/0x1e0 > Jul 15 19:17:29 linux-x5uw kernel: cpu_startup_entry+0x5d/0x60 > Jul 15 19:17:29 linux-x5uw kernel: start_kernel+0x422/0x42a > Jul 15 19:17:29 linux-x5uw kernel: ? early_idt_handler_array+0x120/0x120 > Jul 15 19:17:29 linux-x5uw kernel: x86_64_start_kernel+0x12c/0x13b > Jul 15 19:17:29 linux-x5uw kernel: secondary_startup_64+0x9f/0x9f > Jul 15 19:17:29 linux-x5uw kernel: handlers: > Jul 15 19:17:29 linux-x5uw kernel: [<ffffffffc0604030>] amd_gpio_irq_handler > [pinctrl_amd] > Jul 15 19:17:29 linux-x5uw kernel: Disabling IRQ #7 what kernel is that on? what distro, etc? havn't seen that before. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/230 ------------------------------------------------------------------------ On 2017-07-16T18:55:32+00:00 edisonalvaringo wrote: Opensuse 42.2. linux-4.11.0-2.g057f66f from Opensuse tumbleweed repos. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/231 ------------------------------------------------------------------------ On 2017-07-16T18:57:19+00:00 edisonalvaringo wrote: booting with irqpoll it make thing much worse and spams dmesg with "lost hpet rtc xxxx interrupts" Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/232 ------------------------------------------------------------------------ On 2017-07-16T19:01:58+00:00 edisonalvaringo wrote: I don't know if it is related but I'm having trouble resuming from hibernation sometimes the usb ports will stop working . I get this message also [ 877.231395] ------------[ cut here ]------------ [ 877.231395] WARNING: CPU: 0 PID: 4060 at ../arch/x86/kernel/cpu/mcheck/mce_amd.c:191 mce_amd_feature_init+0x27d/0x2c0 [ 877.231396] Modules linked in: ccm dm_crypt dm_mod loop ppdev parport_pc parport vmw_vsock_vmci_transport vsock vmw_vmci nf_log_ipv6 xt_pkttype nf_log_ipv4 nf_log_common xt_LOG xt_limit af_packet ip6t_REJECT nf_reject_ipv6 xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT nf_reject_ipv4 iptable_raw xt_CT iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack libcrc32c ip6table_filter ip6_tables x_tables it87 hwmon_vid joydev fuse snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_intel snd_hda_codec edac_mce_amd snd_hda_core snd_hwdep snd_pcm snd_timer kvm i2c_designware_platform snd irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel ath9k ath9k_common ath9k_hw ath mac80211 [ 877.231405] cfg80211 ghash_clmulni_intel rfkill r8169 mii pcbc soundcore ccp pinctrl_amd shpchp aesni_intel i2c_piix4 aes_x86_64 acpi_cpufreq tpm_infineon tpm_tis tpm_tis_core tpm gpio_amdpt gpio_generic pcspkr crypto_simd glue_helper cryptd button i2c_designware_core wmi arc4 ppp_mppe hid_generic usbhid bcache amdgpu i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm xhci_pci xhci_hcd sr_mod drm cdrom usbcore msr sg ppp_generic slhc efivarfs [ 877.231412] CPU: 0 PID: 4060 Comm: systemd-sleep Tainted: G W 4.12.0-2.g2399a91-default #1 [ 877.231413] Hardware name: Gigabyte Technology Co., Ltd. AB350-Gaming/AB350-Gaming-CF, BIOS F5 06/19/2017 [ 877.231413] task: ffff995671398000 task.stack: ffffbc5a81a0c000 [ 877.231414] RIP: 0010:mce_amd_feature_init+0x27d/0x2c0 [ 877.231414] RSP: 0018:ffffbc5a81a0fd08 EFLAGS: 00010096 [ 877.231415] RAX: 0000000000000028 RBX: 0000000000000005 RCX: ffffffff98e5abe8 [ 877.231415] RDX: ffffffff98e5abe8 RSI: 0000000000000096 RDI: 0000000000000002 [ 877.231415] RBP: 00000000c000205d R08: 0000000000000000 R09: 0000000000000028 [ 877.231416] R10: ffffbc5a81a0fc80 R11: 0000000000000000 R12: 0000000000000006 [ 877.231416] R13: 0000000000000000 R14: 0000000000000000 R15: ffffbc5a81a0fd24 [ 877.231417] FS: 00007f96b749e740(0000) GS:ffff9956d6600000(0000) knlGS:0000000000000000 [ 877.231417] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 877.231417] CR2: 00007f420b571926 CR3: 0000000213bc5000 CR4: 00000000003406f0 [ 877.231418] Call Trace: [ 877.231419] mce_syscore_resume+0x1e/0x30 [ 877.231420] syscore_resume+0x4b/0x1a0 [ 877.231421] suspend_devices_and_enter+0x488/0x7e0 [ 877.231422] pm_suspend+0x31a/0x390 [ 877.231423] state_store+0x42/0x90 [ 877.231424] kernfs_fop_write+0xfa/0x180 [ 877.231424] __vfs_write+0x23/0x140 [ 877.231426] ? __getnstimeofday64+0x3b/0xd0 [ 877.231427] ? getnstimeofday64+0xa/0x20 [ 877.231427] ? __audit_syscall_entry+0xab/0x100 [ 877.231428] ? security_file_permission+0x36/0xb0 [ 877.231429] vfs_write+0xad/0x1a0 [ 877.231430] SyS_write+0x42/0x90 [ 877.231431] do_syscall_64+0x57/0xc0 [ 877.231432] entry_SYSCALL64_slow_path+0x25/0x25 [ 877.231432] RIP: 0033:0x7f96b6bdc2d0 [ 877.231432] RSP: 002b:00007ffe6b5bfee8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 877.231433] RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f96b6bdc2d0 [ 877.231433] RDX: 0000000000000004 RSI: 00007f96b74e5000 RDI: 0000000000000004 [ 877.231434] RBP: 00007f96b74e5000 R08: 00007f96b749e740 R09: 00007f96b749e740 [ 877.231434] R10: 0000000000000022 R11: 0000000000000246 R12: 0000559c982b41a0 [ 877.231434] R13: 0000000000000001 R14: 0000000000000004 R15: 0000000000000000 [ 877.231435] Code: e0 04 8b 04 07 83 f8 0c 77 0b 48 c1 e0 04 48 8b b0 20 8a 80 98 48 c7 c7 61 57 a2 98 48 89 4c 24 10 48 89 54 24 08 e8 74 41 15 00 <0f> ff 48 8b 4c 24 10 48 8b 54 24 08 e9 eb fe ff ff 44 89 e6 48 [ 877.231448] ---[ end trace a2abf38abea5bc60 ]--- Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/233 ------------------------------------------------------------------------ On 2017-07-17T04:52:39+00:00 edisonalvaringo wrote: Should I open a new bug? the irq problem is similar on pinctrl_amd, if compile a kernel without pinctrl there are no strange messages. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/234 ------------------------------------------------------------------------ On 2017-10-07T05:21:57+00:00 ldkxingzhe wrote: I got the same problem. Arch, kernel: 4.13, CPU: Ryzen 7 1700, motherboard: B350 Plus. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/235 ------------------------------------------------------------------------ On 2017-10-07T11:40:41+00:00 rootexpression wrote: https://www.phoronix.com/scan.php?page=news_item&px=Ryzen-Segv-Response Perhaps this is related to the hardware bug from that first batch of processors. Just don't want to see you wasting your time fixing something with software that you can't fix with software. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/236 ------------------------------------------------------------------------ On 2017-10-07T15:28:09+00:00 ldkxingzhe wrote: maybe. but my win10 is fine. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/237 ------------------------------------------------------------------------ On 2017-10-07T22:00:36+00:00 rootexpression wrote: (In reply to ldk from comment #22) > maybe. but my win10 is fine. Uh huh. Please read up on the hardware bug. "AMD engineers found the problem to be very complex and characterize it as a performance marginality problem exclusive to certain workloads on Linux." Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/238 ------------------------------------------------------------------------ On 2018-01-23T23:42:52+00:00 jpujades wrote: Similar problem with Acer TravelMate B117-M (SSD disk). Upgraded the BIOS system from 1.07 to 1.13 and 1.15 (the latest) Lubuntu 16.04 LTS HWE 64 bit System works fine with 4.10.0-42 System shows the messages at start-up when using 4.13.0-26 or 4.13.0-31 kernels. Curiously, if I turn off the system, connect/disconnect the battery (battery reset hole at the bottom of the laptop) and turn on the system, NO errors. At next boot, errors reappear. However, the system seems to work without problems, despite the start-up IRQ errors. I have to test more. I don't know if I will have performance problems or other kind of troubles. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/241 ------------------------------------------------------------------------ On 2018-01-24T16:28:22+00:00 jpujades wrote: It seems to be related with https://bugzilla.kernel.org/show_bug.cgi?id=194945#c73 I can see also bad interrupts for chv-gpio No more IRQ errors with kernel 4.14.15-041415-generic http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14.15/ Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/242 ------------------------------------------------------------------------ On 2018-01-25T15:53:26+00:00 jpujades wrote: "System shows the messages at start-up when using 4.13.0-26 or 4.13.0-31 kernels." I'm sorry, the messages were: unexpected irq trap at vector 73 Tested on HP Convertible x360 11-ab0XX with same results. No more messages about IRQ errors with kernel 4.14.15-041415-generic Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/243 ------------------------------------------------------------------------ On 2018-01-25T16:03:09+00:00 rootexpression wrote: (In reply to Josep Pujadas-Jubany from comment #24) > Similar problem with Acer TravelMate B117-M (SSD disk). > Upgraded the BIOS system from 1.07 to 1.13 and 1.15 (the latest) > Lubuntu 16.04 LTS HWE 64 bit > > System works fine with 4.10.0-42 > System shows the messages at start-up when using 4.13.0-26 or 4.13.0-31 > kernels. > > Curiously, if I turn off the system, connect/disconnect the battery (battery > reset hole at the bottom of the laptop) and turn on the system, NO errors. > > At next boot, errors reappear. > > However, the system seems to work without problems, despite the start-up IRQ > errors. I have to test more. I don't know if I will have performance > problems or other kind of troubles. This bug report here is for AMD Ryzen cpus. You'll need to find or make a bug report for your laptop. The bug discussed here is specific to only AMD Ryzen CPUs. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/244 ** Changed in: linux Status: Confirmed => Fix Released ** Bug watch added: bugzilla.proxmox.com/ #1366 https://bugzilla.proxmox.com/show_bug.cgi?id=1366 ** Bug watch added: Linux Kernel Bug Tracker #194945 https://bugzilla.kernel.org/show_bug.cgi?id=194945 -- 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 Gigabyte AM4 motherboards (AMD Ryzen) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
