Illegal instruction on ARM Linux (raspberry pi)

[surdu]

• Version: v4.3.1 & v5.7.0
• Platform: Linux raspberrypi 4.1.13+ _#_826 PREEMPT Fri Nov 13 20:13:22 GMT 2015 armv6l GNU/Linux

After installing nodejs using the package manager as instructed in the docs on raspbery pi, whenever I try to run either npm or node I get a Illegal instruction.

I realize that maybe more information are needed, but I don't know what else to add.

[bnoordhuis]

Can you turn on core dumps (ulimit -c unlimited) and run node -e 0? Open the core dump in gdb with gdb node <corefile> and type thread apply all backtrace full followed by disassemble $pc,+32. Please post the output here.

[surdu]

Sure thing:

gdb node core
Copyright and license bla bla bla
...
...
This GDB was configured as "arm-linux-gnueabihf".
...
...
Reading symbols from node...(no debugging symbols found)...done.

warning: core file may not match specified executable file.
[New LWP 750]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Core was generated by `node -e 0'.
Program terminated with signal SIGILL, Illegal instruction.
#0  0x00339992 in BN_GF2m_mod_solve_quad ()

(gdb) thread apply all backtrace full

Thread 1 (Thread 0xb6f72440 (LWP 750)):
#0  0x00339992 in BN_GF2m_mod_solve_quad ()
No symbol table info available.

(gdb) disassemble $pc,+32
Dump of assembler code from 0x339992 to 0x3399b2:
=> 0x00339992 <BN_GF2m_mod_solve_quad+98>:  mov.w   r5, r5, lsr #1
   0x00339996 <BN_GF2m_mod_solve_quad+102>: beq.n   0x3399a4 <BN_GF2m_mod_solve_quad+116>
   0x00339998 <BN_GF2m_mod_solve_quad+104>: cmp r8, lr
   0x0033999a <BN_GF2m_mod_solve_quad+106>: it  gt
   0x0033999c <BN_GF2m_mod_solve_quad+108>: strgt.w r4, [r11, lr, lsl #2]
   0x003399a0 <BN_GF2m_mod_solve_quad+112>: add.w   lr, lr, #1
   0x003399a4 <BN_GF2m_mod_solve_quad+116>: subs    r4, #1
   0x003399a6 <BN_GF2m_mod_solve_quad+118>: cmp r4, r1
   0x003399a8 <BN_GF2m_mod_solve_quad+120>: bne.n   0x33998e <BN_GF2m_mod_solve_quad+94>
   0x003399aa <BN_GF2m_mod_solve_quad+122>: cmp r2, r0
   0x003399ac <BN_GF2m_mod_solve_quad+124>: sub.w   r1, r1, #32
   0x003399b0 <BN_GF2m_mod_solve_quad+128>: bne.n   0x33997e <BN_GF2m_mod_solve_quad+78>
End of assembler dump.

[silverwind]

Either you got a wrong binary or we have an issue with OpenSSL. To rule out a possible build issue on our side, can you build from source? Beware, these builds take around 6 hours on that hardware :)

[bnoordhuis]

Quick check, does env OPENSSL_ppccap=0 node -e 0 work?

[apeeters]

@bnoordhuis Nope, same error here.

[apeeters]

For reference: all builds seem to fail, I tried several, up to nodejs_4.0.0-1nodesource1~jessie1_armhf.deb.

[bnoordhuis]

Right, the armhf package is for ARMv7. The Raspberry Pi is ARMv6.

[apeeters]

That explains! For reference, node-v4.3.1-linux-armv6l.tar.gz works fine.

[silverwind]

Yeah that download page does explicitly state that only ARMv7 and up are supported, so you guys got a wrong binary. You can download the correct ARMv6 ones at https://nodejs.org/en/download/stable/.

As for ARMv6 support in the install script, I'm not sure where to best post a issue, but it might be https://github.com/nodesource/distributions.