From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 09 Apr 2024 14:42:35 +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 1ruAo7-004TlE-1F for lore@lore.pengutronix.de; Tue, 09 Apr 2024 14:42:35 +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 1ruAo6-0002Ds-Ts; Tue, 09 Apr 2024 14:42:34 +0200 Received: from mail.thorsis.com ([2003:a:e28:26e4::10]) by metis.whiteo.stw.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ruAnz-0002Dj-2a for distrokit@pengutronix.de; Tue, 09 Apr 2024 14:42:28 +0200 Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id E86CA148C716; Tue, 9 Apr 2024 14:42:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thorsis.com; s=dkim; t=1712666542; h=from:subject:date:message-id:to:cc:mime-version:content-type; bh=hDYf+SADSyhRaGsH6Nrwa6aUcxBFkF3T0CGgDARE4hQ=; b=BcstUlcpRI9rY1xksGwFAraMacvnn9szFF0jzizsuPmvVvsCvkkQx8YRQV8O6Sxg+DraXG AzZBnBAFJR5VWSL7Q18A2tJHF6S9L6SiiRkiZs4UFXSrYgC8sKO8QBps337lbe4iWn/U9I 3ND80CdEK9DkL//mI3x+A+MTUcKJlvAS/qGu60wsZ0Tcug4C/g9HWIdTRPkW2sjU420Rim eqWZaVvQfjEefpG+zBBYqAhjJ/Zg8ZYiJIIYvrzjitg1InE+p0ds/e/MrVAXr+JCqWLBNN ruQLADFNQVZyEm4yl8KPVPiXkVuf2xVi0acVxyebMCtjp8D2G43HMDPWZu595w== Date: Tue, 9 Apr 2024 14:42:20 +0200 From: Alexander Dahl To: systemd-devel@lists.freedesktop.org Message-ID: <20240409-moonlight-viewpoint-29d2a170d8b7@thorsis.com> Mail-Followup-To: systemd-devel@lists.freedesktop.org, distrokit@pengutronix.de MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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.9 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: [DistroKit] 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: distrokit@pengutronix.de 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 everyone, I'm currently trying to build a firmware for an embedded device and running into trouble because systemd seems to crash. The BSP is based on pengutronix DistroKit (master) built with ptxdist and the target is the Microchip SAM9X60-Curiosity board, which is arm v5te architecture (that board is not part of DistroKit, support for that is in an upper layer of mine not public yet (?)). Everything is quite recent, building systemd version 255.2 currently. On startup I get messages like this (this is the first one, later on there are lot more, all with the same status): [ 11.175650] systemd[1]: systemd-journald.service: Main process exited, code=killed, status=11/SEGV [ 11.239679] systemd[1]: systemd-journald.service: Failed with result 'signal'. [ 11.292640] systemd[1]: Failed to start systemd-journald.service. [FAILED] Failed to start systemd-journald.service. See 'systemctl status systemd-journald.service' for details. The system drops me on a shell later, where I can run the above mentioned command, which gives: ~ # systemctl status systemd-journald.service x systemd-journald.service - Journal Service Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static) Active: failed (Result: signal) since Tue 2024-04-09 11:44:52 UTC; 11min a> TriggeredBy: x systemd-journald-dev-log.socket * systemd-journald-audit.socket x systemd-journald.socket Docs: man:systemd-journald.service(8) man:journald.conf(5) Process: 197 ExecStart=/usr/lib/systemd/systemd-journald (code=killed, sign> Main PID: 197 (code=killed, signal=SEGV) FD Store: 0 (limit: 4224) CPU: 330ms This does not help me much. Other services crashing: systemd-udevd and systemd-timesyncd, also with status 11/SEGV which is segmentation fault, right? I had this board running with an older version of systemd, but I can not remember which was the last good version. Could anyone give me a hint please how to debug this? (The same version runs fine btw. when building that BSP for an arm v7a target!) Greets Alex