Created attachment 423411 [details]
Dump of systemd segfault upon booting
Description of problem:
Today I tried 'systemd' for the first time on my Fedora Rawhide machine. I installed the package with yum and added 'init=/bin/systemd' to the kernel command line, then rebooted the machine. Upon rebooting the machine, a reproducible segfault in libc occurs upon which 'systemd' and therefore 'init' is killed, so that the kernel panics. I have rebooted the machine several times and found that the values for the CPU registers in the dump are the same most of the time, but differ sometimes. Please find the attached logs. I also ran '/bin/systemd --test --running-as=init' as suggested in #systemd on FreeNode and are attaching that output as well (stdout + stderr).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add 'init=/bin/systemd' to the kernel command line on a standard Fedora Rawhide
2. Reboot the machine
'systemd' runs the init scripts and the system comes up normally
Linux oslo.physik.fu-berlin.de 2.6.34-20.fc14.i686 #1 SMP Wed Jun 2 13:12:51 UTC 2010 i686 i686 i386 GNU/Linux
Created attachment 423414 [details]
Dump of systemd segfault upon booting (corrected)
Please ignore the first dump attached, due to some weird bug in Google Chrome, a different file for upload was chosen than I actually selected.
Created attachment 423415 [details]
Output of 'systemd --test --running-as=init'
Created attachment 423417 [details]
Dump of systemd segfault upon booting - 2nd reboot
Created attachment 423418 [details]
Dump of systemd segfault upon booting - 3rd reboot
Created attachment 423419 [details]
Dump of systemd segfault upon booting - 4th reboot
I have pushed another build which should resolve this issue.