linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Allin Cottrell <cottrell@wfu.edu>
To: linux-hotplug@vger.kernel.org
Subject: segfault at start-up with systemd 190
Date: Sat, 22 Sep 2012 15:01:43 +0000	[thread overview]
Message-ID: <alpine.LNX.2.01.1209221048040.481@waverley.dhcp.wfu.edu> (raw)

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

-- 
Allin Cottrell
Department of Economics
Wake Forest University, NC


                 reply	other threads:[~2012-09-22 15:01 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=alpine.LNX.2.01.1209221048040.481@waverley.dhcp.wfu.edu \
    --to=cottrell@wfu.edu \
    --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).