Thread #4 4802 [core: 0] (Suspended : Signal : SIGSEGV:Segmentation fault)
__lll_unlock_elision() at 0x7fffe4ce5940
boost::posix::pthread_mutex_unlock() at pthread_mutex_scoped_lock.hpp:62 0x4a79b4
boost::mutex::unlock() at mutex.hpp:76 0x4a79b4
boost::unique_lock<boost::mutex>::~unique_lock() at lock_types.hpp:331 0x4a9a9b
function calling boost::unique_lock<boost::mutex> locker(mutex)
<...more frames...>
From what I’ve seen this may be an issue with processor microcode and can be fixed enabling early microcode updates, unfortunately the documentation I found is for archlinux, then, does anybody know if there is a way doing the same in Leap 15.
For information, I searched for an equivalent for Leap 15 grub method and found a line that may be the one on which we can load the microcode updates:
Is it the one ? Anyway, unfortunately I can’t find what I should add for microcode updates load, is it one of the many files in /lib/firmware/intel-ucode (I have an Intel CPU) ?
AFAIK
On all current openSUSE versions including LEAP 15, a current package containing CPU microcode updates is installed by default so you should be getting the recommended updates for your hardware already.
In my case (verifying functionality for virtualization apps), there is some kind of way to probe the kernel for whether the microcode patch has opened the functionality or not.
Consider also that microcode updates are very CPU and vendor specific, even Intel kernels have greatly progressed on what can be patched with each new CPU release. If your CPU doesn’t support that microcode API, then you may be SOL.
Ok, fixed it, best… way… ever, since the application is a Qt application I replaced the boost::mutex by a QMutex and it does not crash anymore :
By the way, there are several other mutexes in the application that do not lead to a __lll_unlock_elision crash, in any case, the mystery remains !
I just looked at your answer since for now I had no more this issue, but I found another in the application, then, starting from the ucode-intel package, do you know if there is one version that in know working, and also, but this is another story and especially if it does the job, do you know if we can specify a package version to install with autoyast ?