Re: Panic on evbearm6

2018-11-05 Thread Chavdar Ivanov
It might be interesting that the same panic happens when building go1.9 as well, although much later in the build sequence: bootstrap/cmd/link/internal/x86 bootstrap/cmd/link # Building go_bootstrap for host, netbsd/arm. runtime/internal/sys runtime/internal/atomic runtime encoding

Re: Panic on evbearm6

2018-11-05 Thread Michael van Elst
ci4...@gmail.com (Chavdar Ivanov) writes: >And there is another one on the same system from tonight: >--- >panic: kernel diagnostic assertion "(armreg_fpexc_read() & VFP_FPEXC_EN) >== 0" failed: file "/home/sysbuild/src/sys/arch/arm/vfp/vfp_init.c", Obviously a bug, but apparently a different

Re: Panic on evbearm6

2018-11-05 Thread Chavdar Ivanov
... and happens also with go 1.10 in the following stage: --- ===> Building for go110-1.10.4nb2 cd /usr/pkgsrc/lang/go110/work/go/src && env GOROOT_BOOTSTRAP=/usr/pkg/go14 GOROOT_FINAL=/usr/pkg/go110 GOARM=6 /usr/pkg/bin/bash ./make.bash Building Go cmd/dist using /usr/pkg/go14. Building Go

Re: Panic on evbearm6

2018-11-05 Thread Chavdar Ivanov
The above panic is repeatable. On Mon, 5 Nov 2018 at 10:14, Chavdar Ivanov wrote: > > > > On 11/04/18 17:03, Michael van Elst wrote: > > ci4...@gmail.com (Chavdar Ivanov) writes: > > > >> This was on the original RPI Zero, 512MB RAM (dmesg shows for some > >> reason total 448MB, avail 434MB). As

Re: Panic on evbearm6

2018-11-05 Thread Chavdar Ivanov
On 11/04/18 17:03, Michael van Elst wrote: ci4...@gmail.com (Chavdar Ivanov) writes: This was on the original RPI Zero, 512MB RAM (dmesg shows for some reason total 448MB, avail 434MB). As I said, it was running python3.7.1 tests at the time, so it may have been overloaded. It has only the

Re: Panic on evbearm6

2018-11-04 Thread Michael van Elst
ci4...@gmail.com (Chavdar Ivanov) writes: >This was on the original RPI Zero, 512MB RAM (dmesg shows for some >reason total 448MB, avail 434MB). As I said, it was running >python3.7.1 tests at the time, so it may have been overloaded. It has >only the default 256MB ld0b partition for swap. It's

Re: Panic on evbearm6

2018-11-04 Thread Chavdar Ivanov
This was on the original RPI Zero, 512MB RAM (dmesg shows for some reason total 448MB, avail 434MB). As I said, it was running python3.7.1 tests at the time, so it may have been overloaded. It has only the default 256MB ld0b partition for swap. On Sun, 4 Nov 2018 at 12:51, Nick Hudson wrote: > >

Re: Panic on evbearm6

2018-11-04 Thread Nick Hudson
On 04/11/2018 12:09, Chavdar Ivanov wrote: I just got: -- Nov 4 11:50:40 rpi /netbsd: [ 91750.0747877] panic: kernel diagnostic assertion "(flags & (PR_WAITOK|PR_NOWAIT)) == PR_NOWAIT" failed: file "/home/sysbuild/src/sys/kern/subr_pool.c", line 864 Nov 4 11:50:40 rpi /netbsd: [

Re: Panic on evbearm6

2018-11-04 Thread Michael van Elst
ci4...@gmail.com (Chavdar Ivanov) writes: >I just got: >-- >Nov 4 11:50:40 rpi /netbsd: [ 91750.0747877] panic: kernel diagnostic >assertion "(flags & (PR_WAITOK|PR_NOWAIT)) == PR_NOWAIT" failed: file >"/home/sysbuild/src/sys/kern/subr_pool.c", line 864 >Nov 4 11:50:40 rpi /netbsd:

Panic on evbearm6

2018-11-04 Thread Chavdar Ivanov
I just got: -- Nov 4 11:50:40 rpi /netbsd: [ 91750.0747877] panic: kernel diagnostic assertion "(flags & (PR_WAITOK|PR_NOWAIT)) == PR_NOWAIT" failed: file "/home/sysbuild/src/sys/kern/subr_pool.c", line 864 Nov 4 11:50:40 rpi /netbsd: [ 91750.0747877] cpu0: Begin traceback... Nov 4