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: kernel crash on darwin (Sierra)? #22016

Closed
fd0 opened this issue Sep 25, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@fd0
Copy link

commented Sep 25, 2017

What version of Go are you using (go version)?

go version go1.9 linux/amd64 (cross-compiled to darwin)

Does this issue reproduce with the latest release?

yes

What operating system and processor architecture are you using (go env)?

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/fd0/shared/work/go"
GORACE=""
GOROOT="/usr/lib/go"
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build170408252=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"

What did you do?

I've built the official released binaries for restic on Linux for darwin. A user reported a kernel crash on a Mac with Sierra. According to the user, the machine is otherwise rock solid. The stack trace is:

Anonymous UUID:       72A2DB74-5BE6-0759-EAAF-962BC14E3A29

Sat Sep 23 20:43:12 2017

*** Panic Report ***
panic(cpu 3 caller 0xffffff8021ffe39d): Kernel trap at 0xffffff8021fa4431, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff7f868ce884, CR3: 0x00000003c9b1e033, CR4: 0x00000000001626e0
RAX: 0xffffff802ba4d438, RBX: 0xffffff7f80000000, RCX: 0xffffff7f868ce880, RDX: 0x000000008013e781
RSP: 0xffffff9220e33ab0, RBP: 0xffffff9220e33af0, RSI: 0x00000000008b5487, RDI: 0x0000000080000000
R8:  0xffffff8038fc6880, R9:  0x0000000000000000, R10: 0x00000000ffffff9f, R11: 0x00000000001f1ac4
R12: 0xffffff80509fe900, R13: 0xffffff802ced8738, R14: 0x0000003fffffffc0, R15: 0x0000000000000000
RFL: 0x0000000000010246, RIP: 0xffffff8021fa4431, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0xffffff7f868ce884, Error code: 0x0000000000000002, Fault CPU: 0x3, PL: 1, VF: 5

Backtrace (CPU 3), Frame : Return Address
0xffffff9220e33740 : 0xffffff8021ee953c 
0xffffff9220e337c0 : 0xffffff8021ffe39d 
0xffffff9220e339a0 : 0xffffff8021e9a593 
0xffffff9220e339c0 : 0xffffff8021fa4431 
0xffffff9220e33af0 : 0xffffff8021faa4e5 
0xffffff9220e33b40 : 0xffffff8021f89d31 
0xffffff9220e33e40 : 0xffffff8021f80d2c 
0xffffff9220e33f30 : 0xffffff8022374685 
0xffffff9220e33f50 : 0xffffff80224240f5 
0xffffff9220e33fb0 : 0xffffff8021e9ad96 

BSD process name corresponding to current thread: restic_0.7.3_dar

Mac OS version:
16G29

Kernel version:
Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64
Kernel UUID: D3314D98-5D40-3CD8-98A4-F1DD46C20E03
Kernel slide:     0x0000000021c00000
Kernel text base: 0xffffff8021e00000
__HIB  text base: 0xffffff8021d00000
System model name: Macmini6,1 (Mac-031AEE4D24BFF0B1)

Please let me know if there's anything we can do on our end to help debugging this issue. Thank you!

What did you expect to see?

No kernel crash.

What did you see instead?

A kernel crash.

@ianlancetaylor ianlancetaylor changed the title Kernel crash on darwin (Sierra)? runtime: kernel crash on darwin (Sierra)? Sep 25, 2017

@ianlancetaylor ianlancetaylor added this to the Go1.10 milestone Sep 25, 2017

@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

commented Sep 25, 2017

Is this reproducible? How easily?

Unfortunately I don't see any useful information in that panic report. I don't even see which system call was executing or anything. Perhaps others can pull out something useful.

If we can reproduce the problem, then ideally we could get the Darwin equivalent of an strace showing the system call sequence that led to the crash.

@fd0

This comment has been minimized.

Copy link
Author

commented Sep 25, 2017

I'll try to find that out, thanks!

@fd0

This comment has been minimized.

Copy link
Author

commented Sep 27, 2017

It looks like it's faulty memory, the user managed to crash the kernel with the Apple Hardware Test and memtest86. I'm therefore closing this issue. Thanks!

@fd0 fd0 closed this Sep 27, 2017

@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

commented Sep 27, 2017

Thanks for following up.

@golang golang locked and limited conversation to collaborators Sep 27, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.