Is there any more information I could provide?

Please answer a couple of the issue template questions that you deleted:

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

Does this issue reproduce with the latest release?

Clear steps to reproduce the issue could be useful, too.

Thanks for the prompt reply. Please bear with me while I try to obtain this information.

Also, when you are in gdb and stopped at the SIGILL, can you do:

x/i $pc
info reg $lr
info reg $ctr

@Helflym Are you seeing this problem too?

I've lost access to my AIX VM and trying to get it back to see if I can reproduce with latest Go. The above problem was from a binary built with go1.14. I'll be back with more details ASAP.

Thanks a lot for jumping in 🙏

No, I don't remember having already seen anything like this.
I'll take a deeper look tomorrow (I can't today).

I managed to reproduce this issue on my own now, I have the binary and the core dump available. It happens with go1.16 too.

@laboger here is the response to the commands you've requested (core dump from binary compiled with go1.16):

Program terminated with signal SIGILL, Illegal instruction.
#0  0x000000010004e904 in runtime.check () at /usr/local/go/src/runtime/runtime1.go:239
239     /usr/local/go/src/runtime/runtime1.go: A file or directory in the path name does not exist..
(gdb) where
#0  0x000000010004e904 in runtime.check () at /usr/local/go/src/runtime/runtime1.go:239
#1  0x0000000100072dbc in runtime.rt0_go () at /usr/local/go/src/runtime/asm_ppc64x.s:82
#2  0xbadc0ffee0ddf00d in ?? ()
(gdb) x/i $pc
=> 0x10004e904 <runtime.check+468>:     lbarx   r31,0,r6
(gdb) info reg $lr
lr             0x100072dbc      0x100072dbc <runtime.rt0_go+172>
(gdb) info reg $ctr
ctr            0x100072d10      4295437584
(gdb) 

Note that this time it breaks in a different place.

Any ideas for next steps?

That is an atomic byte instruction from POWER8.
Are your sure your chip supports it? https://github.com/golang/go/wiki/MinimumRequirements#ppc64-big-endian

That is an atomic byte instruction from POWER8.
Are your sure your chip supports it?

My bad. The machine I logged into said "POWER8" in the title, but checking prtconf right now I see it's POWER7. I wonder if that's the issue for the problem in the start of this thread too. I'm going to look into it and if that's the case, close the issue.

It turns out the processor was Power7. Closing. Sorry for the misunderstanding.

@randall77 I hope it's ok to ping you here. I have a question and I don't want to pollute with yet another open issue, perhaps you have a quick answer for me. Would a machine like this support:

Server 1:Processor Implementation 
Mode: POWER 7 Processor 
Type: PowerPC_POWER8

Server 2:Processor Implementation 
Mode: POWER 7Processor 
Type: PowerPC_POWER9

Example of two machines running processor type POWER8 and POWER9 but mode is POWER7.

@gbbr if I remember correctly, the processor mode is exactly as if the CPU behind was a power7. Thus, it won't be supported.

I have no idea. Wouldn't be hard for you to test it, I suppose.

@gbbr Sorry for the late response. lbarx is new in power8 do won't run on power7. Is there a reason this is running in power7 mode on a power8 and power9? Seems like that could be easily fixed with the appropriate setting.