-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
go1.5.2, linux/amd64, Building packages ... fatal error: procresize: invalid arg #13908
Comments
How many processors? |
jpi@hydra:~/bin/go1.5/src> cpumap This is an SGI UV Total Number of Sockets : 36 UV Information Number of connected NUMAlink ports: 416 |
The default limit is 256: In src/runtime/runtime2.go: const (
// The max value of GOMAXPROCS.
// There are no fundamental restrictions on the value.
_MaxGomaxprocs = 1 << 8
) Change that and recompile. Or set GOMAXPROCS=256. |
I changed it to: But still ... Building packages and commands for linux/amd64.fatal error: procresize: invalid arg runtime stack: Thanks by the way! |
Sorry, it's too late. Now I changed it to 1024 and it works! |
Thanks a lot, Brad! |
I'm trying to compile/install the go1.5.2 compiler on a SGI NUMA hardware running SUSE Linux Enterprise Server 11 (x86_64). I installed the go1.4.3 compiler before. It passed all tests. Then I set the GOROOT_BOOTSTRAP variable and ran ./all.bash.
Unfortunately, the proccess fails while
Building go_bootstrap for host, linux/amd64.
...
with
Building packages and commands for linux/amd64.
fatal error: procresize: invalid arg
runtime stack:
runtime.throw(0x7a6c00, 0x17)
/home/jpi/bin/go1.5/src/runtime/panic.go:527 +0x90
runtime.procresize(0x240, 0x0)
/home/jpi/bin/go1.5/src/runtime/proc1.go:2713 +0xb0f
runtime.schedinit()
/home/jpi/bin/go1.5/src/runtime/proc1.go:72 +0x110
runtime.rt0_go(0x7fffffffdf88, 0x9, 0x7fffffffdf88, 0x0, 0x0, 0x9, 0x7fffffffe394, 0x7fffffffe3ca, 0x7fffffffe3d2, 0x7fffffffe3db, ...)
/home/jpi/bin/go1.5/src/runtime/asm_amd64.s:109 +0x132
Has anyone an idea what is going wrong? Thanks!
The text was updated successfully, but these errors were encountered: