From nobody Fri Jul 12 12:35:15 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WL9zZ6s3Mz5QJW2 for ; Fri, 12 Jul 2024 12:35:22 +0000 (UTC) (envelope-from SRS0=SYDv=OM=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WL9zZ3cwsz435s; Fri, 12 Jul 2024 12:35:22 +0000 (UTC) (envelope-from SRS0=SYDv=OM=quip.cz=000.fbsd@elsa.codelab.cz) Authentication-Results: mx1.freebsd.org; none Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 2753AD7890; Fri, 12 Jul 2024 14:35:20 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1720787720; bh=uEAg6BQQXZMwk6H4MPXtZM6X5w4yMA3KlgmJXiDuZto=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=rNwYzkmykQQVPK/SoPxikipSTssP3wdlwt8BXrI/yyMtrZn9yBfUc4kJ6AHkIm8aX FT6pCDlCfC467H2VmDmGNPGYAADlszHITe+DJdGAvk8bdrle7MVlpbd9LD4C3DYNUQ Ev+YjIC6N/qurDfyPbPR5Xkq8kiXaDCJOjc+vkBo= Received: from [192.168.145.49] (ip-89-177-27-225.bb.vodafone.cz [89.177.27.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 01A9BD78B1; Fri, 12 Jul 2024 14:35:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1720787717; bh=uEAg6BQQXZMwk6H4MPXtZM6X5w4yMA3KlgmJXiDuZto=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=KHuTnssRQlZxaHaegZuTYAlGLlpmLX+og1GemjavvvKFjs5FnQObSr2/cpqFJL9Vw TeDOLmHcTBu8GjkzZmxPas4W9Cz0vIxA4Ounu+t0aLFNx8unf+FGk/vZqwo7vpTvWB wMRv5yDgi46XWUH5tgICkphlkStWnNxjdfboyJxo= Message-ID: <47c9a84d-847c-4bbf-82f5-dfac6c02b041@quip.cz> Date: Fri, 12 Jul 2024 14:35:15 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: exited on signal 11 (no core dump - other error) To: Tomoaki AOKI Cc: Zhenlei Huang , FreeBSD Current References: <694d7804-3eab-4a27-8f6f-53f79346e9df@quip.cz> <20240712185607.bf0aba83738501c80dce9cc2@dec.sakura.ne.jp> Content-Language: cs-Cestina From: Miroslav Lachman <000.fbsd@quip.cz> In-Reply-To: <20240712185607.bf0aba83738501c80dce9cc2@dec.sakura.ne.jp> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ] X-Rspamd-Queue-Id: 4WL9zZ3cwsz435s On 12/07/2024 11:56, Tomoaki AOKI wrote: > On Fri, 12 Jul 2024 10:20:19 +0200 > Miroslav Lachman <000.fbsd@quip.cz> wrote: [..] >> Something similar happens to me, but when logging into KDE Plasma. >> Sometimes it happens that desktop applications that start from a saved >> session (Firefox, Thunderbird, Telegram, Signal...) start loading and >> then everything crashes. The login screen reappears and when I log in >> again, everything crashes again until I restart the machine. The machine >> gets into this state randomly, about once a week. >> >> Jul 5 12:24:52 xxx kernel: pid 1647 (packagekitd), jid 0, uid 0: exited >> on signal 11 (core dumped) >> Jul 5 12:25:28 xxx kernel: pid 1897 (kalarm), jid 0, uid 1001: exited >> on signal 6 (core dumped) >> Jul 5 12:25:36 xxx kernel: pid 1467 (Xorg), jid 0, uid 0: exited on >> signal 6 (core dumped) >> Jul 5 12:25:37 xxx kernel: pid 1772 (signal-desktop), jid 0, uid 1001: >> exited on signal 5 (core dumped) >> Jul 5 12:25:39 xxx pulseaudio[1630]: [] core-util.c: Failed to create >> secure directory (/var/run/user/1001/pulse): No such file or directory >> Jul 5 12:25:40 xxx kernel: pid 1776 (audacious), jid 0, uid 1001: >> exited on signal 6 (core dumped) >> Jul 5 12:25:41 xxx kernel: pid 1915 (drkonqi), jid 0, uid 1001: exited >> on signal 6 (core dumped) >> Jul 5 12:25:42 xxx kernel: pid 1914 (kwin_x11), jid 0, uid 1001: exited >> on signal 6 (core dumped) >> >> My system is 13.3-p3 amd64. >> >> Kind regards >> Miroslav Lachman > > What comes in my mind is... > > *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. Translated with DeepL.com (free version) Kind regards Miroslav Lachman