Date: Sat, 2 Sep 2023 07:06:12 +0000 From: Gary Jennejohn <garyj@gmx.de> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD-15 kernel panic when the amdtemp device is in the kernel Message-ID: <20230902090612.6e25fbdc@ernst.home> In-Reply-To: <CANCZdfqXanzJU8Ki0vdjce6wieZrJvbiqs%2Bkqen6d2VQd=pzAQ@mail.gmail.com> References: <20230901130314.460f91bf@ernst.home> <87edjixf6v.wl-herbert@gojira.at> <20230901160441.038539cd@ernst.home> <87cyz2x6x1.wl-herbert@gojira.at> <20230901182134.23b8d5f3@ernst.home> <CANCZdfqXanzJU8Ki0vdjce6wieZrJvbiqs%2Bkqen6d2VQd=pzAQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Fri, 1 Sep 2023 16:00:03 -0600 Warner Losh <imp@bsdimp.com> wrote: > I think that the problem is that admsmn has probed, but not attached (or > failed to attach for some reason), so we find the device, but it's not > initialized yet, so when we call amdsmn_read, it tries to lock a mutex > that's not yet initialized. > > Not sure why this is happening, or why loading it as modules fixes it... > > But since I don't have the hardware, I can't help more. Sorry. > Might it be worth adding an entry to /usr/src/UPDATING for users with older Zen versions like mine (Zen 1 and Zen 2), recommending kldload'ing of amdsmn and amdtemp? -- Gary Jennejohnhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230902090612.6e25fbdc>