#1005001 kernel: traps: boinccmd/boincmgr trap invalid opcode [â¦] error:0 in libboinc.so.7.18.1/boincmgr #1005001
- Package:
- boinc-client
- Source:
- boinc
- Description:
- core client for the BOINC distributed computing infrastructure
- Submitter:
- Marcel Partap
- Date:
- 2022-03-07 16:45:03 UTC
- Severity:
- normal
After an update, boinccmd and boincmgr crash with "Illegal instruction"..?! Log: kernel: traps: boinccmd[1250032] trap invalid opcode ip:7fa11f98453c sp:7ffd25f42c40 error:0 in libboinc.so.7.18.1[7fa11f968000+52000] kernel: traps: boincmgr[1251274] trap invalid opcode ip:55814c1a6689 sp:7ffe16eb6840 error:0 in boincmgr[55814c17d000+18e000] Still happily crunching; boinctui still works for suspend/resume.
… Sorry for the oversight, it was the old client binary still running.. A boinc-client.service restart also fails with: kernel: traps: boinc[1263003] trap invalid opcode ip:562370352cf4 sp:7ffedd7ca2c0 error:0 in boinc[56237034a000+c0000] systemd[1]: boinc-client.service: Failed with result 'signal'. Downgraded to 7.16.16+dfsg-1, which works but now spams the log with "No protocol specified" 😏
i can confirm this bug since update to 7.18.1 boinc client does not start any more systemd[1]: boinc-client.service: Main process exited, code=killed, status=4/ILL traps: boinc[436] trap invalid opcode ip:557a0e20bcf4 sp:7fffaf68e300 error:0 in boinc[557a0e203000+c0000] systemd[1]: boinc-client.service: Failed with result 'signal'.
Dear Maintainer, I could reproduce this issue inside a minimal QEMU VM with a CPU lacking the AVX instructions. It looks like the patch new-autoconf-build-fix.patch introduced adding of "-mavx" to CXXFLAGS flags. Salsa already contains a patch [1] to remove that "-mavx": "Reversing -mavx for compatibility with older servers" A package version containing this patch is not yet released. Kind regards, Bernhard [1] https://salsa.debian.org/pkg-boinc-team/boinc/-/commit/a0611c2bc86864428337b07b382e4d5cf823b95d