You are not logged in.

#1 2015-08-12 16:21:41

ostroffjh
Member
From: Southeast Connecticut, USA
Registered: 2009-11-13
Posts: 25

go gives me "SIGKILL: illegal instruction"

This started with me trying to use the heroku toolbelt, but it seems the underlying problem is that any attempt to use go (1.4.2-2) gives me an error

SIGILL: illegal instruction
PC=0x81f4ea9

goroutine 1 [running, locked to thread]:
math.init·1()
        /usr/lib/go/src/math/pow10.go:34 +0x19 fp=0x1872ff4c sp=0x1872ff48
math.init()
        /usr/lib/go/src/math/unsafe.go:21 +0x3f fp=0x1872ff50 sp=0x1872ff4c
strconv.init()
        /usr/lib/go/src/strconv/quote.go:455 +0x45 fp=0x1872ff6c sp=0x1872ff50
go/parser.init()
        /usr/lib/go/src/go/parser/parser.go:2462 +0x4a fp=0x1872ff78 sp=0x1872ff6c
main.init()
        /usr/lib/go/src/cmd/go/zdefaultcc.go:6 +0x45 fp=0x1872ffcc sp=0x1872ff78
runtime.main()
        /usr/lib/go/src/runtime/proc.go:58 +0xbd fp=0x1872fff0 sp=0x1872ffcc
runtime.goexit()
        /usr/lib/go/src/runtime/asm_386.s:2287 +0x1 fp=0x1872fff4 sp=0x1872fff0

goroutine 2 [runnable]:
runtime.forcegchelper()
        /usr/lib/go/src/runtime/proc.go:90
runtime.goexit()
        /usr/lib/go/src/runtime/asm_386.s:2287 +0x1

goroutine 3 [runnable]:
runtime.bgsweep()
        /usr/lib/go/src/runtime/mgc0.go:82
runtime.goexit()
        /usr/lib/go/src/runtime/asm_386.s:2287 +0x1

eax     0x187380a0
ebx     0x856f650
ecx     0x187000a0
edx     0x474df990
edi     0x7
esi     0x2b28
ebp     0x187380a0
esp     0x1872ff48
eip     0x81f4ea9
eflags  0x10206
cs      0x73
fs      0x0
gs      0x33

Most posts I've found on this seem to be related to ARM and/or cross compilation.  I'm using an old Athlon - /proc/cpuinfo gives

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 10
model name      : AMD Athlon(TM) XP
stepping        : 0
cpu MHz         : 1916.619
cache size      : 512 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fdiv_bug        : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow 3dnowprefetch vmmcall
bugs            : fxsave_leak sysret_ss_attrs
bogomips        : 3834.95
clflush size    : 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts

Is there any point in reporting this as a bug, or am I just using too old a CPU to be supported by Arch any more?  Thanks for any other troubleshooting suggestions.
[edit - I suspect it's likely the lack of sse2 that is the issue, based on some old posts related to other  issues about losing support for older CPUs.]

Last edited by ostroffjh (2015-08-12 16:28:41)

Offline

Board footer

Powered by FluxBB