‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On July 23, 2018 5:38 AM, Mike Larkin <[email protected]> wrote:
> On Fri, Jul 20, 2018 at 08:31:37AM -0400, Adam Steen wrote: > > > > Synopsis: Kernel Panic 6.3 on Lenovo x220 > > > Category: System > > > Environment: > > > System : OpenBSD 6.3 > > > Details : OpenBSD 6.3-current (GENERIC) #123: Fri Jul 13 00:36:30 MDT 2018 > > > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC > > > > Architecture : OpenBSD.amd64 > > Machine : amd64 > > > > > > > Description: > > > I was testing MirageOS on OpenBSD and had to leave so I ctrl-C the > > > program and then kernel panic'd. When i could attempt to reproduce the > > > problem, i have not been able to reproduce it to gather better > > > information. > > > > The exact command i ran: doas ukvm-bin hello.ukvm > > To get to this point i have installed the ocaml 4.06/opam 2 ports patch and > > installed both ocaml and opam2 (i have other pkgs installed in the past) > > then ran > > rm -rf $HOME/.opam && \ > > rm -rf $HOME/devl/mirage-skeleton && \ > > opam init -a && \ > > eval $(opam env) && \ > > opam pin add solo5-kernel-ukvm git://github.com/Solo5/solo5 -y && > > opam install mirage -y && \ > > git clone git://github.com/mirage/mirage-skeleton.git > > $HOME/devl/mirage-skeleton && \ > > cd $HOME/devl/mirage-skeleton/tutorial/hello && \ > > mirage configure -t ukvm && \ > > gmake depends && \ > > gmake > > once you have everything built, you can then run > > doas ukvm-bin hello.ukvm > > and then CTRL-C during its run. (I am yet to reproduce the panic) > > this program directly uses /dev/vmm without using vmd or vmctl. > > Photo of the crash: > > https://s22.postimg.cc/r9yma7q8h/crash.jpg > > Photo of the trace: > > https://s22.postimg.cc/wy4x12zpt/trace.jpg > > Sorry i didn't know enough at the time to get more information. > > This is the same bug that many people are seeing. It's not reproducible, > and I don't know what is causing it. > > -ml Hi Mike and Others sorry if this is not required or unwelcome just in case it was needed, I was able to reproduce the panic by launching and killing lots of unikernels based on MirageOS/Solo5/vmm, i have been able to reproduce this panic 4 times today, 3 times in the last hour. i used the following script to launch and kill the unikernels #!/usr/bin/env ksh i=1 while (( i <= 10000 )) do echo "\n\n$i\n" (( i+=1 )) devl/mirage-skeleton/tutorial/hello/ukvm-bin devl/mirage-skeleton/tutorial/hello/hello.ukvm & x=$! sleep 0.1 kill -s INT $x done But first you will need to get Mirage installed. first apply the "UPDATE of lang/ocaml to 4.06 and dependent ports" diff by chrisz@ [1] then run opam init -a && \ eval $(opam env) && \ opam pin add solo5-kernel-ukvm git://github.com/Solo5/solo5 -y && opam install mirage -y&& \ git clone git://github.com/mirage/mirage-skeleton.git $HOME/devl/mirage-skeleton && \ cd $HOME/devl/mirage-skeleton/tutorial/hello && \ mirage configure -t ukvm && \ gmake depends && \ gmake and you should have ukvm-bin and hello.ukvm in $HOME/devl/mirage-skeleton/tutorial/hello available to use. cheers Adam [1] https://marc.info/?l=openbsd-ports&m=152960337514741&w=2
