On 11/2/21 17:48, Cy Schubert wrote:
In message <36923A7F-23DE-490D-B1FA-A8B064740BD6@unrelenting.technology>,
Greg
V via freebsd-current writes:
On November 2, 2021 5:16:35 PM GMT+03:00, Michael Butler via freebsd-current
wrote:
On current as of this morning (I haven't tried to bisect yet)
In message <36923A7F-23DE-490D-B1FA-A8B064740BD6@unrelenting.technology>,
Greg
V via freebsd-current writes:
>
>
> On November 2, 2021 5:16:35 PM GMT+03:00, Michael Butler via freebsd-current
> wrote:
> >On current as of this morning (I haven't tried to bisect yet) ..
> >
> > .. with either
On 11/2/21 16:37, Greg V via freebsd-current wrote:
On November 2, 2021 5:16:35 PM GMT+03:00, Michael Butler via freebsd-current
wrote:
On current as of this morning (I haven't tried to bisect yet) ..
.. with either graphics/drm-devel-kmod or graphics/drm-current-kmod,
trying to start a
On November 2, 2021 5:16:35 PM GMT+03:00, Michael Butler via freebsd-current
wrote:
>On current as of this morning (I haven't tried to bisect yet) ..
>
> .. with either graphics/drm-devel-kmod or graphics/drm-current-kmod,
>trying to start a VirtualBox VM triggers this panic ..
>
>#16
On current as of this morning (I haven't tried to bisect yet) ..
FreeBSD toshi.auburn.protected-networks.net 14.0-CURRENT FreeBSD
14.0-CURRENT #42 main-a670e1c13a: Tue Nov 2 09:29:28 EDT 2021
r...@toshi.auburn.protected-networks.net:/usr/obj/usr/src/amd64.amd64/sys/TOSHI
amd64
.. with
