From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Wed, 10 Apr 2024 15:50:03 +0200 Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ruYKx-0066y8-11 for lore@lore.pengutronix.de; Wed, 10 Apr 2024 15:50:03 +0200 Received: from localhost ([127.0.0.1] helo=metis.whiteo.stw.pengutronix.de) by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1ruYKw-0005zr-Kj; Wed, 10 Apr 2024 15:50:02 +0200 Received: from mail.thorsis.com ([217.92.40.78]) by metis.whiteo.stw.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ruYKq-0005zT-0v for distrokit@pengutronix.de; Wed, 10 Apr 2024 15:49:57 +0200 Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 63C3C148CA5C; Wed, 10 Apr 2024 15:49:50 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thorsis.com; s=dkim; t=1712756991; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=EraLUEKVYfP5y+AaKm0SPAp98/Fo00z/BKWQQEgHPE8=; b=uwenaq/LrKswFdI9yhp9uWHMgm5UsU5qs0uaF9gUBedTCZoieC7XljSFjI6Ir8YZUE2TMV V0WXQgoQhZMWgwNJMnZRrkPLZ4D1D64HT0Nj80ks+VeLKJ5j/oa56E7Br0A2hKaQFu1Y4l 3hks5izMchn3GLdq4a+gToooynUwKRwsrAtNSd86cMuoaZxyCb1gvmdlgJ7I0uOK4tkElj CV50dNNB9FrqgcbDpyhKEQafKqNAg3INFjBAmHj+mNooa+GYGHsXgp1OAQ2kEa48YuGtcv P9qcgqMJuGXi+SVgkZ3nU7GLEMJXfPk/QfXkjJUOiuBItoKC5sQbQmozn79SzQ== Date: Wed, 10 Apr 2024 15:49:49 +0200 From: Alexander Dahl To: Mantas =?utf-8?Q?Mikul=C4=97nas?= Message-ID: <20240410-setup-coroner-2deb6f89fac6@thorsis.com> Mail-Followup-To: Mantas =?utf-8?Q?Mikul=C4=97nas?= , Topi Miettinen , systemd-devel@lists.freedesktop.org, distrokit@pengutronix.de References: <20240409-moonlight-viewpoint-29d2a170d8b7@thorsis.com> <20240409-encounter-aptitude-09d3f64a697c@thorsis.com> <20240410-cavalier-droop-6034d4ff719e@thorsis.com> <20240410-captive-prelude-36601436cb9d@thorsis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/2.2.12 (2023-09-09) X-Last-TLS-Session-Version: TLSv1.3 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.whiteo.stw.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.2 Subject: Re: [DistroKit] [systemd-devel] How to debug systemd services failing to start with 11/SEGV? X-BeenThere: distrokit@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: DistroKit Mailinglist List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: systemd-devel@lists.freedesktop.org, distrokit@pengutronix.de, Topi Miettinen Sender: "DistroKit" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: distrokit-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.whiteo.stw.pengutronix.de); SAEximRunCond expanded to false Hello Mantas, Am Wed, Apr 10, 2024 at 04:45:58PM +0300 schrieb Mantas Mikulėnas: > On Wed, Apr 10, 2024 at 4:08 PM Alexander Dahl wrote: > > > Note: platform here is 32 bit arm, namely v5te on Microchip SAM9X60 > > SoC. Kernel is 6.6, maybe I did not get the kernelconfig right and > > some options are not set correctly? Or maybe those crashes are real? > > Then I could need some help how to _really_ enable coredumps for > > journald, udevd, and timesyncd. Got a hint off-list to pass > > 'systemd.dump_core=true' to kernel cmdline, but that had no effect on > > coredump creation. > > > > I would just set kernel.core_pattern to a *file* path, e.g. > "/var/log/core.%P". Then use the shell's ulimit command to raise the > coredump size limit as it defaults to zero (ulimit -c unlimited), and > manually start /usr/lib/systemd/systemd-timesyncd from the shell (timesyncd > is the simplest one and doesn't do anything system-critical). Tried that already. The service does not crash in that case. As a workaround for now I added this to /etc/systemd/system/systemd-journald.service.d/override.conf but I'm pretty sure it just hides the underlying issue? [Service] MemoryDenyWriteExecute=no Greets Alex > > Alternatively, run the service under the debugger: `gdb /usr/.../timesyncd`. > > -- > Mantas Mikulėnas