568 940 java clock_gettime(0x1, 0xa7e5b6cc) = 0568 940 java clock_gettime(0x1, 0xa7e5b6bc) = 0568 940 java clock_gettime568 645 java clock_gettime(0x1, 0xa89d4ec8) = 0568 645 java futex(0xbac44328, 0x81, 0x1, 0xbac44328, 0, 0xa89d4ee8) = 0568 602 java clock_gettime(0x1, 0xb8aaf0b8) = 0568 602 java futex(0xbac2c428, 0x81, 0x1, 0xbac2c428, 0, 0xb8aaf0d8) = 0568 749 java clock_gettime(0x1, 0xa76fea18) = 0568 749 java clock_gettime(0x1, 0xa76feab0) = 0568 749 java futex(0x81632728, 0x81, 0x1, 0x8163728, 0, 0xa76fea38) = 0568 679 java clock_gettime(0x1, 0xa8904ea8) = 0568 679 java clock_gettime(0x1, 0xa8904f60) = 0This is the copied output from a screen capture (copied by hand) with ktruss -iI am runing NetBSD i386 under VirtualBox 5.2.6 r120293After 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).
= 0panic: SPL NOT LOWERED ON SYSCALL EXIT
cpu= Begin traceback....vpanic(c01006fd,db258fa8,
a7e5ab38,c01006ee,c01006fd, a7e500b3,a7ea0023,a7ea0023, 3d0023,a7d42c00) at netbsd:vpanic+0x121snprintf(c01006fd,a7e500b3, a7e500b3,a7ea0023,a7ea0023, 3d0023,a7d42c00,805aa400, a7e5ab38,65,a7e5aa98) at netbsd:snprintfcpu: End of traceback...dumping to dev 0,1 offset 2099624dump 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.
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?