Comment 1:

There was a question if this isolated to pandaboards, and I do not believe this is the
case,
I've run this loop on a pandaboard and you get after 10 minutes a failure
+ go test runtime -short -timeout=300s -cpu=1,2,4
runtime: newstack called from g=stress.bash: line 7:  9635 Segmentation fault      go
test runtime -short -timeout=300s -cpu=1,2,4
However, on a quad core imx6 machine the same test will result in 
+ go test runtime -short -timeout=300s -cpu=1,2,4
--- FAIL: TestCgoCrashHandler-2 (0.81s)
        crash_test.go:86: output:
                wanted:
                main: recovered done
                new-thread: recovered done
                second-new-thread: recovered done
                main-again: recovered done
FAIL
FAIL    runtime 101.198s
It is interesting to note that the pandaboard is a dual core host, and the imx6 fails
with -cpus=2

Comment 2:

Haven't seen this in a while. Assuming it's gone.

Status changed to TimedOut.