Date: Thu, 27 Apr 2023 00:17:34 +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-FOciNN6ibb@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 #173 from George Mitchell <george@m5p.com> --- Here are a collection of points in response to Mark Millard's request. 1. Regardless of the order in which I load kernel modules by hand in single-user mode, I can't ever duplicate the crash. 2. The crash never happens if amdgpu.ko is not loaded. 3. Emmanuel Vadot categorically states that the many, many references to drm_modeset_is_locked failures in the crash summaries are noise and don't indicate drm failures and are caused by virtual terminal switching. But I still get crashes even when there are no virtual terminal switches (because= I didn't start X windows and I didn't type ALT-Fn). 4. The crash always happens after amdgpu.ko is loaded, and (in terms of tim= e of occurrence) at about the time vboxnetflt.ko or acpi_wmi.ko is loaded. The seeming zfs crash can happen even when zfs.ko is loaded before amdgpu.ko, a= nd I theorize that it happens when my large (1TB) USB ZFS-formatted drive comes = on line and gets tasted (after amdgpu.ko is loaded). 5. But I can't come up with any theory in which I can blame the actual cras= h on vboxnetflt.ko, acpi_wmi.ko, or zfs.ko. This bug should not be assigned to freebsd-fs. But I can't tell you to whom it should be assigned. --=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-FOciNN6ibb>