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

cmd/compile,runtime: SIGILL on linux-loong64-3a5000 #53093

Open
bcmills opened this issue May 26, 2022 · 5 comments
Open

cmd/compile,runtime: SIGILL on linux-loong64-3a5000 #53093

bcmills opened this issue May 26, 2022 · 5 comments
Labels
arch-loong64 Issues solely affecting the loongson architecture. compiler/runtime Issues related to the Go compiler and/or runtime. 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
Member

bcmills commented May 26, 2022 •
edited 

#!watchflakes
post <- builder ~ `^linux-loong64` && `signal: illegal instruction \(core dumped\)`

signal: illegal instruction (core dumped)
FAIL	cmd/go/internal/modfetch	0.362s

greplogs -l -e '(?ms)\Alinux-loong64-.*signal: illegal instruction \(core dumped\)'
2022-05-24T17:02:34-70668a4/linux-loong64-3a5000

(attn @golang/loong64)
@bcmills bcmills added the arch-loong64 Issues solely affecting the loongson architecture. label May 26, 2022
@bcmills bcmills changed the title cmd/compile: SIGILL on linux-loong64-3a5000 cmd/compile,runtime: SIGILL on linux-loong64-3a5000 May 26, 2022
@bcmills bcmills added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label May 26, 2022
@bcmills bcmills added this to the Backlog milestone May 26, 2022
@abner-chenc
Copy link
Contributor 

ok  	os/exec/internal/fdtest	0.016s
signal: illegal instruction (core dumped)
FAIL	os/signal	0.129s
ok  	os/user	0.005s

Sorry, We're having the same issue and we're analysing what's causing it.

@xen0n
Copy link
Member

xen0n commented May 27, 2022

I can't reproduce this.

##### Test execution environment.             
# GOARCH: loong64                             
# CPU:                                        
# GOOS: linux                                 
# OS Version: Linux 5.17.0-00067-g8d427f9dd274 #10 SMP PREEMPT Sun May 22 09:34:01 AM CST 2022 loongarch64

Try bumping your kernel version and/or bootstrap toolchain version?

@xen0n
Copy link
Member

xen0n commented May 27, 2022

(My kernel is my handmade https://github.com/xen0n/linux/tree/loongarch-playground-v13.101, FYI. (Basically the last known good version to boot on old firmware, but with UAPI manually upgraded to latest.)

@bcmills bcmills mentioned this issue May 27, 2022
Closed
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 7, 2022
@xen0n
Copy link
Member

xen0n commented Nov 3, 2022

@abner-chenc Hi, do you still see this issue appearing in your daily development? I assume you should be using a more recent system for a while.

@gopherbot
Copy link

Change https://go.dev/cl/465156 mentions this issue: dashboard: unmark known-issues with low failure rates

gopherbot pushed a commit to golang/build that referenced this issue Feb 4, 2023
@bcmills @gopherbot
dashboard: unmark known-issues with low failure rates
20ebdbd 
I had initially added known issues fairly aggressively in order to use
them to reduce noise in 'greplogs -triage'. Now that we are using
'watchflakes' for triage, that noise reduction is no longer important
(the failures are already clustered to their respective known issues),
and having greyed-out cells on the dashboard makes new regressions too
easy to miss.

Concretely:

- golang/go#42212 is mostly specific to x/net at this point (as
  golang/go#57841)

- There have been no failures matching golang/go#51001 since October.

- golang/go#52724 has been so rare lately that we hadn't yet added a
  'watchflakes' pattern for it.

- There have been no failures matching golang/go#51443 since May.

- There have been no failures matching golang/go#53116 or
  golang/go#53093 since I enabled 'watchflakes' for the builder in
  December.

- The linux-amd64-perf builder seems to be passing consistently for
  x/benchmarks and x/tools, so there is no need to refer to
  golang/go#53538 to explain failures on it.

Change-Id: Ia16db2a23e5fa037a299f1f56fb26f1cf84521e1
Reviewed-on: https://go-review.googlesource.com/c/build/+/465156
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Run-TryBot: Bryan Mills <bcmills@google.com>
Auto-Submit: Bryan Mills <bcmills@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
arch-loong64 Issues solely affecting the loongson architecture. compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Go Compiler / Runtime
Status: Triage Backlog
Test Flakes
Status: No status
Milestone
Backlog
Development

No branches or pull requests
4 participants
@xen0n @bcmills @gopherbot @abner-chenc