Re: exited on signal 11 (no core dump - other error)

On 12/07/2024 18:45, Tomoaki AOKI wrote:
> On Fri, 12 Jul 2024 14:35:15 +0200
> Miroslav Lachman <000.fbsd@quip.cz> wrote:
> 
>> On 12/07/2024 11:56, Tomoaki AOKI wrote:

[..]

>>>    *Hardware problem
>>>       *Main memory (including memory slot)
>>>       *Dedicated grhaphics memories, if any
>>>        (seems that X-related processes are crashing)
>>>       *Power failures / instabilities
>>>
>>>    *Software problem
>>>       *Mis-alignments caused by ASLR or something
>>>       *Bitten by uncommon bugs in fundamental libraries like libc,
>>>        xcb, glib,...
>>>       *Not sure it's MFC'ed to 13.x or not, but missingly determined
>>>        instruction sets for SIMD libc or something alike.
>>
>> I also thought about the memory modules (even though they are ECC), but
>> a few days ago I replaced them with 4 other modules from the server and
>> the problem persisted. Of course it could be anything else (graphic
>> card, power supply, etc.), but it's strange that it only happens after
>> booting when logging into KDE. When everything crashes and the login
>> screen reappears, I try to log in again, everything crashes again
>> (usually in the part where Signal Desktop starts, but I don't know if
>> it's related). I can repeat this 5 or 10 times, but until I reboot, KDE
>> doesn't fully start. When I reboot, the machine runs all day, even for
>> several days at a time.
>>
>> It also happens that the screenlocker crashes
>>
>> Jul 11 17:32:16 xxx kernel: pid 6487 (kscreenlocker_greet), jid 0, uid
>> 1001: exited on signal 11
>> Jul 11 17:32:16 xxx kernel: pid 6489 (kscreenlocker_greet), jid 0, uid
>> 1001: exited on signal 11
>>
>> Then I have to log in as root via Ctrl+Alt+F2 and run: ck-unlock-session
>> Session1
>>
>> Otherwise, when KDE is running, all applications work without crashing.
>>
>>
>>
>> Kind regards
>> Miroslav Lachman
> 
> Could MySQL related?
> 
> IIRC, KDE defaulted its backend (for akonadi) to MySQL.
> If you're using MySQL for something other than KDE, too, and any of
> the database is/are heavily updated, is there any possibility that
> MySQL cannot flush/commit pending transactions in time?

I already disabled all MySQL related services right after KDE 
installation. MySQL is also disabled in rc.conf, nothing needs it.

The machine in question has 24GB of RAM and 8GB of swap. OS is installed 
on top of Samsung SSD 860 EVO 1TB. So it should be fast enough to run 
KDE5 Plasma desktop (it actually runs KDE for a years), these crashes 
first appeared after some pkg upgrade this year. I don't pkg upgrade too 
often because it almost always come with some apps incompatibilities 
etc.. But the last pkg upgrade was done about a week ago and crashes are 
still there.

Kind regards
Miroslav Lachman