Date: Tue, 28 Mar 2023 14:43:26 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko Message-ID: <bug-267028-3630-AugKWAQxkk@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267028-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-267028-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267028 --- Comment #152 from George Mitchell <george@m5p.com> --- As expected, I have had no crashes since avoiding drm-510-kmod and running = in VESA mode. Might it be worth updating 5.10.163_2 to 5.10.163_3? Notes I haven't mentioned recently: Prior to FBSD 13, whenever I tried drm-510-kmod, my machine would lock up hard and not respond to anything oth= er than cycling power. I have a AMD Ryzen 3 2200G with Radeon Vega Graphics running on a Gigabyte B450M D53H motherboard. Every time I boot up, I see = the following ACPI warnings, which don't otherwise seem to affect operation: Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid Leng= th but zero Address: 0x0000000000000000/0x1 (20201113/tbfadt-796) ACPI: \134AOD.WQBA: 1 arguments were passed to a non-method ACPI object (Buffer) (20201113/nsarguments-361) ACPI: \134GSA1.WQCC: 1 arguments were passed to a non-method ACPI object (Buffer) (20201113/nsarguments-361) Do any of you understand these? --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267028-3630-AugKWAQxkk>