From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 09 Apr 2024 15:55:53 +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 1ruBx3-004Z0L-2L for lore@lore.pengutronix.de; Tue, 09 Apr 2024 15:55:53 +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 1ruBx3-0001Ue-A7; Tue, 09 Apr 2024 15:55:53 +0200 Received: from gardel.0pointer.net ([2a01:238:43ed:c300:10c3:bcf3:3266:da74]) by metis.whiteo.stw.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ruBug-0000RY-4q for distrokit@pengutronix.de; Tue, 09 Apr 2024 15:53:26 +0200 Received: from gardel-login.0pointer.net (gardel-mail [85.214.157.71]) by gardel.0pointer.net (Postfix) with ESMTP id 53081E802D7; Tue, 9 Apr 2024 15:53:25 +0200 (CEST) Received: by gardel-login.0pointer.net (Postfix, from userid 1000) id DBC73160433; Tue, 9 Apr 2024 15:53:24 +0200 (CEST) Date: Tue, 9 Apr 2024 15:53:24 +0200 From: Lennart Poettering To: systemd-devel@lists.freedesktop.org, distrokit@pengutronix.de Message-ID: References: <20240409-moonlight-viewpoint-29d2a170d8b7@thorsis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240409-moonlight-viewpoint-29d2a170d8b7@thorsis.com> 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=-3.2 required=4.0 tests=AWL,BAYES_00,SPF_HELO_PASS, SPF_PASS autolearn=ham autolearn_force=no version=3.4.2 X-Mailman-Approved-At: Tue, 09 Apr 2024 15:55:50 +0200 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: , 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 On Di, 09.04.24 14:42, Alexander Dahl (ada@thorsis.com) wrote: > 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? Yes. > 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? "coredumpctl gdb" should get open the most recent backtrace for you. The coredump should also show up in the logs with a backtrace. Lennart -- Lennart Poettering, Berlin