Re: port-i386/53062: panic: SPL NOT LOWERED ON SYSCALL EXIT

[Jose Luis Rodriguez Garcia <joseyluis%gmail.com@localhost>]

The following reply was made to PR port-i386/53062; it has been noted by GNATS.

From: Jose Luis Rodriguez Garcia <joseyluis%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: port-i386-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
	netbsd-bugs%netbsd.org@localhost
Subject: Re: port-i386/53062: panic: SPL NOT LOWERED ON SYSCALL EXIT
Date: Wed, 7 Mar 2018 08:32:28 +0100

 --001a113ec948ba7cef0566cd8fbc
 Content-Type: text/plain; charset="UTF-8"
 
 With a kernel compiled with DEBUG and LOCKDEBUG I obtain this error from
 kernel (green color):
 execve_loadvm: check exec failed 8
 execve_loadvm: check exec failed 8
 execve_loadvm: check exec failed 8
 execve_loadvm: check exec failed 8
 
 It is just at beginning and several seconds before of the crash. I don't
 know if it can be related to the panic.
 
 On Fri, Mar 2, 2018 at 10:17 AM, Jose Luis Rodriguez Garcia <
 joseyluis%gmail.com@localhost> wrote:
 
 > I am runing NetBSD i386 under VirtualBox 5.2.6 r120293
 > After the system panics, if I don't power off the server on VirtualBox, I
 > can't reproduce the panic after the system reboot (altough I am not sure
 > that it works 100% reliable).
 >
 > This is the copied output from a screen capture (copied by hand) with
 > ktruss -i
 >
 > 568 679 java clock_gettime(0x1, 0xa8904f60) = 0
 > 568 679 java clock_gettime(0x1, 0xa8904ea8) = 0
 > 568 749 java futex(0x81632728, 0x81, 0x1, 0x8163728, 0, 0xa76fea38) = 0
 > 568 749 java clock_gettime(0x1, 0xa76feab0) = 0
 > 568 749 java clock_gettime(0x1, 0xa76fea18) = 0
 > 568 602 java futex(0xbac2c428, 0x81, 0x1, 0xbac2c428, 0, 0xb8aaf0d8) = 0
 > 568 602 java clock_gettime(0x1, 0xb8aaf0b8) = 0
 > 568 645 java futex(0xbac44328, 0x81, 0x1, 0xbac44328, 0, 0xa89d4ee8)  = 0
 > 568 645 java clock_gettime(0x1, 0xa89d4ec8) = 0
 > 568 940 java clock_gettime                          = 0
 > 568 940 java clock_gettime(0x1, 0xa7e5b6bc) = 0
 > 568 940 java clock_gettime(0x1, 0xa7e5b6cc) = 0
 > panic: SPL NOT LOWERED ON SYSCALL EXIT
 >
 > cpu= Begin traceback....
 > vpanic(c01006fd,db258fa8,a7e5ab38,c01006ee,c01006fd,
 > a7e500b3,a7ea0023,a7ea0023,3d0023,a7d42c00) at netbsd:vpanic+0x121
 > snprintf(c01006fd,a7e500b3,a7e500b3,a7ea0023,a7ea0023,
 > 3d0023,a7d42c00,805aa400,a7e5ab38,65,a7e5aa98) at netbsd:snprintf
 > cpu: End of traceback...
 > dumping to dev 0,1 offset 2099624
 > dump 69 68 67 66 65 64 63 62 61 60 59 58 57 ......
 >
 >
 >
 >
 >
 > On Thu, Mar 1, 2018 at 2:15 AM, <coypu%sdf.org@localhost> wrote:
 >
 >> The following reply was made to PR port-i386/53062; it has been noted by
 >> GNATS.
 >>
 >> From: coypu%sdf.org@localhost
 >> To: gnats-bugs%NetBSD.org@localhost
 >> Cc:
 >> Subject: Re: port-i386/53062: panic: SPL NOT LOWERED ON SYSCALL EXIT
 >> Date: Thu, 1 Mar 2018 01:10:41 +0000
 >>
 >>  I'm not sure what is happening from this backtrace.
 >>
 >>  Will you consider running ktruss -i on one of the parent linux
 >>  processes, outputting to stdout or a file, and seeing what the last
 >>  messages before a panic are?
 >>
 >>  Thanks.
 >>
 >>
 >
 
 --001a113ec948ba7cef0566cd8fbc
 Content-Type: text/html; charset="UTF-8"
 Content-Transfer-Encoding: quoted-printable
 
 <div dir=3D"ltr"><div><div>With a kernel compiled with DEBUG and LOCKDEBUG =
 I obtain this error from kernel (green color):<br></div>execve_loadvm: chec=
 k exec failed 8<br>
 execve_loadvm: check exec failed 8
 
 <br>
 execve_loadvm: check exec failed 8
 
 <br>
 execve_loadvm: check exec failed 8
 
 <br><br></div>It is just at beginning and several seconds before of the cra=
 sh. I don&#39;t know if it can be related to the panic.<br></div><div class=
 =3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Mar 2, 2018 at 10:1=
 7 AM, Jose Luis Rodriguez Garcia <span dir=3D"ltr">&lt;<a href=3D"mailto:jo=
 seyluis%gmail.com@localhost" target=3D"_blank">joseyluis%gmail.com@localhost</a>&gt;</span> wro=
 te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
 left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><div><div>=
 <div><div><div><div><div><div><div><div><div><div>I am runing NetBSD i386 u=
 nder VirtualBox 5.2.6 r120293<br></div>After the system panics, if I don&#3=
 9;t power off the server on VirtualBox, I can&#39;t reproduce the panic aft=
 er the system reboot (altough I am not sure that it works 100% reliable).<b=
 r><br></div>This is the copied output from a screen capture (copied by hand=
 ) with ktruss -i<br><br></div>568 679 java clock_gettime(0x1, 0xa8904f60) =
 =3D 0<br></div>568 679 java clock_gettime(0x1, 0xa8904ea8) =3D 0<br></div>5=
 68 749 java futex(0x81632728, 0x81, 0x1, 0x8163728, 0, 0xa76fea38) =3D 0<br=
 ></div>568 749 java clock_gettime(0x1, 0xa76feab0) =3D 0<br></div>568 749 j=
 ava clock_gettime(0x1, 0xa76fea18) =3D 0<br></div>568 602 java futex(0xbac2=
 c428, 0x81, 0x1, 0xbac2c428, 0, 0xb8aaf0d8) =3D 0<br></div>568 602 java clo=
 ck_gettime(0x1, 0xb8aaf0b8) =3D 0<br></div>568 645 java futex(0xbac44328, 0=
 x81, 0x1, 0xbac44328, 0, 0xa89d4ee8)=C2=A0 =3D 0<br></div>568 645 java cloc=
 k_gettime(0x1, 0xa89d4ec8) =3D 0<br></div>568 940 java clock_gettime=C2=A0=
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
 =A0=C2=A0=C2=A0=C2=A0<wbr>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
 =3D 0<br></div>568 940 java clock_gettime(0x1, 0xa7e5b6bc) =3D 0<br></div>5=
 68 940 java clock_gettime(0x1, 0xa7e5b6cc) =3D 0<br><div><div><span class=
 =3D""><div>panic: SPL NOT LOWERED ON SYSCALL EXIT<br></div></span><div><br>=
 cpu=3D Begin traceback....<br></div><div><div><div><div><div><div><div><div=
 ><div><div><div><div><div><div>vpanic(c01006fd,db258fa8,<wbr>a7e5ab38,c0100=
 6ee,c01006fd,<wbr>a7e500b3,a7ea0023,a7ea0023,<wbr>3d0023,a7d42c00) at netbs=
 d:vpanic+0x121<br></div><div>snprintf(c01006fd,a7e500b3,<wbr>a7e500b3,a7ea0=
 023,a7ea0023,<wbr>3d0023,a7d42c00,805aa400,<wbr>a7e5ab38,65,a7e5aa98) at ne=
 tbsd:snprintf<br></div><div>cpu: End of traceback...<br></div><div>dumping =
 to dev 0,1 offset 2099624<br></div><div>dump 69 68 67 66 65 64 63 62 61 60 =
 59 58 57 ......<br></div><div><br><br><br><br></div></div></div></div></div=
 ></div></div></div></div></div></div></div></div></div></div></div></div><d=
 iv class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><div c=
 lass=3D"gmail_quote">On Thu, Mar 1, 2018 at 2:15 AM,  <span dir=3D"ltr">&lt=
 ;<a href=3D"mailto:coypu%sdf.org@localhost"; target=3D"_blank">coypu%sdf.org@localhost</a>&gt;</=
 span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
 x;border-left:1px #ccc solid;padding-left:1ex">The following reply was made=
  to PR port-i386/53062; it has been noted by GNATS.<br>
 <br>
 From: <a href=3D"mailto:coypu%sdf.org@localhost"; target=3D"_blank">coypu%sdf.org@localhost</a><=
 br>
 To: gnats-bugs%NetBSD.org@localhost<br>
 Cc:<br>
 Subject: Re: port-i386/53062: panic: SPL NOT LOWERED ON SYSCALL EXIT<br>
 Date: Thu, 1 Mar 2018 01:10:41 +0000<br>
 <br>
 =C2=A0I&#39;m not sure what is happening from this backtrace.<br>
 <br>
 =C2=A0Will you consider running ktruss -i on one of the parent linux<br>
 =C2=A0processes, outputting to stdout or a file, and seeing what the last<b=
 r>
 =C2=A0messages before a panic are?<br>
 <br>
 =C2=A0Thanks.<br>
 <br>
 </blockquote></div><br></div>
 </div></div></blockquote></div><br></div>
 
 --001a113ec948ba7cef0566cd8fbc--