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.

Sign up for GitHub

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: TestNeedmDeadlock failure with SIGSEGV on linux-mips-rtrk builder #43625

Closed
bcmills opened this issue Jan 11, 2021 · 6 comments
Closed

runtime: TestNeedmDeadlock failure with SIGSEGV on linux-mips-rtrk builder #43625

bcmills opened this issue Jan 11, 2021 · 6 comments
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Backlog

Comments

@bcmills
Copy link
Contributor

bcmills commented Jan 11, 2021

2021-01-08T18:15:43-8f6a9ac/linux-mips-rtrk

--- FAIL: TestNeedmDeadlock (0.03s)
    crash_test.go:104: /tmp/gobuilder-mips64/tmp/go-build2938167109/testprogcgo.exe NeedmDeadlock exit status: exit status 2
    crash_cgo_test.go:631: want OK
        , got fatal error: unexpected signal during runtime execution
        [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x0]
        
        runtime stack:
        runtime.throw(0x57cb56, 0x2a)
        	/tmp/gobuilder-mips64/go/src/runtime/panic.go:1112 +0x60
        runtime.sigpanic()
        	/tmp/gobuilder-mips64/go/src/runtime/signal_unix.go:714 +0x3b4
        
        goroutine 17 [syscall, locked to thread]:
        runtime.goexit()
        	/tmp/gobuilder-mips64/go/src/runtime/asm_mipsx.s:635 +0x4 fp=0x83aff0 sp=0x83aff0 pc=0x47d9f8
        
        goroutine 1 [syscall]:
        main._Cfunc_runNeedmSignalThread()
        	_cgo_gotypes.go:404 +0x4c
        main.NeedmDeadlock()
        	/tmp/gobuilder-mips64/go/src/runtime/testdata/testprogcgo/needmdeadlock.go:93 +0x4c
        main.main()
        	/tmp/gobuilder-mips64/go/src/runtime/testdata/testprogcgo/main.go:34 +0x1d8
        
        goroutine 6 [runnable]:
        time.Sleep(0x1, 0x2a05f200)
        	/tmp/gobuilder-mips64/go/src/runtime/time.go:184 +0x184
        main.NeedmDeadlock.func1()
        	/tmp/gobuilder-mips64/go/src/runtime/testdata/testprogcgo/needmdeadlock.go:88 +0x48
        created by main.NeedmDeadlock
        	/tmp/gobuilder-mips64/go/src/runtime/testdata/testprogcgo/needmdeadlock.go:87 +0x44
        
FAIL
FAIL	runtime	116.006s

CC @ianlancetaylor @mengzhuo
@bcmills
Copy link
Contributor Author

bcmills commented Jan 11, 2021

This test is new as of Go 1.16 (for #42207), so marking as release-blocker at least until we better understand the failure mode here. (CC @golang/release)

@bcmills bcmills added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker labels Jan 11, 2021
@bcmills bcmills added this to the Go1.16 milestone Jan 11, 2021
@mengzhuo
Copy link
Contributor

Thanks @bcmills

I'll take a look.

@bcmills bcmills mentioned this issue Jan 15, 2021
Closed
@aclements
Copy link
Member

(FYI, we dropped the release-blocker label because this is a non-first-class port.)

@mengzhuo
Copy link
Contributor

Some updates:
Unfortunately I can't reproduce this issue on my loongson box(mips64le) using 32bit compatible mode.

@dmitshur
Copy link
Contributor

Thanks for the update. It seems there's not enough time to become able to reproduce and then fix this for Go 1.16, so I'll reset the milestone to Backlog for now.

@dmitshur dmitshur modified the milestones: Go1.16, Backlog Feb 10, 2021
@bcmills bcmills mentioned this issue Feb 16, 2021
Closed
@mknyszek mknyszek mentioned this issue Oct 26, 2022
Open
@bcmills
Copy link
Contributor Author

bcmills commented Jan 11, 2023

Duplicate of #56420

@bcmills bcmills marked this as a duplicate of #56420 Jan 11, 2023
@bcmills bcmills closed this as not planned Won't fix, can't repro, duplicate, stale Jan 11, 2023
@golang golang locked and limited conversation to collaborators Jan 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
6 participants
@cagedmantis @mengzhuo @dmitshur @aclements @bcmills @gopherbot