There is not a single situation that triggers a SIGBUS. With out extra particulars it is unimaginable to debug this downside remotely.
A Bus Error may be indicative of a {hardware} downside. Verify your motherboard and search for bulged capacitors close to the place the reminiscence slots are positioned. For those who discover any, take your PC to a technician. You might attempt taking out the reminiscence modules and clear their gold contacts with paper or eraser rubber. It is also beneficial you clear out the reminiscence slots themselves from any mud.
To utterly rule out a reminiscence downside you may boot your Linux field into memtest86 (included in most Ubuntu boot choices or reside pictures) and depart it operating for a number of hours. If hardware-related, memtest86 will discover most memory-related issues throughout its very first check phases.
Software program circumstances may set off a SIGBUS. Since there is not presently a selected recognized problem on Bitcoin Core that triggers a Bus Error, I might assume it is an issue in your set up. Attempt rebuilding Bitcoin Core from supply or reinstalling/upgrading its prerequisite packages.
Lastly, chances are you’ll attempt tweaking Bitcoin Core’s reminiscence parameters to see if the Bus Error goes away. For those who discover your Linux field is disk thrashing and utilizing an excessive amount of swap when operating Bitcoin, that may very well be a sign of low reminiscence. Use iotop and htop in several screens to observe the IO and CPU-bound programs respectively whereas operating Bitcoin Core and see if both disk or CPU are being hogged by a selected course of.