From: Dave Reisner <d@falconindy.com>
To: linux-hotplug@vger.kernel.org
Subject:
Date: Sat, 22 Sep 2012 15:13:49 +0000 [thread overview]
Message-ID: <20120922151349.GD474@rampage> (raw)
systemd-devel@lists.freedesktop.org
Bcc:
Subject: Re: segfault at start-up with systemd 190
Reply-To:
In-Reply-To: <alpine.LNX.2.01.1209221048040.481@waverley.dhcp.wfu.edu>
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
reply other threads:[~2012-09-22 15:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120922151349.GD474@rampage \
--to=d@falconindy.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).