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

runtime: "fatal: systemstack called from unexpected goroutine" on Android #51001

Open
bcmills opened this issue Feb 3, 2022 · 7 comments
Open

runtime: "fatal: systemstack called from unexpected goroutine" on Android #51001

bcmills opened this issue Feb 3, 2022 · 7 comments
Labels
NeedsInvestigation okay-after-beta1 OS-Android release-blocker
Milestone

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented Feb 3, 2022

greplogs --dashboard -md -l -e '^fatal: systemstack called from unexpected goroutine' --since=2021-01-01

2022-02-02T21:12:39-53d6a72/android-amd64-emu

##### GOMAXPROCS=2 runtime -cpu=1,2,4 -quick
fatal: systemstack called from unexpected goroutineTrap 
exitcode=133
FAIL	runtime	59.879s

2021-10-08T16:26:20-59d4e92-99c1b24/android-amd64-emu

fatal: systemstack called from unexpected goroutineSegmentation fault 
exitcode=139FAIL	golang.org/x/net/publicsuffix	3.419s

I'll also note that badsystemstackMsg seems to be missing a final newline as of CL 93659 (CC @aclements @randall77). 😅

@bcmills bcmills added NeedsInvestigation OS-Android labels Feb 3, 2022
@bcmills bcmills added this to the Backlog milestone Feb 3, 2022
@bcmills
Copy link
Member Author

@bcmills bcmills commented May 3, 2022

This happened in a TryBot in https://storage.googleapis.com/go-build-log/f1e11825/android-amd64-emu_262486a5.log:

##### GOMAXPROCS=2 runtime -cpu=1,2,4 -quick
fatal: systemstack called from unexpected goroutineTrap 
exitcode=133
FAIL	runtime	16.177s
FAIL
2022/05/03 14:18:09 Failed: exit status 1
go tool dist: FAILED

Marking as release-blocker because this affects TryBot runs. Since android/amd64 is not a first-class port, either the underlying bug can be diagnosed and fixed, or the builder can be removed from the default TryBot set. (I'll leave that choice up to @golang/runtime to decide and implement.)

@bcmills bcmills removed this from the Backlog milestone May 3, 2022
@bcmills bcmills added this to the Go1.19 milestone May 3, 2022
@bcmills
Copy link
Member Author

@bcmills bcmills commented May 3, 2022

This may or may not be OS-specific. There is another failure in the builder logs since February, but on plan9 rather than android; it isn't obvious to me whether that is an independent bug.

greplogs -l -e 'fatal: systemstack called from unexpected goroutine' --since=2022-02-03
2022-03-05T21:20:16-e155b03-45f4544/plan9-amd64-0intro

@bcmills
Copy link
Member Author

@bcmills bcmills commented May 4, 2022

greplogs -l -e 'fatal: systemstack called from unexpected goroutine' --since=2022-03-06
2022-05-03T19:48:07-bccce90/android-arm64-corellium

@bcmills bcmills changed the title runtime: "fatal: systemstack called from unexpected goroutine" on android-amd64-emu runtime: "fatal: systemstack called from unexpected goroutine" on android/amd64 May 4, 2022
@mknyszek
Copy link
Contributor

@mknyszek mknyszek commented May 18, 2022

@golang/runtime This is a second class port, but because it's a trybot, this is a release blocker. Should we consider removing this as a trybot? Is that bringing us enough value?

@gopherbot
Copy link

@gopherbot gopherbot commented May 20, 2022

Change https://go.dev/cl/407615 mentions this issue: dashboard: remove android-amd64-emu from main go repo's TryBot set

@dmitshur
Copy link
Contributor

@dmitshur dmitshur commented May 20, 2022

I've mailed CL 407615 that makes android-amd64-emu a post-submit builder only (in the main repo) while investigation of this issue is underway. If submitted, this issue can be unmarked as a release-blocker for Go 1.19.

@bcmills bcmills changed the title runtime: "fatal: systemstack called from unexpected goroutine" on android/amd64 runtime: "fatal: systemstack called from unexpected goroutine" on Android May 23, 2022
@bcmills
Copy link
Member Author

@bcmills bcmills commented May 23, 2022

Curiously, this does not appear to be arch-specific: we've seen these failures on both amd64 and arm64.

greplogs -l -e 'fatal: systemstack called from unexpected goroutine' --since=2022-05-04
2022-05-20T22:30:37-2b0e457/android-arm64-corellium

@prattmic prattmic added the okay-after-beta1 label May 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation okay-after-beta1 OS-Android release-blocker
Projects
Status: Todo
Development

No branches or pull requests

5 participants