[Bug 1942684] [NEW] Kernel 5.14.0/1 fails to boot
Public bug reported: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc6. I have not tried 5.14.0-rc7 since it is not available on the mainline app FWIW. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: hirsute kernel-bug ** Attachment added: "Crash log" https://bugs.launchpad.net/bugs/1942684/+attachment/5522972/+files/journal.txt ** Tags added: hirsute kernel-bug ** Description changed: - I have been testing kernels 5.14.0 and 5.14.1 since their release + I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to - boot. + boot with either one. - I am able to boot just fine with 5.14.0-rc6. I have not tried 5.14.0-rc7 - since it is not available on the mainline app FWIW. + However, I am able to boot just fine with 5.14.0-rc6. I have not tried + 5.14.0-rc7 since it is not available on the mainline app FWIW. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.0/1 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942684] Re: Kernel 5.14.0/1 fails to boot
apport information ** Tags added: apport-collected wayland-session ** Description changed: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc6. I have not tried 5.14.0-rc7 since it is not available on the mainline app FWIW. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65.1 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2021-07-04 (62 days ago) + InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: wayland-session hirsute + Uname: Linux 5.14.0-051400rc6-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1942684/+attachment/5522973/+files/ProcCpuinfoMinimal.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/1942684 Title: Kernel 5.14.0/1 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942684] Re: Kernel 5.14.0/1 fails to boot
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.0/1 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942377] Re: Linux 5.14 fails to boot
I have the same behavior, but my error is caused by an invalid opcode (i think) - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942377 Title: Linux 5.14 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942684] Re: Kernel 5.14.0/1 fails to boot
** Description changed: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. - However, I am able to boot just fine with 5.14.0-rc6. I have not tried - 5.14.0-rc7 since it is not available on the mainline app FWIW. + However, I am able to boot just fine with 5.14.0-rc7. + journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.0/1 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942684] Re: Kernel 5.14.0/1/5.13.14 fails to boot
Seems like it is one of these commits - https://cgit.freedesktop.org/drm/drm/tag/?h=drm-fixes-2021-08-27 I just looked at changelog for 5.13.14 and those 3 commits were also added. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.0/1/5.13.14 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
** Summary changed: - Kernel 5.14.0/1/5.13.14 fails to boot + Kernel 5.14.X / 5.13.14 fails to boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
OK, so none of the 5.14.0/1/2/3 kernels will boot. As I mentioned before...1 of the 3 pacthes introduced the regression: Borislav Petkov (1): drm/amdgpu: Fix build with missing pm_suspend_target_state module export Christian König (1): drm/amdgpu: use the preferred pin domain after the check Michel Dänzer (1): drm/amdgpu: Cancel delayed work when GFXOFF is disabled This the commit in the linux repo - 77dd11439b86e3f7990e4c0c9e0b67dca82750ba Here is the error my from uploaded crash log: Sep 04 09:07:39 bluestang-pc kernel: RIP: 0010:amdgpu_discovery_reg_base_init+0x225/0x260 [amdgpu] Sep 04 09:07:39 bluestang-pc kernel: Code: 0f 85 d4 fe ff ff 48 83 45 c0 01 48 8b 45 c0 39 45 c8 0f 8f 55 fe ff ff 8b 45 b4 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 <0f> 0b 48 c7 c7 e4 5a 61 c1 e8 9d 79 10 ff eb de 41 89 d0 48 c7 c7 Sep 04 09:07:39 bluestang-pc kernel: RSP: 0018:b883c1907928 EFLAGS: 00010202 Sep 04 09:07:39 bluestang-pc kernel: RAX: 0008 RBX: 99558b89f128 RCX: 0006 Sep 04 09:07:39 bluestang-pc kernel: RDX: c1615b69 RSI: c15c0428 RDI: Sep 04 09:07:39 bluestang-pc kernel: RBP: b883c1907978 R08: 0008 R09: 000b Sep 04 09:07:39 bluestang-pc kernel: R10: 99558b89f120 R11: R12: 995587c0 Sep 04 09:07:39 bluestang-pc kernel: R13: 0019 R14: 0019 R15: 99558b89f120 Sep 04 09:07:39 bluestang-pc kernel: FS: 7f3d5b7138c0() GS:995c7ea4() knlGS: Sep 04 09:07:39 bluestang-pc kernel: CS: 0010 DS: ES: CR0: 80050033 Sep 04 09:07:39 bluestang-pc kernel: CR2: 7fc505b6c420 CR3: 000106d9 CR4: 00750ee0 Sep 04 09:07:39 bluestang-pc kernel: PKRU: 5554 Sep 04 09:07:39 bluestang-pc kernel: Call Trace: Sep 04 09:07:39 bluestang-pc kernel: nv_set_ip_blocks+0x8e/0xab0 [amdgpu] Sep 04 09:07:39 bluestang-pc kernel: amdgpu_device_ip_early_init+0x2b1/0x47f [amdgpu] Sep 04 09:07:39 bluestang-pc kernel: ? amdgpu_device_get_job_timeout_settings+0x90/0x1cc [amdgpu] Sep 04 09:07:39 bluestang-pc kernel: amdgpu_device_init.cold+0xc9/0x6d1 [amdgpu] Sep 04 09:07:39 bluestang-pc kernel: amdgpu_driver_load_kms+0x6d/0x310 [amdgpu] Sep 04 09:07:39 bluestang-pc kernel: amdgpu_pci_probe+0x11b/0x1a0 [amdgpu] Sep 04 09:07:39 bluestang-pc kernel: local_pci_probe+0x48/0x80 Sep 04 09:07:39 bluestang-pc kernel: pci_device_probe+0x105/0x1d0 Sep 04 09:07:39 bluestang-pc kernel: really_probe+0x1fe/0x400 Sep 04 09:07:39 bluestang-pc kernel: __driver_probe_device+0x109/0x180 Sep 04 09:07:39 bluestang-pc kernel: driver_probe_device+0x23/0x90 Sep 04 09:07:39 bluestang-pc kernel: __driver_attach+0xac/0x1b0 Sep 04 09:07:39 bluestang-pc kernel: ? __device_attach_driver+0xe0/0xe0 Sep 04 09:07:39 bluestang-pc kernel: bus_for_each_dev+0x7e/0xc0 Sep 04 09:07:39 bluestang-pc kernel: driver_attach+0x1e/0x20 Sep 04 09:07:39 bluestang-pc kernel: bus_add_driver+0x135/0x1f0 Sep 04 09:07:39 bluestang-pc kernel: driver_register+0x95/0xf0 Sep 04 09:07:39 bluestang-pc kernel: __pci_register_driver+0x68/0x70 Sep 04 09:07:39 bluestang-pc kernel: amdgpu_init+0x7c/0x1000 [amdgpu] Sep 04 09:07:39 bluestang-pc kernel: ? 0xc0e95000 Sep 04 09:07:39 bluestang-pc kernel: do_one_initcall+0x48/0x1d0 Sep 04 09:07:39 bluestang-pc kernel: ? kmem_cache_alloc_trace+0x159/0x2c0 Sep 04 09:07:39 bluestang-pc kernel: do_init_module+0x62/0x290 Sep 04 09:07:39 bluestang-pc kernel: load_module+0xaa8/0xb40 Sep 04 09:07:39 bluestang-pc kernel: __do_sys_finit_module+0xbf/0x120 Sep 04 09:07:39 bluestang-pc kernel: __x64_sys_finit_module+0x18/0x20 Sep 04 09:07:39 bluestang-pc kernel: do_syscall_64+0x5c/0xc0 Sep 04 09:07:39 bluestang-pc kernel: ? exit_to_user_mode_prepare+0x37/0xb0 Sep 04 09:07:39 bluestang-pc kernel: ? syscall_exit_to_user_mode+0x27/0x50 Sep 04 09:07:39 bluestang-pc kernel: ? __x64_sys_newfstatat+0x1c/0x20 Sep 04 09:07:39 bluestang-pc kernel: ? do_syscall_64+0x69/0xc0 Sep 04 09:07:39 bluestang-pc kernel: ? do_syscall_64+0x69/0xc0 Sep 04 09:07:39 bluestang-pc kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Sep 04 09:07:39 bluestang-pc kernel: RIP: 0033:0x7f3d5bbcbf6d Sep 04 09:07:39 bluestang-pc kernel: Code: 28 0d 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d cb de 0c 00 f7 d8 64 89 01 48 Sep 04 09:07:39 bluestang-pc kernel: RSP: 002b:7fffa53a9048 EFLAGS: 0246 ORIG_RAX: 0139 Sep 04 09:07:39 bluestang-pc kernel: RAX: ffda RBX: 55866fe87bf0 RCX: 7f3d5bbcbf6d Sep 04 09:07:39 bluestang-pc kernel: RDX: RSI: 7f3d5bd71e2d RDI: 001a Sep 04 09:07:39 bluestang-pc kernel: RBP: 0002 R08: R09: 55866e61889d Sep 04 09:07:39 bluestang-pc kernel: R10:
[Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
Patch file of commit that caused the regression ** Patch added: "patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+attachment/5524711/+files/5.14.X-KOOPS.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
The patch "drm/amd/amdgpu: Increase HWIP_MAX_INSTANCE to 10" fixes the KOOPS. I am currently on 5.15-rc2 and have not experienced any issues. I reckon that 5.14.7 will also be fine since the changelog shows that the same patch was backported. Looks like this bug has always been there but was brought to light once CONFIG_UBSAN_TRAP was enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
