Date: Mon, 25 May 2026 19:12:21 -0700 From: Gleb Smirnoff <glebius@freebsd.org> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-current@freebsd.org, freebsd-arm@freebsd.org, samm@freebsd.org, emaste@freebsd.org, adrian@freebsd.org Subject: Re: Panic on shutdown with Pi2B for May 2026 stabilization week Message-ID: <ahUBhTMeSygLTV3N@cell.glebi.us> In-Reply-To: <ahT_bSjgfIL6xyDb@www.zefox.net> References: <ahQBi0Ntgn2iek3J@cell.glebi.us> <ahT_bSjgfIL6xyDb@www.zefox.net>
index | next in thread | previous in thread | raw e-mail
On Mon, May 25, 2026 at 07:03:25PM -0700, bob prohaska wrote: b> There seem to be two workarounds. One is to simply disconnect b> the Pi's ethernet cable before rebooting. b> b> The other is to apply the patch offered in b> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290417 b> b> Might it be possible to merge the patch? This doesn't seem to be a last month regression, so please let's get this out of scope of the stabilization week. Of course, this needs to be fixed and bug 290417 has a patch that looks alright. I'm adding to Cc the author of the patch and src committers who most recently touched smsc(4). -- Gleb Smirnoffhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ahUBhTMeSygLTV3N>