Dave Reisner
2012-09-22 15:13:49 UTC
systemd-***@lists.freedesktop.org
Bcc:
Subject: Re: segfault at start-up with systemd 190
https://bugs.freedesktop.org/show_bug.cgi?id=55213
Cheers,
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Bcc:
Subject: Re: segfault at start-up with systemd 190
I built and installed system 190 and I'm getting a segfault on
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: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
https://bugs.freedesktop.org/show_bug.cgi?id=55213
Cheers,
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html