Bug 678352

Summary: systemd: crash on boot
Product: [openSUSE] openSUSE 11.4 Reporter: Jan Engelhardt <jengelh>
Component: BasesystemAssignee: Kay Sievers <kasievers>
Status: VERIFIED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: coredump from systemd

Description Jan Engelhardt 2011-03-10 01:59:06 UTC 
The systemd-18-1.2.4 as shipped in openSUSE 11.4 has a problem of some kind.

Mar 10 01:28:47 yaguchi kernel: [   38.272309] systemd[1]: segfault at 10 ip 080
9c28e sp aff473b0 error 4 in systemd[8048000+b6000]
Mar 10 01:28:47 yaguchi kernel: [   38.292144] systemd[1]: Caught <SEGV>, dumped
 core as pid 1488.

Updating to the copy in openSUSE:Factory (systemd-18-1.4 rpm) seems to have fixed it already.
Comment 1 Jan Engelhardt 2011-03-10 09:45:18 UTC 
Created attachment 418505 [details]
coredump from systemd

Seems to also occur with systemd-20.

Would be nice if, upon reception of SIGSEGV, systemd could print something to the console. Right now it's absolutely silent with the exception of /var/log/messages, meaning it appears to just hang until you actually look for the problem.
Comment 2 Kay Sievers 2011-03-10 12:43:26 UTC 
I can't easily look at the core, I have only x86_64 boxes left, and it does not crash here.

Mind to get a backtrace with:
  gdb /bin/systemd /core
  $ bt full

Thanks!
Comment 4 Jan Engelhardt 2011-03-13 09:26:25 UTC 
Unfortunately the bug did not happen again - even with v18 - so far, weird. But bug #676786 has the backtrace that I think I saw, and so might be set to resolved too.

*** This bug has been marked as a duplicate of bug 676786 ***