Re: current now panics when starting VBox VM

On 11/3/21 11:13, Konstantin Belousov wrote: On Wed, Nov 03, 2021 at 11:05:11AM -0400, Michael Butler via freebsd-emulation wrote: On 11/3/21 10:36, Ed Maste wrote: The kgdb back-trace isn't any more enlightening to me :-( __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55 55

Re: current now panics when starting VBox VM

On 11/3/21 11:13, Konstantin Belousov wrote: On Wed, Nov 03, 2021 at 11:05:11AM -0400, Michael Butler via freebsd-emulation wrote: On 11/3/21 10:36, Ed Maste wrote: The kgdb back-trace isn't any more enlightening to me :-( __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55 55

Re: current now panics when starting VBox VM

On 11/3/21 10:36, Ed Maste wrote: On Tue, 2 Nov 2021 at 18:32, Michael Butler via freebsd-emulation wrote: Before reporting this, I rebuilt world including kernel, all kmods and virtualbox itself to no avail :-( Thanks for confirming. Now that the WARN_ON noise is disabled by default would

Re: current now panics when starting VBox VM

On 11/3/21 10:36, Ed Maste wrote: On Tue, 2 Nov 2021 at 18:32, Michael Butler via freebsd-emulation wrote: Before reporting this, I rebuilt world including kernel, all kmods and virtualbox itself to no avail :-( Thanks for confirming. Now that the WARN_ON noise is disabled by default would

Re: current now panics when starting VBox VM

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)

Re: current now panics when starting VBox VM

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)

Re: VirtualBox fails to build on -current; more no-common fall-out?

On 9/24/20 12:06 PM, Michael Butler wrote: I get a duplicate symbol error as follows .. kBuild: Linking VBoxVNCMain kBuild: Linking VBoxVNC The failing command: @c++ -shared   '-Wl,-rpath,/usr/local/lib/virtualbox' -fPIC  -m64   -o

VirtualBox fails to build on -current; more no-common fall-out?

I get a duplicate symbol error as follows .. kBuild: Linking VBoxVNCMain kBuild: Linking VBoxVNC The failing command: @c++ -shared '-Wl,-rpath,/usr/local/lib/virtualbox' -fPIC -m64 -o