Hi, Ryan, "Illegal instruction" can happen when the code is compiled with AVX2 or AVX512 instructions enabled, but then runs on a system whose CPU doesn't support those instructions. If you run hashpipe under gdb, you should be able to generate a backtrace when it crashes to identify the bad instruction. You can also check which instructions a system's CPU(s) supports by examining /proc/cpuinfo. You could try compiling the program on the Dell PowerEdge R410 (after running "make clean") to ensure that only instructions supported by that system's CPU are used.
"Illegal instruction" can also happen is there is a buffer overflow on a local variable and the stack gets corrupted such that a return statement pops off a program counter instruction pointer that points to an invalid instruction. HTH, Dave > On Feb 10, 2022, at 16:36, Ryan Lee <[email protected]> wrote: > > Hi Dave, Jeff, and Casperities, > > I have been trying to get hashpipe working on a new machine and I have > encountered an error that I am unfamiliar with. > > When attempting to run my hashpipe program on the new machine, I am getting > an "Illegal instruction" followed by a core dump. I haven't had any issues > with the same code on other machines. We have the code running on 3 other > machines without any issues which are all running the same OS (Ubuntu 18.04.6 > LTS). However the hashpipe framework and libraries seems to be working > properly as we are able to run the demo codes without any issues. The new > machine we are having is a Dell 1u rack server (Dell PowerEdge R410). > > I have been able to narrow down the issue to be when hashpipe is attempting > to lock the shared status buffer for reading and writing. I use the following > functions to lock and unlock the shared status buffer. > > hashpipe_status_t st = args->st; > hashpipe_status_lock_safe(&st); > hashpipe_status_unlock_safe(&st); > > What is strange to me is that the demo code has this same exact line, but it > doesn't cause any errors. Below is an image of the part of the code causing > the issue and the error message on the command line. > <Code.PNG> > > <Error_Message.PNG> > > Does anyone know what is the source of this error and where I should try to > look for fixing it? > > Thanks, > Ryan -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/3E787016-4246-4F03-87E3-DE3A7A634272%40berkeley.edu.
