Date: Sat, 14 Mar 2026 13:35:54 -0400 From: Ian FREISLICH <ianfreislich@gmail.com> To: freebsd-current@freebsd.org Subject: Re: panic: supervisor write data, protection violation (vn_read/copyout_smap_erms?) Message-ID: <5f6ad9e8-c5fe-40fe-93df-a1ea52450474@gmail.com> In-Reply-To: <320b245d-85fb-49ba-9ef4-d5d335df39ed@protected-networks.net> References: <CAFt_eMree8BYjJCJyr8po9TxkpT0ipQPy5C%2BCm_UCpM%2B5eCNLQ@mail.gmail.com> <d8132248-0e53-4c0d-bb6c-682995d09f02@protected-networks.net> <abVvYHKqs-Mi7sPQ@albert.catwhisker.org> <320b245d-85fb-49ba-9ef4-d5d335df39ed@protected-networks.net>
index | next in thread | previous in thread | raw e-mail
On 3/14/26 11:54, Michael Butler wrote: > On 3/14/26 10:23, David Wolfskill wrote: >> On Sat, Mar 14, 2026 at 09:28:53AM -0400, Michael Butler wrote: >>> To narrow this .. I can reliably start a kernel built at or before >>> commit >>> 277830b4d3ae. >>> >>> On 3/14/26 09:06, Subbsd wrote: >>>> ... >>>> uname -a: >>>> >>>> FreeBSD host1.my.domain 16.0-CURRENT FreeBSD 16.0-CURRENT #0 >>>> main-f91464171d61: Sat Mar 14 12:35:27 UTC 2026 >>>> root@host1.my.domain:/usr/obj/usr/jails/src/src_16/src/amd64.amd64/ >>>> sys/GENERIC >>>> amd64 >>> .... >> >> I updated my headless build machine from main-n284480-9a9f93bcf1aa to >> main-n284504-f91464171d61 this morning, but it panicked prior to >> completing the transition to multi-user mode. >> >> Checking >> https://lists.freebsd.org/archives/dev-commits-src-main/2026- >> March/040570.html, >> blame is cast on 914a53570750; further in that thread, kib@ provides a >> tentative patch (but I have not tested it). > > The patch at the end of this thread appears to solve the problem. Thanks! I can also confirm that it fixes the same panic for me. Ianhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5f6ad9e8-c5fe-40fe-93df-a1ea52450474>