From nobody Fri Jul 12 16:45:58 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 4WLJcg0Y3Wz5QsQk for ; Fri, 12 Jul 2024 17:34:27 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WLJcd6gmNz4ZBX for ; Fri, 12 Jul 2024 17:34:25 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=dec.sakura.ne.jp header.s=s2405 header.b=Au7Crh1v; dmarc=pass (policy=none) header.from=dec.sakura.ne.jp; spf=pass (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp designates 153.125.133.21 as permitted sender) smtp.mailfrom=junchoon@dec.sakura.ne.jp Received: from kalamity.joker.local (123-1-21-232.area1b.commufa.jp [123.1.21.232]) (authenticated bits=0) by www121.sakura.ne.jp (8.17.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 46CGjwph002674 for ; Sat, 13 Jul 2024 01:45:59 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dec.sakura.ne.jp; s=s2405; t=1720802759; bh=/RKciw4R4CBIFsJ6AmHlz4kTZtfLuK6O8BkXUIsYraA=; h=Date:From:To:Subject:In-Reply-To:References; b=Au7Crh1v5wY34Z7UYODaXn2Xq6II1HFIYzQNblrL85i2jtHy+7Jd/7qzK+gsvM8Ds q2VKl+FJOXMT+hQfZj3Hqcb2/0KZe2x5ZaYPxkYQqLCrT5L+6asYSULJR8QBUJCkgL 4Ci6a1ellaveXgmJ2/VHJf7i67gyKb9+fHON75TM= Date: Sat, 13 Jul 2024 01:45:58 +0900 From: Tomoaki AOKI To: current@freebsd.org Subject: Re: exited on signal 11 (no core dump - other error) Message-Id: <20240713014558.7b63d28c9e79e4d96a02048f@dec.sakura.ne.jp> In-Reply-To: <47c9a84d-847c-4bbf-82f5-dfac6c02b041@quip.cz> References: <694d7804-3eab-4a27-8f6f-53f79346e9df@quip.cz> <20240712185607.bf0aba83738501c80dce9cc2@dec.sakura.ne.jp> <47c9a84d-847c-4bbf-82f5-dfac6c02b041@quip.cz> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.1) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Bar: ++ X-Spamd-Result: default: False [2.20 / 15.00]; URIBL_RED(3.50)[dec.sakura.ne.jp:dkim]; SUSPICIOUS_URL_IN_SUSPICIOUS_MESSAGE(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MV_CASE(0.50)[]; HAS_ANON_DOMAIN(0.10)[]; BAD_REP_POLICIES(0.10)[]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; DMARC_POLICY_ALLOW(0.00)[dec.sakura.ne.jp,none]; DKIM_TRACE(0.00)[dec.sakura.ne.jp:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; GREYLIST(0.00)[pass,body]; R_DKIM_ALLOW(0.00)[dec.sakura.ne.jp:s=s2405]; HAS_ORG_HEADER(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; MIME_TRACE(0.00)[0:+]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; R_SPF_ALLOW(0.00)[+ip4:153.125.133.16/28:c]; RCPT_COUNT_ONE(0.00)[1] X-Rspamd-Queue-Id: 4WLJcd6gmNz4ZBX 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: > > 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 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? -- Tomoaki AOKI