Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

runtime: "unexpected signal during runtime execution" during bgscavenge on plan9 #35456

Open
bcmills opened this issue Nov 8, 2019 · 49 comments
Open

runtime: "unexpected signal during runtime execution" during bgscavenge on plan9 #35456

bcmills opened this issue Nov 8, 2019 · 49 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. help wanted NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Plan9
Milestone
Unplanned

Comments

@bcmills
Copy link
Contributor

bcmills commented Nov 8, 2019 •
edited 

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`

From plan9-386-0intro (https://build.golang.org/log/a94f5d80b1a5d38ecdf8b02bed7bfb305f569118), a cmd/vet test failure that appears to have nothing to do with cmd/vet:

--- FAIL: TestVet (1.94s)
    --- FAIL: TestVet/assign (0.43s)
        vet_test.go:162: error check failed: 
            assign.go:18: missing error "self-assignment of x to x"
            assign.go:20: missing error "self-assignment of s.x to s.x"
            assign.go:22: missing error "self-assignment of s.l.0. to s.l.0."
            Unmatched Errors:
            fatal error: unexpected signal during runtime execution
            [signal sys: trap: fault write code=0x0 addr=0x0 pc=0xa960]
            goroutine 4 [running]:
            runtime.throw(0x96394d, 0x2a)
            	/tmp/workdir-gnot/go/src/runtime/panic.go:1106 +0x63 fp=0x11429f44 sp=0x11429f30 pc=0x2e783
            runtime.sigpanic()
            	/tmp/workdir-gnot/go/src/runtime/os_plan9.go:79 +0x333 fp=0x11429f78 sp=0x11429f44 pc=0x2b033
            runtime.newobject(0x92d1a0, 0x0)
            	/tmp/workdir-gnot/go/src/runtime/malloc.go:1153 fp=0x11429f7c sp=0x11429f78 pc=0xa960
            runtime.bgscavenge(0x1143c000)
            	/tmp/workdir-gnot/go/src/runtime/mgcscavenge.go:211 +0x5b fp=0x11429fe8 sp=0x11429f7c pc=0x1d83b
            runtime.goexit()
            	/tmp/workdir-gnot/go/src/runtime/asm_386.s:1337 +0x1 fp=0x11429fec sp=0x11429fe8 pc=0x573f1
            created by runtime.gcenable
            	/tmp/workdir-gnot/go/src/runtime/mgc.go:215 +0x6a
            goroutine 1 [chan receive, locked to thread]:
            runtime.gopark(0x96ee48, 0x1143c030, 0x1143170e, 0x2)
            	/tmp/workdir-gnot/go/src/runtime/proc.go:304 +0xd8
            runtime.chanrecv(0x1143c000, 0x0, 0x11400001, 0x1515a)
            	/tmp/workdir-gnot/go/src/runtime/chan.go:563 +0x275
            runtime.chanrecv1(0x1143c000, 0x0)
            	/tmp/workdir-gnot/go/src/runtime/chan.go:433 +0x1c
            runtime.gcenable()
            	/tmp/workdir-gnot/go/src/runtime/mgc.go:216 +0x7e
            runtime.main()
            	/tmp/workdir-gnot/go/src/runtime/proc.go:166 +0x183
            runtime.goexit()
            	/tmp/workdir-gnot/go/src/runtime/asm_386.s:1337 +0x1
FAIL
FAIL	cmd/vet	34.760s

CC @aclements @mknyszek @0intro @fhs
@bcmills bcmills added help wanted OS-Plan9 NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Nov 8, 2019
@bcmills bcmills added this to the Unplanned milestone Nov 8, 2019
@mknyszek
Copy link
Contributor

mknyszek commented Nov 8, 2019

This is very odd. It's failing very, very early in the runtime (right when the background scavenger is spinning up) trying to allocate a timer. And the problem seems to be that newobject has a nil type parameter? I'm not even sure how that can happen.

@ianlancetaylor
Copy link
Contributor

The type parameter passed to newobject is 0x92d1a0. The 0x0 is the result parameter. The addr=0x0 printed at the start of the backtrace is meaningless, as this is not a fault signal, it is a trap signal. The trap signal does not set the address field (sigcode1) on Plan 9.

But that said I have no idea why the binary would get a trap signal. I don't know enough about Plan 9 to know what might cause that. If this happened only once I'm inclined to ignore it.

CC @0intro

@fhs
Copy link
Contributor

fhs commented Nov 22, 2019

Not sure if this is related, but cmd/vet crashed from a trap signal in a trybot run:

fatal error: sys: trap: general protection violation pc=0x00200393
[signal sys: trap: code=0x0 addr=0x0 pc=0x200393]

goroutine 1 [running]:
runtime.throw(0x10812000, 0x35)
	/tmp/workdir-gnot/go/src/runtime/panic.go:1106 +0x63 fp=0x108a1498 sp=0x108a1484 pc=0x2da03
runtime.sigpanic()
	/tmp/workdir-gnot/go/src/runtime/os_plan9.go:104 +0x289 fp=0x108a14cc sp=0x108a1498 pc=0x2a3a9
go/internal/gcimporter.(*importReader).declare(0x108a5b40, 0x338e40, 0x108d9140)
	/tmp/workdir-gnot/go/src/go/internal/gcimporter/iimport.go:310 +0x43 fp=0x108a14e4 sp=0x108a14cc pc=0x200393
go/internal/gcimporter.(*importReader).obj(0x108a5b40, 0x10821ff4, 0x4)
	/tmp/workdir-gnot/go/src/go/internal/gcimporter/iimport.go:270 +0x796 fp=0x108a1580 sp=0x108a14e4 pc=0x200136
go/internal/gcimporter.(*iimporter).doDecl(0x10862500, 0x108d9020, 0x10821ff4, 0x4)
	/tmp/workdir-gnot/go/src/go/internal/gcimporter/iimport.go:202 +0x160 fp=0x108a15c8 sp=0x108a1580 pc=0x1ff1f0
go/internal/gcimporter.iImportData(0x10851410, 0x108dfce0, 0x109e0001, 0x4ff96, 0x7fdff, 0x1085e820, 0x14, 0x0, 0x0, 0x0, ...)
	/tmp/workdir-gnot/go/src/go/internal/gcimporter/iimport.go:153 +0xb5f fp=0x108a1788 sp=0x108a15c8 pc=0x1fec0f
go/internal/gcimporter.Import(0x10851410, 0x108dfce0, 0x1085e820, 0x14, 0x0, 0x0, 0x108dabc0, 0x0, 0x0, 0x0)
	/tmp/workdir-gnot/go/src/go/internal/gcimporter/gcimporter.go:159 +0x421 fp=0x108a188c sp=0x108a1788 pc=0x1fda21
go/importer.(*gcimports).ImportFrom(0x108e17f0, 0x1085e820, 0x14, 0x0, 0x0, 0x0, 0x8c, 0x1085c630, 0x4e9324)
	/tmp/workdir-gnot/go/src/go/importer/importer.go:102 +0x58 fp=0x108a18b8 sp=0x108a188c pc=0x205008
go/importer.(*gcimports).Import(0x108e17f0, 0x1085e820, 0x14, 0x14, 0x1085c680, 0x291401)
	/tmp/workdir-gnot/go/src/go/importer/importer.go:95 +0x48 fp=0x108a18e0 sp=0x108a18b8 pc=0x204f88
cmd/vendor/golang.org/x/tools/go/analysis/unitchecker.run.func2(0x1085e941, 0x14, 0x290cc0, 0x52d201, 0x0)
	/tmp/workdir-gnot/go/src/cmd/vendor/golang.org/x/tools/go/analysis/unitchecker/unitchecker.go:221 +0x78 fp=0x108a1910 sp=0x108a18e0 pc=0x214748
cmd/vendor/golang.org/x/tools/go/analysis/unitchecker.importerFunc.Import(0x108e1800, 0x1085e941, 0x14, 0x0, 0x0, 0xb4f00)
	/tmp/workdir-gnot/go/src/cmd/vendor/golang.org/x/tools/go/analysis/unitchecker/unitchecker.go:396 +0x2b fp=0x108a1928 sp=0x108a1910 pc=0x21437b
go/types.(*Checker).importPackage(0x1085c7e0, 0x8b4, 0x1085e941, 0x14, 0x10860210, 0x20, 0x0)
	/tmp/workdir-gnot/go/src/go/types/resolver.go:158 +0x48e fp=0x108a1998 sp=0x108a1928 pc=0x1cf0ae
go/types.(*Checker).collectObjects(0x1085c7e0)
	/tmp/workdir-gnot/go/src/go/types/resolver.go:253 +0x383 fp=0x108a1cc4 sp=0x108a1998 pc=0x1cf573
go/types.(*Checker).checkFiles(0x1085c7e0, 0x108dabb8, 0x1, 0x2, 0x0, 0x0)
	/tmp/workdir-gnot/go/src/go/types/check.go:253 +0x89 fp=0x108a1ce8 sp=0x108a1cc4 pc=0x1b72d9
go/types.(*Checker).Files(...)
	/tmp/workdir-gnot/go/src/go/types/check.go:246
go/types.(*Config).Check(0x108dfd00, 0x10820bc2, 0x7, 0x10851410, 0x108dabb8, 0x1, 0x2, 0x108d8a20, 0x0, 0x1087cae0, ...)
	/tmp/workdir-gnot/go/src/go/types/api.go:348 +0xf4 fp=0x108a1d1c sp=0x108a1ce8 pc=0x1adab4
cmd/vendor/golang.org/x/tools/go/analysis/unitchecker.run(0x10851410, 0x1087ca80, 0x10880500, 0x15, 0x20, 0x108a1e40, 0x1082089c, 0x108a1de8, 0x108ac020, 0x2cb0bc)
	/tmp/workdir-gnot/go/src/cmd/vendor/golang.org/x/tools/go/analysis/unitchecker/unitchecker.go:235 +0x3e7 fp=0x108a1df0 sp=0x108a1d1c pc=0x213bb7
cmd/vendor/golang.org/x/tools/go/analysis/unitchecker.Run(0xdfffef94, 0x23, 0x10880500, 0x15, 0x20)
	/tmp/workdir-gnot/go/src/cmd/vendor/golang.org/x/tools/go/analysis/unitchecker/unitchecker.go:131 +0xd8 fp=0x108a1f54 sp=0x108a1df0 pc=0x213288
cmd/vendor/golang.org/x/tools/go/analysis/unitchecker.Main(0x10880500, 0x15, 0x20)
	/tmp/workdir-gnot/go/src/cmd/vendor/golang.org/x/tools/go/analysis/unitchecker/unitchecker.go:118 +0x1ed fp=0x108a1f98 sp=0x108a1f54 pc=0x21302d
main.main()
	/tmp/workdir-gnot/go/src/cmd/vet/main.go:35 +0x276 fp=0x108a1fb8 sp=0x108a1f98 pc=0x24f726
runtime.main()
	/tmp/workdir-gnot/go/src/runtime/proc.go:203 +0x261 fp=0x108a1ff0 sp=0x108a1fb8 pc=0x2fe71
runtime.goexit()
	/tmp/workdir-gnot/go/src/runtime/asm_386.s:1337 +0x1 fp=0x108a1ff4 sp=0x108a1ff0 pc=0x53601

@gopherbot
Copy link

Change https://golang.org/cl/233797 mentions this issue: dashboard: change "plan9" SlowBot alias to refer to plan9-arm

gopherbot pushed a commit to golang/build that referenced this issue May 13, 2020
dashboard: change "plan9" SlowBot alias to refer to plan9-arm
033b1e5 
The plan9-arm builder is currently passing fairly reliably on the
dashboard, whereas the plan9-386-0intro builder is frequently failing
with an "unexpected fault address".

Until the plan9-386-0intro build is fixed, the plan9-arm builder seems
more useful as a SlowBot to check architecture-agnostic changes that
affect plan9.

Updates golang/go#35456
Updates golang/go#22227

Change-Id: Ib5ecddafec91ca9274f9f0e15cb98621b41dda85
Reviewed-on: https://go-review.googlesource.com/c/build/+/233797
Run-TryBot: Bryan C. Mills <bcmills@google.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
@bcmills bcmills mentioned this issue Nov 19, 2021
Open
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 7, 2022
@rsc rsc mentioned this issue Mar 15, 2023
Closed
@bcmills bcmills added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Mar 16, 2023
@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-01-19 20:44 plan9-arm go@3bb8864e (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0xd2c0]

runtime stack:
runtime.throw({0x43be80, 0x2a})
	/boot/workdir/go/src/runtime/panic.go:1047 +0x4c fp=0x3ffffc80 sp=0x3ffffc6c pc=0x3b840
runtime.sigpanic()
	/boot/workdir/go/src/runtime/os_plan9.go:80 +0x4e8 fp=0x3ffffcc0 sp=0x3ffffc80 pc=0x37510
runtime.nextFreeFast(...)
	/boot/workdir/go/src/runtime/malloc.go:819
runtime.mallocgc(0x21c, 0x423210, 0x1)
	/boot/workdir/go/src/runtime/malloc.go:1040 +0x494 fp=0x3ffffcfc sp=0x3ffffcc4 pc=0xd2c0
runtime.newobject(0x423210)
	/boot/workdir/go/src/runtime/malloc.go:1254 +0x2c fp=0x3ffffd10 sp=0x3ffffcfc pc=0xda48
runtime.allocm(0x903a600, 0x468d88, 0xc)
	/boot/workdir/go/src/runtime/proc.go:1831 +0x9c fp=0x3ffffd3c sp=0x3ffffd10 pc=0x42308
runtime.newm(0x468d88, 0x903a600, 0xc)
	/boot/workdir/go/src/runtime/proc.go:2196 +0x4c fp=0x3ffffd54 sp=0x3ffffd3c pc=0x429e8
runtime.startm(0x903a600, 0x1)
	/boot/workdir/go/src/runtime/proc.go:2411 +0x110 fp=0x3ffffd80 sp=0x3ffffd54 pc=0x42fbc
runtime.wakep()
	/boot/workdir/go/src/runtime/proc.go:2541 +0xcc fp=0x3ffffda0 sp=0x3ffffd80 pc=0x43650
runtime.resetspinning()
	/boot/workdir/go/src/runtime/proc.go:3244 +0x50 fp=0x3ffffdb0 sp=0x3ffffda0 pc=0x457c8
runtime.schedule()
	/boot/workdir/go/src/runtime/proc.go:3366 +0xd8 fp=0x3ffffdcc sp=0x3ffffdb0 pc=0x45d94
runtime.park_m(0x90032c0)
	/boot/workdir/go/src/runtime/proc.go:3511 +0x150 fp=0x3ffffde0 sp=0x3ffffdcc pc=0x46558
runtime.mcall()
	/boot/workdir/go/src/runtime/asm_arm.s:265 +0x48 fp=0x3ffffde8 sp=0x3ffffde0 pc=0x697e0

— watchflakes

@bcmills bcmills removed the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Mar 16, 2023
@bcmills bcmills changed the title runtime: "unexpected signal during runtime execution" during bgscavenge on plan9-386-0intro runtime: "unexpected signal during runtime execution" during bgscavenge on plan9 Mar 16, 2023
@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-03-07 14:28 plan9-arm benchmarks@2652dad2 go@d49b11be (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x163fc]

runtime stack:
runtime.throw({0x63fa08, 0x2a})
	runtime/panic.go:1076 +0x4c fp=0x3ffffab8 sp=0x3ffffaa4 pc=0x3bf44
runtime.sigpanic()
	runtime/os_plan9.go:80 +0x4c0 fp=0x3ffffaf8 sp=0x3ffffab8 pc=0x37cf8
runtime.(*mcache).prepareForSweep(0x0)
	runtime/mcache.go:321 +0x14 fp=0x3ffffb14 sp=0x3ffffafc pc=0x163fc
runtime.acquirep(0x9433900)
	runtime/proc.go:5153 +0x2c fp=0x3ffffb34 sp=0x3ffffb14 pc=0x4a44c
runtime.stopm()
	runtime/proc.go:2392 +0xb0 fp=0x3ffffb48 sp=0x3ffffb34 pc=0x432ec
runtime.findRunnable()
	runtime/proc.go:3064 +0xd4c fp=0x3ffffbe8 sp=0x3ffffb48 pc=0x44e18
runtime.schedule()
	runtime/proc.go:3417 +0xac fp=0x3ffffc04 sp=0x3ffffbe8 pc=0x46118
runtime.park_m(0x95d4900)
	runtime/proc.go:3568 +0x14c fp=0x3ffffc18 sp=0x3ffffc04 pc=0x46908
runtime.mcall()
	runtime/asm_arm.s:265 +0x48 fp=0x3ffffc20 sp=0x3ffffc18 pc=0x6ee50

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-03-28 14:28 plan9-arm go@abf9b112 (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x163fc]

runtime stack:
runtime.throw({0x63fa08, 0x2a})
	runtime/panic.go:1076 +0x4c fp=0x3ffffd94 sp=0x3ffffd80 pc=0x3bf44
runtime.sigpanic()
	runtime/os_plan9.go:80 +0x4c0 fp=0x3ffffdd4 sp=0x3ffffd94 pc=0x37cf8
runtime.(*mcache).prepareForSweep(0x0)
	runtime/mcache.go:321 +0x14 fp=0x3ffffdf0 sp=0x3ffffdd8 pc=0x163fc
runtime.acquirep(0x9437900)
	runtime/proc.go:5153 +0x2c fp=0x3ffffe10 sp=0x3ffffdf0 pc=0x4a44c
runtime.stopm()
	runtime/proc.go:2392 +0xb0 fp=0x3ffffe24 sp=0x3ffffe10 pc=0x432ec
runtime.findRunnable()
	runtime/proc.go:3064 +0xd4c fp=0x3ffffec4 sp=0x3ffffe24 pc=0x44e18
runtime.schedule()
	runtime/proc.go:3417 +0xac fp=0x3ffffee0 sp=0x3ffffec4 pc=0x46118
runtime.park_m(0x9402900)
	runtime/proc.go:3568 +0x14c fp=0x3ffffef4 sp=0x3ffffee0 pc=0x46908
runtime.mcall()
	runtime/asm_arm.s:265 +0x48 fp=0x3ffffefc sp=0x3ffffef4 pc=0x6ee50

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-04-06 15:43 plan9-arm image@ed5dba0e go@c6306612 (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x45080]

runtime stack:
runtime.throw({0x64a633, 0x2a})
	runtime/panic.go:1077 +0x4c fp=0x3ffffc2c sp=0x3ffffc18 pc=0x3cb64
runtime.sigpanic()
	runtime/os_plan9.go:80 +0x4c0 fp=0x3ffffc6c sp=0x3ffffc2c pc=0x38920
runtime.findRunnable()
	runtime/proc.go:2834 +0x248 fp=0x3ffffd10 sp=0x3ffffc70 pc=0x45080
runtime.schedule()
	runtime/proc.go:3462 +0xac fp=0x3ffffd2c sp=0x3ffffd10 pc=0x46e84
runtime.park_m(0x9402900)
	runtime/proc.go:3613 +0x14c fp=0x3ffffd40 sp=0x3ffffd2c pc=0x47674
runtime.mcall()
	runtime/asm_arm.s:265 +0x48 fp=0x3ffffd48 sp=0x3ffffd40 pc=0x700c8

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-05-11 19:07 plan9-arm go@a2737b1a (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x4645c]

runtime stack:
runtime.throw({0x488444, 0x2a})
	/boot/workdir/go/src/runtime/panic.go:1077 +0x4c fp=0x3ffffbec sp=0x3ffffbd8 pc=0x3fce4
runtime.sigpanic()
	/boot/workdir/go/src/runtime/os_plan9.go:80 +0x4c0 fp=0x3ffffc2c sp=0x3ffffbec pc=0x3bc14
runtime.runSafePointFn()
	/boot/workdir/go/src/runtime/proc.go:1763 +0x50 fp=0x3ffffc48 sp=0x3ffffc30 pc=0x4645c
runtime.findRunnable()
	/boot/workdir/go/src/runtime/proc.go:2740 +0x6c fp=0x3ffffce8 sp=0x3ffffc48 pc=0x47f90
runtime.schedule()
	/boot/workdir/go/src/runtime/proc.go:3414 +0xac fp=0x3ffffd04 sp=0x3ffffce8 pc=0x49f70
runtime.park_m(0x9002900)
	/boot/workdir/go/src/runtime/proc.go:3565 +0x14c fp=0x3ffffd18 sp=0x3ffffd04 pc=0x4a760
runtime.mcall()
	/boot/workdir/go/src/runtime/asm_arm.s:265 +0x48 fp=0x3ffffd20 sp=0x3ffffd18 pc=0x73348

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-05-16 16:00 plan9-arm sys@352d8339 go@7b0835d4 (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x48e0c]

runtime stack:
runtime.throw({0x6698cd, 0x2a})
	runtime/panic.go:1077 +0x4c fp=0x3ffffc24 sp=0x3ffffc10 pc=0x40918
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4c0 fp=0x3ffffc64 sp=0x3ffffc24 pc=0x3c6fc
runtime.findRunnable()
	runtime/proc.go:2866 +0x23c fp=0x3ffffd08 sp=0x3ffffc68 pc=0x48e0c
runtime.schedule()
	runtime/proc.go:3494 +0xac fp=0x3ffffd24 sp=0x3ffffd08 pc=0x4ac1c
runtime.park_m(0x998a500)
	runtime/proc.go:3645 +0x160 fp=0x3ffffd40 sp=0x3ffffd24 pc=0x4b42c
runtime.mcall()
	runtime/asm_arm.s:265 +0x48 fp=0x3ffffd48 sp=0x3ffffd40 pc=0x74778

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-07-20 19:30 plan9-arm go@3ffc8a25 (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x1a0ac]

runtime stack:
runtime.throw({0x4a30d4, 0x2a})
	/boot/workdir/go/src/runtime/panic.go:1077 +0x4c fp=0x3ffffc8c sp=0x3ffffc78 pc=0x40c68
runtime.sigpanic()
	/boot/workdir/go/src/runtime/os_plan9.go:75 +0x4d4 fp=0x3ffffccc sp=0x3ffffc8c pc=0x3cb08
runtime.(*mcache).prepareForSweep(0x0)
	/boot/workdir/go/src/runtime/mcache.go:321 +0x14 fp=0x3ffffce8 sp=0x3ffffcd0 pc=0x1a0ac
runtime.acquirep(0x9039900)
	/boot/workdir/go/src/runtime/proc.go:5339 +0x2c fp=0x3ffffd08 sp=0x3ffffce8 pc=0x4f5fc
runtime.stopm()
	/boot/workdir/go/src/runtime/proc.go:2538 +0xb4 fp=0x3ffffd1c sp=0x3ffffd08 pc=0x48398
runtime.findRunnable()
	/boot/workdir/go/src/runtime/proc.go:3233 +0xd58 fp=0x3ffffdc4 sp=0x3ffffd1c pc=0x49f40
runtime.schedule()
	/boot/workdir/go/src/runtime/proc.go:3587 +0xac fp=0x3ffffde0 sp=0x3ffffdc4 pc=0x4b128
runtime.park_m(0x9202d00)
	/boot/workdir/go/src/runtime/proc.go:3750 +0x160 fp=0x3ffffdfc sp=0x3ffffde0 pc=0x4b9b4
runtime.mcall()
	/boot/workdir/go/src/runtime/asm_arm.s:265 +0x48 fp=0x3ffffe04 sp=0x3ffffdfc pc=0x74f78

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-07-31 18:04 plan9-arm go@24af43fa (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x49408]

runtime stack:
runtime.throw({0x68f521, 0x2a})
	runtime/panic.go:837 +0x4c fp=0x3ffffba0 sp=0x3ffffb8c pc=0x40b9c
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d4 fp=0x3ffffbe0 sp=0x3ffffba0 pc=0x3cfa0
runtime.findRunnable()
	runtime/proc.go:2953 +0x240 fp=0x3ffffc94 sp=0x3ffffbe4 pc=0x49408
runtime.schedule()
	runtime/proc.go:3605 +0xac fp=0x3ffffcb0 sp=0x3ffffc94 pc=0x4b1e0
runtime.park_m(0x9402800)
	runtime/proc.go:3768 +0x160 fp=0x3ffffccc sp=0x3ffffcb0 pc=0x4ba6c
runtime.mcall()
	runtime/asm_arm.s:265 +0x48 fp=0x3ffffcd4 sp=0x3ffffccc pc=0x74ef0

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-08-07 12:58 plan9-arm tools@2dc7ebab go@009c628b x/tools/gopls/internal/lsp/analysis/deprecated.Test (log) 
--- FAIL: Test (12.16s)
    analysistest.go:292: loading [a]: err: exit status: 'go 18728: 2': stderr: fatal error: unexpected signal during runtime execution
        [signal sys: trap: fault read code=0x0 addr=0x0 pc=0x3b39c]

        runtime stack:
        runtime.throw({0x68ec49, 0x2a})
        	runtime/panic.go:845 +0x4c fp=0x3ffffa74 sp=0x3ffffa60 pc=0x40bbc
        runtime.sigpanic()
        	runtime/os_plan9.go:75 +0x4d4 fp=0x3ffffab4 sp=0x3ffffa74 pc=0x3cf74
        runtime.(*spanSet).push(0xa69bc0, 0x9389d70)
...
        runtime.gcMarkTermination()
        	runtime/mgc.go:1101 +0x6f8 fp=0x9905f4c sp=0x9905da0 pc=0x20368
        runtime.gcMarkDone()
        	runtime/mgc.go:941 +0x2fc fp=0x9905f80 sp=0x9905f4c pc=0x1fb28
        runtime.gcBgMarkWorker()
        	runtime/mgc.go:1445 +0x3e8 fp=0x9905fec sp=0x9905f80 pc=0x21614
        runtime.goexit()
        	runtime/asm_arm.s:859 +0x4 fp=0x9905fec sp=0x9905fec pc=0x76a5c
        created by runtime.gcBgMarkStartWorkers in goroutine 1
        	runtime/mgc.go:1237 +0x20

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-08-04 16:57 plan9-arm crypto@b4ddeeda go@6e434079 (log)

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-08-16 16:38 plan9-arm go@9049d77d (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0xe54c]

goroutine 718 [running]:
runtime.throw({0x688394, 0x2a})
	runtime/panic.go:859 +0x4c fp=0x96ef38c sp=0x96ef378 pc=0x410a0
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d4 fp=0x96ef3cc sp=0x96ef38c pc=0x3d434
runtime.lock2(0x6a)
	runtime/lock_sema.go:46 +0x30 fp=0x96ef3f8 sp=0x96ef3d0 pc=0xe54c
...
cmd/go/internal/work.ActorFunc.Act(0x6bfaa0, 0x9812c40, {0x766770, 0xa69fc0}, 0x983b8c0)
	cmd/go/internal/work/action.go:78 +0x3c fp=0x96efe70 sp=0x96efe54 pc=0x5116a0
cmd/go/internal/work.(*Builder).Do.func3({0x766770, 0xa69fc0}, 0x983b8c0)
	cmd/go/internal/work/exec.go:151 +0x764 fp=0x96eff84 sp=0x96efe70 pc=0x5217f8
cmd/go/internal/work.(*Builder).Do.func4()
	cmd/go/internal/work/exec.go:219 +0xcc fp=0x96effec sp=0x96eff84 pc=0x520f08
runtime.goexit()
	runtime/asm_arm.s:859 +0x4 fp=0x96effec sp=0x96effec pc=0x77148
created by cmd/go/internal/work.(*Builder).Do in goroutine 1
	cmd/go/internal/work/exec.go:205 +0x3a8

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-08-17 21:51 plan9-arm go@639f6f7e (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x3b85c]

goroutine 603 [running]:
runtime.throw({0x689d3c, 0x2a})
	runtime/panic.go:1018 +0x4c fp=0x966bb44 sp=0x966bb30 pc=0x41224
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d4 fp=0x966bb84 sp=0x966bb44 pc=0x3d434
runtime.(*spanSet).push(0xa60d08, 0xa822d8)
	runtime/mspanset.go:136 +0x228 fp=0x966bbc8 sp=0x966bb88 pc=0x3b85c
...
cmd/go/internal/work.ActorFunc.Act(0x6c1474, 0x967e460, {0x768ae0, 0xa6cfc0}, 0x967b200)
	cmd/go/internal/work/action.go:78 +0x3c fp=0x966be70 sp=0x966be54 pc=0x513024
cmd/go/internal/work.(*Builder).Do.func3({0x768ae0, 0xa6cfc0}, 0x967b200)
	cmd/go/internal/work/exec.go:151 +0x764 fp=0x966bf84 sp=0x966be70 pc=0x523184
cmd/go/internal/work.(*Builder).Do.func4()
	cmd/go/internal/work/exec.go:219 +0xcc fp=0x966bfec sp=0x966bf84 pc=0x52288c
runtime.goexit()
	runtime/asm_arm.s:859 +0x4 fp=0x966bfec sp=0x966bfec pc=0x773b0
created by cmd/go/internal/work.(*Builder).Do in goroutine 1
	cmd/go/internal/work/exec.go:205 +0x3a8

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-08-21 18:18 plan9-arm arch@b6e87532 go@05f95115 (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x4bb74]

runtime stack:
runtime.throw({0x689c39, 0x2a})
	runtime/panic.go:1018 +0x4c fp=0x3ffffa94 sp=0x3ffffa80 pc=0x41218
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d4 fp=0x3ffffad4 sp=0x3ffffa94 pc=0x3d42c
runtime.schedule()
	runtime/proc.go:3645 +0x2a4 fp=0x3ffffaf4 sp=0x3ffffad8 pc=0x4bb74
runtime.park_m(0x9ac3a00)
	runtime/proc.go:3765 +0x160 fp=0x3ffffb10 sp=0x3ffffaf4 pc=0x4c208
runtime.mcall()
	runtime/asm_arm.s:265 +0x48 fp=0x3ffffb18 sp=0x3ffffb10 pc=0x757dc

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-08-04 16:57 plan9-arm crypto@b4ddeeda go@56b3b244 (log)

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-08-25 15:10 plan9-arm go@882a356e (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x15bc0]

runtime stack:
runtime.throw({0x15cc18, 0x2a})
	/boot/workdir/go1.4/src/runtime/panic.go:1047 +0x4c fp=0x3ffffce0 sp=0x3ffffccc pc=0x3927c
runtime.sigpanic()
	/boot/workdir/go1.4/src/runtime/os_plan9.go:80 +0x4e8 fp=0x3ffffd20 sp=0x3ffffce0 pc=0x352dc
runtime.(*mcache).prepareForSweep(0x0)
	/boot/workdir/go1.4/src/runtime/mcache.go:321 +0x14 fp=0x3ffffd3c sp=0x3ffffd24 pc=0x15bc0
runtime.acquirep(0x8c32000)
	/boot/workdir/go1.4/src/runtime/proc.go:5115 +0x2c fp=0x3ffffd44 sp=0x3ffffd3c pc=0x4743c
runtime.stopm()
	/boot/workdir/go1.4/src/runtime/proc.go:2336 +0xb0 fp=0x3ffffd58 sp=0x3ffffd44 pc=0x40394
runtime.findRunnable()
	/boot/workdir/go1.4/src/runtime/proc.go:3025 +0xd44 fp=0x3ffffdf8 sp=0x3ffffd58 pc=0x41f04
runtime.schedule()
	/boot/workdir/go1.4/src/runtime/proc.go:3378 +0xac fp=0x3ffffe14 sp=0x3ffffdf8 pc=0x431fc
runtime.park_m(0x8c02b40)
	/boot/workdir/go1.4/src/runtime/proc.go:3529 +0x150 fp=0x3ffffe28 sp=0x3ffffe14 pc=0x439ec
runtime.mcall()
	/boot/workdir/go1.4/src/runtime/asm_arm.s:265 +0x48 fp=0x3ffffe30 sp=0x3ffffe28 pc=0x6664c

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-09-15 20:17 plan9-arm tools@866a6b0f go@c05fceb7 x/tools/go/analysis/passes/lostcancel.Test (log) 
--- FAIL: Test (11.33s)
    analysistest.go:319: loading [a b typeparams]: err: exit status: 'go 12268: 2': stderr: fatal error: unexpected signal during runtime execution
        [signal sys: trap: fault read code=0x0 addr=0x0 pc=0x1946c]

        goroutine 230 [running]:
        runtime.throw({0x685615, 0x2a})
        	runtime/panic.go:1018 +0x4c fp=0x96b13a0 sp=0x96b138c pc=0x41354
        runtime.sigpanic()
        	runtime/os_plan9.go:75 +0x4d4 fp=0x96b13e0 sp=0x96b13a0 pc=0x3d57c
        runtime.writeHeapBits.flush({0x9780000, 0x25, 0x6, 0x0}, 0x9780000, 0x0)
...
        cmd/go/internal/work.ActorFunc.Act(0x6bce70, 0x9420930, {0x764b90, 0xa6c170}, 0x973a0c0)
        	cmd/go/internal/work/action.go:78 +0x3c fp=0x96b1e70 sp=0x96b1e54 pc=0x5141e8
        cmd/go/internal/work.(*Builder).Do.func3({0x764b90, 0xa6c170}, 0x973a0c0)
        	cmd/go/internal/work/exec.go:151 +0x764 fp=0x96b1f84 sp=0x96b1e70 pc=0x524188
        cmd/go/internal/work.(*Builder).Do.func4()
        	cmd/go/internal/work/exec.go:219 +0xcc fp=0x96b1fec sp=0x96b1f84 pc=0x523890
        runtime.goexit({})
        	runtime/asm_arm.s:859 +0x4 fp=0x96b1fec sp=0x96b1fec pc=0x770ec
        created by cmd/go/internal/work.(*Builder).Do in goroutine 1
        	cmd/go/internal/work/exec.go:205 +0x3a8

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-09-25 14:43 plan9-arm go@de3bae19 (log) 
fatal error: unexpected signal during runtime execution
fatal error: unexpected signal during runtime execution
panic during panic
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x3f554]

runtime stack:
runtime.throw({0x61f923, 0x2a})
	/tmp/genbootstrap-3479644045/go-plan9-arm-bootstrap/src/runtime/panic.go:1047 +0x4c fp=0x3ffffbdc sp=0x3ffffbc8 pc=0x3aca0
runtime.sigpanic()
	/tmp/genbootstrap-3479644045/go-plan9-arm-bootstrap/src/runtime/os_plan9.go:80 +0x4e8 fp=0x3ffffc1c sp=0x3ffffbdc pc=0x36aa4
runtime.preemptall(...)
	/tmp/genbootstrap-3479644045/go-plan9-arm-bootstrap/src/runtime/proc.go:5531
runtime.freezetheworld()
	/tmp/genbootstrap-3479644045/go-plan9-arm-bootstrap/src/runtime/proc.go:916 +0x170 fp=0x3ffffc30 sp=0x3ffffc20 pc=0x3f554
runtime.startpanic_m()
	/tmp/genbootstrap-3479644045/go-plan9-arm-bootstrap/src/runtime/panic.go:1220 +0x15c fp=0x3ffffc44 sp=0x3ffffc30 pc=0x3b2d0
runtime.fatalthrow.func1()
	/tmp/genbootstrap-3479644045/go-plan9-arm-bootstrap/src/runtime/panic.go:1125 +0x2c fp=0x3ffffc64 sp=0x3ffffc44 pc=0x3afc8
runtime.fatalthrow(0x2)
	/tmp/genbootstrap-3479644045/go-plan9-arm-bootstrap/src/runtime/panic.go:1120 +0x64 fp=0x3ffffc80 sp=0x3ffffc64 pc=0x3af84
runtime.throw({0x61f923, 0x2a})
	/tmp/genbootstrap-3479644045/go-plan9-arm-bootstrap/src/runtime/panic.go:1047 +0x4c fp=0x3ffffc94 sp=0x3ffffc80 pc=0x3aca0
runtime.sigpanic()
	/tmp/genbootstrap-3479644045/go-plan9-arm-bootstrap/src/runtime/os_plan9.go:80 +0x4e8 fp=0x3ffffcd4 sp=0x3ffffc94 pc=0x36aa4
runtime.forEachP(0x6565d0)
	/tmp/genbootstrap-3479644045/go-plan9-arm-bootstrap/src/runtime/proc.go:1673 +0xe4 fp=0x3ffffd10 sp=0x3ffffcd8 pc=0x41094
runtime.gcMarkDone.func1()
	/tmp/genbootstrap-3479644045/go-plan9-arm-bootstrap/src/runtime/mgc.go:814 +0x4c fp=0x3ffffd24 sp=0x3ffffd10 pc=0x663e4
runtime.systemstack()
	/tmp/genbootstrap-3479644045/go-plan9-arm-bootstrap/src/runtime/asm_arm.s:317 +0x60 fp=0x3ffffd28 sp=0x3ffffd24 pc=0x69950

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-09-22 21:51 plan9-arm oauth2@14b275c9 go@5152be39 (log) 
runtime: program exceeds 0-thread limit
fatal error: thread exhaustion

runtime stack:
runtime.throw({0x670c18, 0x11})
	runtime/panic.go:1018 +0x4c fp=0x3ffffd74 sp=0x3ffffd60 pc=0x41354
runtime.checkmcount()
	runtime/proc.go:805 +0xd4 fp=0x3ffffd90 sp=0x3ffffd74 pc=0x45874
runtime.mReserveID()
	runtime/proc.go:821 +0x74 fp=0x3ffffda4 sp=0x3ffffd90 pc=0x4591c
...
runtime.retake(0x1788ab41d31b6a80)
	runtime/proc.go:5745 +0x2f8 fp=0x3ffffe20 sp=0x3ffffdf8 pc=0x513a4
runtime.sysmon()
	runtime/proc.go:5653 +0x5d0 fp=0x3ffffe8c sp=0x3ffffe20 pc=0x50eb8
runtime.mstart1()
	runtime/proc.go:1601 +0x7c fp=0x3ffffe9c sp=0x3ffffe8c pc=0x47604
runtime.mstart0()
	runtime/proc.go:1558 +0x64 fp=0x3ffffeac sp=0x3ffffe9c pc=0x47578
runtime.mstart()
	runtime/asm_arm.s:210 +0x8 fp=0x3ffffeb0 sp=0x3ffffeac pc=0x754d4

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-10-02 20:28 plan9-arm go@eb070d74 (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x1a904]

runtime stack:
runtime.throw({0x686517, 0x2a})
	runtime/panic.go:1018 +0x4c fp=0x3ffffb74 sp=0x3ffffb60 pc=0x4122c
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d4 fp=0x3ffffbb4 sp=0x3ffffb74 pc=0x3d454
runtime.(*mcache).prepareForSweep(0x0)
	runtime/mcache.go:321 +0x14 fp=0x3ffffbd0 sp=0x3ffffbb8 pc=0x1a904
runtime.acquirep(0x9435900)
	runtime/proc.go:5347 +0x2c fp=0x3ffffbf0 sp=0x3ffffbd0 pc=0x4fde8
runtime.exitsyscallfast_pidle()
	runtime/proc.go:4322 +0xcc fp=0x3ffffc0c sp=0x3ffffbf0 pc=0x4d8f8
runtime.exitsyscallfast.func1()
	runtime/proc.go:4271 +0x2c fp=0x3ffffc24 sp=0x3ffffc0c pc=0x4d6f0
traceback: unexpected SPWRITE function runtime.systemstack
runtime.systemstack(0x1)
	runtime/asm_arm.s:317 +0x60 fp=0x3ffffc28 sp=0x3ffffc24 pc=0x75484

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-10-18 19:36 plan9-arm go@5d0a277f (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x1588c]
2023-10-23 09:01 plan9-arm tools@6360c0b1 go@3839447a x/tools/go/analysis/internal/versiontest.TestVettool (log) 
--- FAIL: TestVettool (2.57s)
    version_test.go:107: vettool: exit status: 'go 13852: 2'
        fatal error: unexpected signal during runtime execution
        [signal sys: trap: fault read code=0x0 addr=0x0 pc=0x1ea8c]

        runtime stack:
        runtime.throw({0x6873e0, 0x2a})
        	runtime/panic.go:1016 +0x4c fp=0x3ffffd70 sp=0x3ffffd5c pc=0x41048
        runtime.sigpanic()
        	runtime/os_plan9.go:75 +0x4d4 fp=0x3ffffdb0 sp=0x3ffffd70 pc=0x3d2d0
...
        cmd/go/internal/work.(*buildActor).Act(0x96ff988, 0x953aaf0, {0x7660c0, 0xa6e088}, 0x9564840)
        	cmd/go/internal/work/action.go:460 +0x34 fp=0x9619e70 sp=0x9619e54 pc=0x5158fc
        cmd/go/internal/work.(*Builder).Do.func3({0x7660c0, 0xa6e088}, 0x9564840)
        	cmd/go/internal/work/exec.go:151 +0x770 fp=0x9619f84 sp=0x9619e70 pc=0x524548
        cmd/go/internal/work.(*Builder).Do.func4()
        	cmd/go/internal/work/exec.go:220 +0xcc fp=0x9619fec sp=0x9619f84 pc=0x523c44
        runtime.goexit({})
        	runtime/asm_arm.s:859 +0x4 fp=0x9619fec sp=0x9619fec pc=0x76a64
        created by cmd/go/internal/work.(*Builder).Do in goroutine 1
        	cmd/go/internal/work/exec.go:206 +0x3a8

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-10-24 07:12 plan9-arm crypto@cf8dcb0f go@0262ea1f (log)

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-11-02 17:31 plan9-arm go@a334c452 (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x3afdc]

goroutine 580 [running]:
runtime.throw({0x68947a, 0x2a})
	runtime/panic.go:1016 +0x4c fp=0x96f131c sp=0x96f1308 pc=0x407a0
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d4 fp=0x96f135c sp=0x96f131c pc=0x3ca28
runtime.(*spanSet).pop(0xa63ca8)
	runtime/mspanset.go:189 +0x144 fp=0x96f13a8 sp=0x96f1360 pc=0x3afdc
...
cmd/go/internal/work.(*buildActor).Act(0x95cd6c8, 0x952e0a0, {0x768318, 0xa70190}, 0x98bb200)
	cmd/go/internal/work/action.go:460 +0x34 fp=0x96f1e70 sp=0x96f1e54 pc=0x517508
cmd/go/internal/work.(*Builder).Do.func3({0x768318, 0xa70190}, 0x98bb200)
	cmd/go/internal/work/exec.go:151 +0x770 fp=0x96f1f84 sp=0x96f1e70 pc=0x526150
cmd/go/internal/work.(*Builder).Do.func4()
	cmd/go/internal/work/exec.go:220 +0xcc fp=0x96f1fec sp=0x96f1f84 pc=0x52584c
runtime.goexit({})
	runtime/asm_arm.s:859 +0x4 fp=0x96f1fec sp=0x96f1fec pc=0x761a4
created by cmd/go/internal/work.(*Builder).Do in goroutine 1
	cmd/go/internal/work/exec.go:206 +0x3a8

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-11-01 07:09 plan9-arm go@6ecadb4d (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0xe0c4]

runtime stack:
runtime.throw({0x689455, 0x2a})
	runtime/panic.go:1016 +0x4c fp=0x3ffffbcc sp=0x3ffffbb8 pc=0x407a0
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d4 fp=0x3ffffc0c sp=0x3ffffbcc pc=0x3ca28
runtime.notesleep(0x9608434)
	runtime/lock_sema.go:174 +0x6c fp=0x3ffffc2c sp=0x3ffffc10 pc=0xe0c4
runtime.mPark(...)
	runtime/proc.go:1688
runtime.stopm()
	runtime/proc.go:2585 +0x90 fp=0x3ffffc40 sp=0x3ffffc2c pc=0x47fcc
runtime.findRunnable()
	runtime/proc.go:3298 +0xd80 fp=0x3ffffce8 sp=0x3ffffc40 pc=0x49bb4
runtime.schedule()
	runtime/proc.go:3652 +0xac fp=0x3ffffd04 sp=0x3ffffce8 pc=0x4ae34
runtime.park_m(0x96b1400)
	runtime/proc.go:3815 +0x160 fp=0x3ffffd20 sp=0x3ffffd04 pc=0x4b69c
runtime.mcall(0x1)
	runtime/asm_arm.s:265 +0x48 fp=0x3ffffd28 sp=0x3ffffd20 pc=0x7462c

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-11-08 15:03 plan9-arm go@04d64a3b cmd/compile/internal/types2.TestIssue13898 (log) 
--- FAIL: TestIssue13898 (4.18s)
panic: main:6:4: could not import go/importer (can't find import: "go/importer": fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x19fec]

runtime stack:
runtime.throw({0x689803, 0x2a})
	runtime/panic.go:1016 +0x4c fp=0x3ffffc78 sp=0x3ffffc64 pc=0x4077c
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d4 fp=0x3ffffcb8 sp=0x3ffffc78 pc=0x3ca04
runtime.(*mcache).prepareForSweep(0x0)
...
cmd/compile/internal/types2_test.TestIssue13898(0x9222700)
	/boot/workdir/go/src/cmd/compile/internal/types2/issues_test.go:250 +0x9c fp=0x9613f94 sp=0x9613f78 pc=0x3197fc
testing.tRunner(0x9222700, 0x3c41a0)
	/boot/workdir/go/src/testing/testing.go:1682 +0x128 fp=0x9613fe0 sp=0x9613f94 pc=0x11d6f0
testing.(*T).Run.gowrap1()
	/boot/workdir/go/src/testing/testing.go:1735 +0x30 fp=0x9613fec sp=0x9613fe0 pc=0x11e67c
runtime.goexit({})
	/boot/workdir/go/src/runtime/asm_arm.s:859 +0x4 fp=0x9613fec sp=0x9613fec pc=0x78d44
created by testing.(*T).Run in goroutine 1
	/boot/workdir/go/src/testing/testing.go:1735 +0x3c4

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-11-09 22:45 plan9-arm go@eda42f7c (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x18894]

runtime stack:
runtime.throw({0x68abbb, 0x2a})
	runtime/panic.go:1016 +0x4c fp=0x3ffffb18 sp=0x3ffffb04 pc=0x40b88
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d0 fp=0x3ffffb58 sp=0x3ffffb18 pc=0x3ce10
runtime.(*mspan).typePointersOfUnchecked(0xa8a2b8, 0x1122640)
	runtime/mbitmap_allocheaders.go:199 +0x4c fp=0x3ffffb6c sp=0x3ffffb5c pc=0x18894
runtime.scanobject(0x1122640, 0x103dc5c)
	runtime/mgcmark.go:1365 +0x8c fp=0x3ffffbbc sp=0x3ffffb6c pc=0x27214
runtime.gcDrain(0x103dc5c, 0x3)
	runtime/mgcmark.go:1161 +0x2d8 fp=0x3ffffc0c sp=0x3ffffbbc pc=0x2680c
runtime.gcDrainMarkWorkerDedicated(...)
	runtime/mgcmark.go:1043
runtime.gcBgMarkWorker.func2()
	runtime/mgc.go:1367 +0xb8 fp=0x3ffffc38 sp=0x3ffffc0c pc=0x2170c
runtime.systemstack(0x1)
	runtime/asm_arm.s:317 +0x60 fp=0x3ffffc3c sp=0x3ffffc38 pc=0x74e18

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-11-21 20:13 plan9-arm go@f7b27790 (log) 
fatal error: unexpected signal during runtime execution
fatal error: unexpected signal during runtime execution
panic during panic
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x45ed4]

runtime stack:
runtime.throw({0x6947cb, 0x2a})
	runtime/panic.go:1023 +0x4c fp=0x3ffffa80 sp=0x3ffffa6c pc=0x41338
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d0 fp=0x3ffffac0 sp=0x3ffffa80 pc=0x3d5c0
...
	os/exec/exec.go:577 +0x50 fp=0x1263fb0 sp=0x1263f74 pc=0x126e88
os/exec.(*Cmd).Start.func2(0x137e150)
	os/exec/exec.go:724 +0x30 fp=0x1263fe4 sp=0x1263fb0 pc=0x127ac0
os/exec.(*Cmd).Start.gowrap1()
	os/exec/exec.go:736 +0x30 fp=0x1263fec sp=0x1263fe4 pc=0x127a64
runtime.goexit({})
	runtime/asm_arm.s:859 +0x4 fp=0x1263fec sp=0x1263fec pc=0x771c0
created by os/exec.(*Cmd).Start in goroutine 416
	os/exec/exec.go:723 +0x968
go tool dist: Failed: exit status: 'go 30131: 2'

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-11-29 15:49 plan9-arm go@1908d435 (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x1a63c]

runtime stack:
runtime.throw({0x69afb0, 0x2a})
	runtime/panic.go:1023 +0x4c fp=0x3ffff9d0 sp=0x3ffff9bc pc=0x42044
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d0 fp=0x3ffffa10 sp=0x3ffff9d0 pc=0x3e384
runtime.(*mcache).prepareForSweep(0x0)
	runtime/mcache.go:321 +0x14 fp=0x3ffffa2c sp=0x3ffffa14 pc=0x1a63c
...
	os/exec/exec.go:577 +0x50 fp=0x11c0fb4 sp=0x11c0f78 pc=0x12b2b0
os/exec.(*Cmd).Start.func2(0x1300060)
	os/exec/exec.go:724 +0x30 fp=0x11c0fe4 sp=0x11c0fb4 pc=0x12bee8
os/exec.(*Cmd).Start.gowrap1()
	os/exec/exec.go:736 +0x30 fp=0x11c0fec sp=0x11c0fe4 pc=0x12be8c
runtime.goexit({})
	runtime/asm_arm.s:859 +0x4 fp=0x11c0fec sp=0x11c0fec pc=0x7b2e4
created by os/exec.(*Cmd).Start in goroutine 397
	os/exec/exec.go:723 +0x968
go tool dist: Failed: exit status: 'go 27274: 2'

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-11-29 21:44 plan9-arm go@858cd8da runtime.TestDebugLogBuild (log) 
--- FAIL: TestDebugLogBuild (17.97s)
    crash_test.go:152: running /boot/workdir/go/bin/go build -o /tmp/go-build1334257494/testprog_-tags=debuglog.exe -tags=debuglog
    debuglog_test.go:167: building testprog [-tags=debuglog]: exit status: 'go 43249: 2'
        fatal error: unexpected signal during runtime execution
        [signal sys: trap: fault read code=0x0 addr=0x0 pc=0x3c940]

        goroutine 244 gp=0x1003e68 m=12 mp=0x1278008 [running]:
        runtime.throw({0x69b240, 0x2a})
        	runtime/panic.go:1023 +0x4c fp=0x126f370 sp=0x126f35c pc=0x42044
        runtime.sigpanic()
...
        os/exec.(*Cmd).writerDescriptor.func1()
        	os/exec/exec.go:578 +0x7c fp=0x110bfb4 sp=0x110bf78 pc=0x12b2dc
        os/exec.(*Cmd).Start.func2(0x1016490)
        	os/exec/exec.go:724 +0x30 fp=0x110bfe4 sp=0x110bfb4 pc=0x12bee8
        os/exec.(*Cmd).Start.gowrap1()
        	os/exec/exec.go:736 +0x30 fp=0x110bfec sp=0x110bfe4 pc=0x12be8c
        runtime.goexit({})
        	runtime/asm_arm.s:859 +0x4 fp=0x110bfec sp=0x110bfec pc=0x7b2e4
        created by os/exec.(*Cmd).Start in goroutine 242
        	os/exec/exec.go:723 +0x968

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-12-01 19:20 plan9-arm go@5a2161ce cmd/compile/internal/types2.TestStdFixed (log) 
--- FAIL: TestStdFixed (38.14s)
    stdlib_test.go:281: /boot/workdir/go/test/fixedbugs/bug257.go:12:2: could not import crypto/md5 (can't find import: "crypto/md5": fatal error: unexpected signal during runtime execution
        [signal sys: trap: fault read code=0x0 addr=0x0 pc=0x3c7b4]

        runtime stack:
        runtime.throw({0x69b340, 0x2a})
        	runtime/panic.go:1023 +0x4c fp=0x3ffffb38 sp=0x3ffffb24 pc=0x42044
        runtime.sigpanic()
        	runtime/os_plan9.go:75 +0x4d0 fp=0x3ffffb78 sp=0x3ffffb38 pc=0x3e384
        runtime.(*spanSet).push(0xa843d8, 0xf40808)
...
        	os/exec/exec.go:577 +0x50 fp=0x1551fb4 sp=0x1551f78 pc=0x12b31c
        os/exec.(*Cmd).Start.func2(0x1362e60)
        	os/exec/exec.go:724 +0x30 fp=0x1551fe4 sp=0x1551fb4 pc=0x12bf54
        os/exec.(*Cmd).Start.gowrap1()
        	os/exec/exec.go:736 +0x30 fp=0x1551fec sp=0x1551fe4 pc=0x12bef8
        runtime.goexit({})
        	runtime/asm_arm.s:859 +0x4 fp=0x1551fec sp=0x1551fec pc=0x7b350
        created by os/exec.(*Cmd).Start in goroutine 101
        	os/exec/exec.go:723 +0x968
        )

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-12-04 19:27 plan9-arm go@818de275 net/http.TestOmitHTTP2Vet (log) 
http.test 37865: warning: process exceeds 100 file descriptors
--- FAIL: TestOmitHTTP2Vet (28.33s)
    http_test.go:105: go vet failed: exit status: 'go 37927: 2', fatal error: unexpected signal during runtime execution
        [signal sys: trap: fault read code=0x0 addr=0x0 pc=0x1a63c]

        runtime stack:
        runtime.throw({0x69b350, 0x2a})
        	runtime/panic.go:1023 +0x4c fp=0x3ffffbd0 sp=0x3ffffbbc pc=0x42044
        runtime.sigpanic()
        	runtime/os_plan9.go:75 +0x4d0 fp=0x3ffffc10 sp=0x3ffffbd0 pc=0x3e384
...
        syscall.await({0x16bbd40, 0x200, 0x200})
        	syscall/zsyscall_plan9_arm.go:45 +0x48 fp=0x16bbd24 sp=0x16bbcf8 pc=0x8f1a4
        syscall.Await(0x12d5c20)
        	syscall/syscall_plan9.go:274 +0x50 fp=0x16bbf84 sp=0x16bbd24 pc=0x8e78c
        syscall.startProcess.func1()
        	syscall/exec_plan9.go:517 +0x210 fp=0x16bbfec sp=0x16bbf84 pc=0x8c704
        runtime.goexit({})
        	runtime/asm_arm.s:859 +0x4 fp=0x16bbfec sp=0x16bbfec pc=0x7b360
        created by syscall.startProcess in goroutine 1002
        	syscall/exec_plan9.go:492 +0xbc

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2023-12-06 21:33 plan9-arm go@a9c9cc07 (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault write code=0x0 addr=0x0 pc=0x9a04]

goroutine 1500 gp=0x16106c8 m=7 mp=0x1514508 [running]:
runtime.throw({0x69c645, 0x2a})
	runtime/panic.go:1023 +0x4c fp=0x1043f08 sp=0x1043ef4 pc=0x427b0
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d0 fp=0x1043f48 sp=0x1043f08 pc=0x3ec84
runtime.(*waitq).dequeue(0x1606ea0)
	runtime/chan.go:781 +0x68 fp=0x1043f64 sp=0x1043f4c pc=0x9a04
...
	os/exec/exec.go:578 +0x7c fp=0x130bfb4 sp=0x130bf78 pc=0x12c038
os/exec.(*Cmd).Start.func2(0x1016f10)
	os/exec/exec.go:724 +0x30 fp=0x130bfe4 sp=0x130bfb4 pc=0x12cc44
os/exec.(*Cmd).Start.gowrap1()
	os/exec/exec.go:736 +0x30 fp=0x130bfec sp=0x130bfe4 pc=0x12cbe8
runtime.goexit({})
	runtime/asm_arm.s:859 +0x4 fp=0x130bfec sp=0x130bfec pc=0x7c040
created by os/exec.(*Cmd).Start in goroutine 1524
	os/exec/exec.go:723 +0x968
go tool dist: Failed: exit status: 'go 60977: 2'

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-01-17 03:56 plan9-arm go@8e658eee (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x14534]

goroutine 266 [running]:
runtime.throw({0x15ced5, 0x2a})
	/boot/workdir/go1.4/src/runtime/panic.go:1047 +0x4c fp=0x8f59a78 sp=0x8f59a64 pc=0x3927c
runtime.sigpanic()
	/boot/workdir/go1.4/src/runtime/os_plan9.go:80 +0x4e8 fp=0x8f59ab8 sp=0x8f59a78 pc=0x352dc
runtime.writeHeapBits.flush({0x8c1a800, 0x10, 0x5, 0x4}, 0x8c1a810, 0x8)
	/boot/workdir/go1.4/src/runtime/mbitmap.go:861 +0x60 fp=0x8f59ac8 sp=0x8f59abc pc=0x14534
...
	/boot/workdir/go/src/cmd/dist/build.go:653 +0x38 fp=0x8f59fec sp=0x8f59fdc pc=0x109e90
runtime.goexit()
	/boot/workdir/go1.4/src/runtime/asm_arm.s:831 +0x4 fp=0x8f59fec sp=0x8f59fec pc=0x681c4
created by main.startInstall
	/boot/workdir/go/src/cmd/dist/build.go:653 +0x128

goroutine 6 [running]:
	goroutine running on other thread; stack unavailable
created by main.bginit
	/boot/workdir/go/src/cmd/dist/util.go:138 +0x40

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-01-08 19:14 plan9-arm perf@4ad5199a go@f19f31f2 (log) 
runtime:   gp: gp=0x11f5e68, goid=0, gp->atomicstatus=0
runtime: getg:  g=0x131bd48, goid=0,  g->atomicstatus=0
fatal error: bad g->status in ready

runtime stack:
runtime.throw({0x68c5ec, 0x16})
	runtime/panic.go:1023 +0x4c fp=0x3ffffd18 sp=0x3ffffd04 pc=0x42784
runtime.ready(0x11f5e68, 0x4, 0x1)
	runtime/proc.go:959 +0x13c fp=0x3ffffd38 sp=0x3ffffd18 pc=0x47138
runtime.send.goready.func1()
...
fatal error: unexpected signal during runtime execution
panic during panic
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x6e290]

runtime stack:
runtime.throw({0x69c9f2, 0x2a})
	runtime/panic.go:1023 +0x4c fp=0x3ffff9c0 sp=0x3ffff9ac pc=0x42784
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d0 fp=0x3ffffa00 sp=0x3ffff9c0 pc=0x3ec58
runtime.(*unwinder).resolveInternal(0x3ffffb44, 0x1, 0x1)
...
runtime.fatalthrow(0x2)
	runtime/panic.go:1192 +0x64 fp=0x3ffffd04 sp=0x3ffffce8 pc=0x42c08
runtime.throw({0x68c5ec, 0x16})
	runtime/panic.go:1023 +0x4c fp=0x3ffffd18 sp=0x3ffffd04 pc=0x42784
runtime.ready(0x11f5e68, 0x4, 0x1)
	runtime/proc.go:959 +0x13c fp=0x3ffffd38 sp=0x3ffffd18 pc=0x47138
runtime.send.goready.func1()
	runtime/proc.go:413 +0x2c fp=0x3ffffd48 sp=0x3ffffd38 pc=0x8a90
runtime.systemstack(0x49901)
	runtime/asm_arm.s:317 +0x60 fp=0x3ffffd4c sp=0x3ffffd48 pc=0x7a650

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-01-08 16:44 plan9-arm crypto@dbb6ec16 go@f19f31f2 (log)

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-01-24 22:13 plan9-arm go@6674f222 (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x1b378]

runtime stack:
runtime.throw({0x4a7ab9, 0x2a})
	/boot/workdir/go/src/runtime/panic.go:1011 +0x4c fp=0x3ffffcd0 sp=0x3ffffcbc pc=0x428ec
runtime.sigpanic()
	/boot/workdir/go/src/runtime/os_plan9.go:75 +0x4d4 fp=0x3ffffd10 sp=0x3ffffcd0 pc=0x3ef04
runtime.(*mcache).prepareForSweep(0x0)
	/boot/workdir/go/src/runtime/mcache.go:321 +0x14 fp=0x3ffffd2c sp=0x3ffffd14 pc=0x1b378
...
	/boot/workdir/go/src/syscall/zsyscall_plan9_arm.go:45 +0x48 fp=0x9b9bd24 sp=0x9b9bcf8 pc=0x8c9c8
syscall.Await(0x95fe560)
	/boot/workdir/go/src/syscall/syscall_plan9.go:274 +0x50 fp=0x9b9bf84 sp=0x9b9bd24 pc=0x8bfb0
syscall.startProcess.func1()
	/boot/workdir/go/src/syscall/exec_plan9.go:517 +0x210 fp=0x9b9bfec sp=0x9b9bf84 pc=0x89f28
runtime.goexit({})
	/boot/workdir/go/src/runtime/asm_arm.s:859 +0x4 fp=0x9b9bfec sp=0x9b9bfec pc=0x78c90
created by syscall.startProcess in goroutine 5093
	/boot/workdir/go/src/syscall/exec_plan9.go:492 +0xbc
go tool dist: FAILED: /boot/workdir/go/pkg/tool/plan9_arm/go_bootstrap install cmd: exit status: 'go_bootstrap 8848: 2'

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-02-02 18:20 plan9-arm go@6b0309ce (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x2be38]

runtime stack:
runtime.throw({0x15d377, 0x2a})
	/boot/workdir/go1.4/src/runtime/panic.go:1047 +0x4c fp=0x3ffffb1c sp=0x3ffffb08 pc=0x3927c
runtime.sigpanic()
	/boot/workdir/go1.4/src/runtime/os_plan9.go:80 +0x4e8 fp=0x3ffffb5c sp=0x3ffffb1c pc=0x352dc
runtime.(*mheap).freeSpanLocked(0x23dc68, 0x8b41b84, 0x0)
	/boot/workdir/go1.4/src/runtime/mheap.go:1600 +0xb4 fp=0x3ffffb90 sp=0x3ffffb60 pc=0x2be38
...
main.dopack({0x8d80400, 0x3a}, {0x8f5c450, 0x2c}, {0x8f4a240, 0x0, 0x0})
	/boot/workdir/go/src/cmd/dist/build.go:1148 +0x2c4 fp=0x8e7ac20 sp=0x8e7ab84 pc=0x10fa94
main.runInstall({0x8df20f1, 0x8}, 0x8d802c0)
	/boot/workdir/go/src/cmd/dist/build.go:1001 +0x4614 fp=0x8e7afdc sp=0x8e7ac20 pc=0x10e578
main.startInstall.func1()
	/boot/workdir/go/src/cmd/dist/build.go:661 +0x38 fp=0x8e7afec sp=0x8e7afdc pc=0x109f38
runtime.goexit()
	/boot/workdir/go1.4/src/runtime/asm_arm.s:831 +0x4 fp=0x8e7afec sp=0x8e7afec pc=0x681c4
created by main.startInstall
	/boot/workdir/go/src/cmd/dist/build.go:661 +0x128

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-02-01 15:34 plan9-arm go@5b6cd3d0 (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x197e4]

runtime stack:
runtime.throw({0x6a3c3b, 0x2a})
	runtime/panic.go:1011 +0x4c fp=0x3ffff774 sp=0x3ffff760 pc=0x42800
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d0 fp=0x3ffff7b4 sp=0x3ffff774 pc=0x3ed58
runtime.readUintptr(...)
	runtime/mbitmap.go:466
...
	os/exec/exec.go:577 +0x50 fp=0x1297fb4 sp=0x1297f78 pc=0x13017c
os/exec.(*Cmd).Start.func2(0x1582450)
	os/exec/exec.go:724 +0x30 fp=0x1297fe4 sp=0x1297fb4 pc=0x130db4
os/exec.(*Cmd).Start.gowrap1()
	os/exec/exec.go:736 +0x30 fp=0x1297fec sp=0x1297fe4 pc=0x130d58
runtime.goexit({})
	runtime/asm_arm.s:859 +0x4 fp=0x1297fec sp=0x1297fec pc=0x7c2f0
created by os/exec.(*Cmd).Start in goroutine 518
	os/exec/exec.go:723 +0x968
go tool dist: Failed: exit status: 'go 25535: 2'

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-02-19 07:24 plan9-arm go@35fa852d (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x53f00]

runtime stack:
runtime.throw({0x69e45c, 0x2a})
	runtime/panic.go:1021 +0x4c fp=0x3ffffc90 sp=0x3ffffc7c pc=0x42820
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d0 fp=0x3ffffcd0 sp=0x3ffffc90 pc=0x3ed50
runtime.(*gQueue).pop(...)
	runtime/proc.go:6940 pc=0x53f01
...
	syscall/zsyscall_plan9_arm.go:45 +0x48 fp=0x1595d24 sp=0x1595cf8 pc=0x90378
syscall.Await(0x12e6480)
	syscall/syscall_plan9.go:274 +0x50 fp=0x1595f84 sp=0x1595d24 pc=0x8f960
syscall.startProcess.func1()
	syscall/exec_plan9.go:517 +0x210 fp=0x1595fec sp=0x1595f84 pc=0x8d8d8
runtime.goexit({})
	runtime/asm_arm.s:859 +0x4 fp=0x1595fec sp=0x1595fec pc=0x7c3bc
created by syscall.startProcess in goroutine 519
	syscall/exec_plan9.go:492 +0xbc
go tool dist: Failed: exit status: 'go 24318: 2'

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-03-08 01:59 plan9-arm go@80a91d34 (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x4b75c]

runtime stack:
runtime.throw({0x6ac4ad, 0x2a})
	runtime/panic.go:1021 +0x4c fp=0x3ffffae0 sp=0x3ffffacc pc=0x42844
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d0 fp=0x3ffffb20 sp=0x3ffffae0 pc=0x3ed74
runtime.findRunnable()
	runtime/proc.go:3204 +0x25d fp=0x3ffffbd4 sp=0x3ffffb24 pc=0x4b75d
...
	os/exec/exec.go:577 +0x21 fp=0x13a4fb4 sp=0x13a4f78 pc=0x131855
os/exec.(*Cmd).Start.func2(0x121e300)
	os/exec/exec.go:724 +0x30 fp=0x13a4fe4 sp=0x13a4fb4 pc=0x1324bc
os/exec.(*Cmd).Start.gowrap1()
	os/exec/exec.go:736 +0x30 fp=0x13a4fec sp=0x13a4fe4 pc=0x132460
runtime.goexit({})
	runtime/asm_arm.s:884 +0x4 fp=0x13a4fec sp=0x13a4fec pc=0x7b9c8
created by os/exec.(*Cmd).Start in goroutine 459
	os/exec/exec.go:723 +0x968
go tool dist: Failed: exit status: 'go 19645: 2'

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-03-08 22:17 plan9-arm go@854dea06 go/types.TestSelf (log) 
--- FAIL: TestSelf (2.72s)
    self_test.go:33: api.go:32:2: could not import go/constant (can't find import: "go/constant": runtime:   gp: gp=0x117cd88, goid=157, gp->atomicstatus=2
        runtime: getg:  g=0x1202488, goid=0,  g->atomicstatus=0
        fatal error: bad g->status in ready

        runtime stack:
        runtime.throw({0x69c4e9, 0x16})
        	runtime/panic.go:1021 +0x4c fp=0x3ffffcd4 sp=0x3ffffcc0 pc=0x42c7c
        runtime.ready(0x117cd88, 0x4, 0x1)
        	runtime/proc.go:960 +0x15c fp=0x3ffffcf4 sp=0x3ffffcd4 pc=0x47854
...
        fatal error: unexpected signal during runtime execution
        panic during panic
        [signal sys: trap: fault read code=0x0 addr=0x0 pc=0x6e338]

        runtime stack:
        runtime.throw({0x6ad029, 0x2a})
        	runtime/panic.go:1021 +0x4c fp=0x3ffff8ac sp=0x3ffff898 pc=0x42c7c
        runtime.sigpanic()
        	runtime/os_plan9.go:75 +0x4d0 fp=0x3ffff8ec sp=0x3ffff8ac pc=0x3f1b4
        runtime.(*unwinder).next(0x3ffffb00)
...
        	runtime/panic.go:1190 +0x64 fp=0x3ffffcc0 sp=0x3ffffca4 pc=0x43100
        runtime.throw({0x69c4e9, 0x16})
        	runtime/panic.go:1021 +0x4c fp=0x3ffffcd4 sp=0x3ffffcc0 pc=0x42c7c
        runtime.ready(0x117cd88, 0x4, 0x1)
        	runtime/proc.go:960 +0x15c fp=0x3ffffcf4 sp=0x3ffffcd4 pc=0x47854
        runtime.send.goready.func1()
        	runtime/proc.go:413 +0x2c fp=0x3ffffd04 sp=0x3ffffcf4 pc=0x8b58
        runtime.systemstack(0x4a101)
        	runtime/asm_arm.s:317 +0x60 fp=0x3ffffd08 sp=0x3ffffd04 pc=0x7a910
        )

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-03-14 17:02 plan9-arm go@c841ba3a (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x10c90]

goroutine 926 gp=0x13f57a8 m=6 mp=0x13f2008 [running]:
runtime.throw({0x6ae3d9, 0x2a})
	runtime/panic.go:1021 +0x4c fp=0x15354a8 sp=0x1535494 pc=0x42cec
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d0 fp=0x15354e8 sp=0x15354a8 pc=0x3f224
runtime.nextFreeFast(...)
	runtime/malloc.go:912 pc=0x10c91
...
	os/exec/exec.go:577 +0x21 fp=0x1161fb4 sp=0x1161f78 pc=0x132ad9
os/exec.(*Cmd).Start.func2(0x13e43e0)
	os/exec/exec.go:724 +0x30 fp=0x1161fe4 sp=0x1161fb4 pc=0x133740
os/exec.(*Cmd).Start.gowrap1()
	os/exec/exec.go:736 +0x30 fp=0x1161fec sp=0x1161fe4 pc=0x1336e4
runtime.goexit({})
	runtime/asm_arm.s:884 +0x4 fp=0x1161fec sp=0x1161fec pc=0x7cbb0
created by os/exec.(*Cmd).Start in goroutine 945
	os/exec/exec.go:723 +0x968
go tool dist: Failed: exit status: 'go 20526: 2'

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-04-02 13:49 plan9-arm go@be50b58d (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x48d98]

runtime stack:
runtime.throw({0x4b12bc, 0x2a})
	/boot/workdir/go/src/runtime/panic.go:1021 +0x4c fp=0x3ffffb04 sp=0x3ffffaf0 pc=0x41bec
runtime.sigpanic()
	/boot/workdir/go/src/runtime/os_plan9.go:75 +0x4d4 fp=0x3ffffb44 sp=0x3ffffb04 pc=0x3e204
runtime.runSafePointFn()
	/boot/workdir/go/src/runtime/proc.go:2029 +0x54 fp=0x3ffffb60 sp=0x3ffffb48 pc=0x48d98
...
	/boot/workdir/go/src/syscall/zsyscall_plan9_arm.go:45 +0x48 fp=0x9d0bd24 sp=0x9d0bcf8 pc=0xcba4c
syscall.Await(0x9654400)
	/boot/workdir/go/src/syscall/syscall_plan9.go:274 +0x50 fp=0x9d0bf84 sp=0x9d0bd24 pc=0xcb034
syscall.startProcess.func1()
	/boot/workdir/go/src/syscall/exec_plan9.go:517 +0x210 fp=0x9d0bfec sp=0x9d0bf84 pc=0xc8fac
runtime.goexit({})
	/boot/workdir/go/src/runtime/asm_arm.s:884 +0x4 fp=0x9d0bfec sp=0x9d0bfec pc=0x78410
created by syscall.startProcess in goroutine 5283
	/boot/workdir/go/src/syscall/exec_plan9.go:492 +0xbc
go tool dist: FAILED: /boot/workdir/go/pkg/tool/plan9_arm/go_bootstrap install cmd: exit status: 'go_bootstrap 9964: 2'

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-03-15 15:59 plan9-arm mod@aa51b25a go@3b29222f (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x18e64]

runtime stack:
runtime.throw({0x6bbdf5, 0x2a})
	runtime/panic.go:1021 +0x4c fp=0x3ffffad4 sp=0x3ffffac0 pc=0x421f8
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d0 fp=0x3ffffb14 sp=0x3ffffad4 pc=0x3e730
runtime.(*mspan).typePointersOfUnchecked(0xf88390, 0x117d860)
	runtime/mbitmap_allocheaders.go:202 +0x4c fp=0x3ffffb28 sp=0x3ffffb18 pc=0x18e64
...
os/exec.(*Cmd).writerDescriptor.func1()
	os/exec/exec.go:577 +0x50 fp=0x1741fb4 sp=0x1741f78 pc=0x12f944
os/exec.(*Cmd).Start.func2(0x1858710)
	os/exec/exec.go:724 +0x30 fp=0x1741fe4 sp=0x1741fb4 pc=0x13057c
os/exec.(*Cmd).Start.gowrap1()
	os/exec/exec.go:736 +0x30 fp=0x1741fec sp=0x1741fe4 pc=0x130520
runtime.goexit({})
	runtime/asm_arm.s:884 +0x4 fp=0x1741fec sp=0x1741fec pc=0x7c6d4
created by os/exec.(*Cmd).Start in goroutine 1940
	os/exec/exec.go:723 +0x968

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-04-11 21:23 plan9-arm go@bfb1f563 (log) 
fatal error: unexpected signal during runtime execution
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0xe0f8]

runtime stack:
runtime.throw({0x6beac7, 0x2a})
	runtime/panic.go:1021 +0x4c fp=0x3ffffb48 sp=0x3ffffb34 pc=0x423a4
runtime.sigpanic()
	runtime/os_plan9.go:75 +0x4d0 fp=0x3ffffb88 sp=0x3ffffb48 pc=0x3e8dc
runtime.(*lfstack).pop(0xab4cc8)
	runtime/lfstack.go:47 +0x50 fp=0x3ffffbb4 sp=0x3ffffb8c pc=0xe0f8
...
	os/exec/exec.go:577 +0x50 fp=0x1441fb4 sp=0x1441f78 pc=0x130254
os/exec.(*Cmd).Start.func2(0x15b0210)
	os/exec/exec.go:724 +0x30 fp=0x1441fe4 sp=0x1441fb4 pc=0x130e8c
os/exec.(*Cmd).Start.gowrap1()
	os/exec/exec.go:736 +0x30 fp=0x1441fec sp=0x1441fe4 pc=0x130e30
runtime.goexit({})
	runtime/asm_arm.s:884 +0x4 fp=0x1441fec sp=0x1441fec pc=0x7cf78
created by os/exec.(*Cmd).Start in goroutine 490
	os/exec/exec.go:723 +0x968
go tool dist: Failed: exit status: 'go 14748: 2'

— watchflakes

@gopherbot
Copy link

Found new dashboard test flakes for:

#!watchflakes
post <- goos == "plan9" && log ~ `unexpected signal during runtime execution` && log ~ `runtime\.bgscavenge`
2024-04-12 18:04 plan9-arm go@28b5d80d (log) 
fatal error: unexpected signal during runtime execution
fatal error: unexpected signal during runtime execution
panic during panic
[signal sys: trap: fault read code=0x0 addr=0x0 pc=0x46ca4]

runtime stack:
runtime.throw({0x4b3b97, 0x2a})
	/boot/workdir/go/src/runtime/panic.go:1021 +0x4c fp=0x3ffffb6c sp=0x3ffffb58 pc=0x41f44
runtime.sigpanic()
	/boot/workdir/go/src/runtime/os_plan9.go:75 +0x4d0 fp=0x3ffffbac sp=0x3ffffb6c pc=0x3e55c
...
	/boot/workdir/go/src/syscall/zsyscall_plan9_arm.go:45 +0x48 fp=0x1269d24 sp=0x1269cf8 pc=0xcc1c0
syscall.Await(0x113c0a0)
	/boot/workdir/go/src/syscall/syscall_plan9.go:274 +0x50 fp=0x1269f84 sp=0x1269d24 pc=0xcb7a8
syscall.startProcess.func1()
	/boot/workdir/go/src/syscall/exec_plan9.go:517 +0x210 fp=0x1269fec sp=0x1269f84 pc=0xc9720
runtime.goexit({})
	/boot/workdir/go/src/runtime/asm_arm.s:884 +0x4 fp=0x1269fec sp=0x1269fec pc=0x78b18
created by syscall.startProcess in goroutine 1511
	/boot/workdir/go/src/syscall/exec_plan9.go:492 +0xbc
go tool dist: FAILED: /boot/workdir/go/pkg/tool/plan9_arm/go_bootstrap install -a cmd/asm cmd/cgo cmd/compile cmd/link: exit status: 'go_bootstrap 5030: 2'

— watchflakes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. help wanted NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Plan9
Projects
Test Flakes
Status: No status
Milestone
Unplanned
Development

No branches or pull requests
5 participants
@fhs @mknyszek @ianlancetaylor @bcmills @gopherbot