Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Dec 2024 12:44:11 +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-WJhFXt6qbU@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 #309 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
(In reply to Andriy Gapon from comment #308)

How many hardware watchpoints can be active at once?

Which node gets the corruption varies . . .

Failures based on the same kernel and kernel.debug:

*(modlist_t) 0xfffff800045fd2c0 showed (vmcore.9):
{link =3D {tqe_next =3D 0xfffff80000000007, tqe_prev =3D 0xfffff800035b6f00=
},
container =3D 0xfffff8000359f300, name =3D 0xffffffff82e1e010
"amdgpu_raven_mec_bin_fw", version =3D 1}

*(modlist_t) 0xfffff800036f6300 showed (vmcore.0):
{link =3D {tqe_next =3D 0xfffff80000000007, tqe_prev =3D 0xfffff800047571c0=
},
container =3D 0xfffff80004bfad80, name =3D 0xffffffff829ef000
"amdgpu_raven_me_bin_fw", version =3D 1}

*(modlist_t) 0xfffff800035a0200 showed (vmcore.1):
{link =3D {tqe_next =3D 0xfffff80000000007, tqe_prev =3D 0xfffff80003967980=
},
container =3D 0xfffff800039fb300, name =3D 0xffffffff82e62026
"amdgpu_raven_mec2_bin_fw", version =3D 1}

But even when it is the same node by name (and same number
of nodes down the list) the address varies:

*(modlist_t) 0xfffff800047c1180  shows (vmcore.4):
{link =3D {tqe_next =3D 0xfffff80000000007, tqe_prev =3D 0xfffff800047c11c0=
},
container =3D 0xfffff80004861a80, name =3D 0xffffffff82e62026
"amdgpu_raven_mec2_bin_fw", version =3D 1}

Overall those suggest some sort of racy context at the
time for the system, rather than a single,
sequential-processing handling.


For reference: vmcore.[23] were for capturing a successful boot.

vmcore.2 involved a "shutdown now" which unloaded things of
interest, making it of no use.

vmcore.3 was a good capture of a successful boot.

--=20
You are receiving this mail because:
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-WJhFXt6qbU>