From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Reisner Date: Sat, 22 Sep 2012 15:13:49 +0000 Subject: Message-Id: <20120922151349.GD474@rampage> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org systemd-devel@lists.freedesktop.org Bcc: Subject: Re: segfault at start-up with systemd 190 Reply-To: In-Reply-To: On Sat, Sep 22, 2012 at 11:01:43AM -0400, Allin Cottrell wrote: > I built and installed system 190 and I'm getting a segfault on > start-up: > > systemd[1] segfault at 7d ... error 4 in libc-2.16.so > > This comes after messages saying that systemd 190 has started in > system mode, inserted the modules 'autofs4' and 'ipv6', and set the > hostname. The log entries that followed the hostname setting on the > last successful boot (with systemd 189) were invoking > systemd-readahead and starting systemd-udevd. > > After reinstalling system 189 (phew, glad I kept sysv init around > for an emergency boot!) things are working fine again. > > I notice that systemd 190 was followed quickly by a 191 release. Any > ideas if 191 would fix this issue? > > system: Linux 3.5.4, gcc 4.7.2, glibc 2.16. > 64-bit kernel with 32-bit userspace > 191 does not fix this: https://bugs.freedesktop.org/show_bug.cgi?idU213 Cheers, Dave