http://bugzilla.opensuse.org/show_bug.cgi?id=918226 Bug ID: 918226 Summary: systemd segfaults after updating from 208-23.3 to 208-28.1 Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: pszaban@wne.edu QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 Build Identifier: On two different SuSE 13.1 x86_64 systems, systemd segfaults several hours after installing: systemd-208-28.1.x86_64.rpm systemd-32bit-208-28.1.x86_64.rpm systemd-rpm-macros-2-28.1.noarch.rpm systemd-sysvinit-208-28.1.x86_64.rpm ... var/log/messages contains: kernel: [680150.869695] systemd[1]: segfault at 137a7020 ip 000000000040e526 sp 00007fffd861c290 error 4 in systemd[400000+ed000] systemd[1]: Caught <SEGV>, dumped core as pid 32253. systemd[1]: Freezing execution Going back to v208-23.3 seems to solve the problem. The first symptom that made me notice this problem is that thousands of defunct processes accumulate on the system. I tried running gdb against the coredump file, but am not sure how much value this will be due to lack of symbol table information: # gdb /bin/systemd core Reading symbols from /usr/lib/systemd/systemd...Missing separate debuginfo for /usr/lib/systemd/systemd Try: zypper install -C "debuginfo(build-id)=14e9c2ba2f551a445f792d053a7f9dc593a60a2e" (no debugging symbols found)...done. [New LWP 32253] Core was generated by `/usr/lib/systemd/systemd --system --deserialize 20'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f5644b2d8cb in ?? () (gdb) backtrace #0 0x00007f5644b2d8cb in ?? () #1 0x000000000040cbcb in ?? () #2 0x00007f5644b2d9f0 in ?? () #3 0x0000000000000001 in ?? () #4 0x0000000000000000 in ?? () If anyone can provide a link as to how to get symbol table information, I'll certainly try to get it. The suggested zypper command doesn't help without the missing repository: # zypper install -C "debuginfo(build-id)=14e9c2ba2f551a445f792d053a7f9dc593a60a2e" Loading repository data... Reading installed packages... No provider of 'debuginfo(build-id) = 14e9c2ba2f551a445f792d053a7f9dc593a60a2e' found. Resolving package dependencies... Nothing to do. Reproducible: Always Steps to Reproduce: 0. HAPPENS EVERY TIME ON SOME COMPUTERS AFTER SEVERAL HOURS OR OVERNIGHT 1. Install systemd 208-28.1 2. wait several hours (overnight) 3. grep segfault /var/log/messages Actual Results: - systemd segfault message in /var/log/messages - ps -ef | grep defunct | wc -l 8992 - cron jobs don't run: systemd-logind[10804]: Failed to start session scope session-7576.scope: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. org.freedesktop.DBus.Error.NoReply /usr/sbin/cron[32297]: pam_systemd(crond:session): Failed to create session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. 2015-02-16T09:41:03.642884-05:00 iggy dbus[920]: [system] Reloaded configuration /usr/sbin/cron[32296]: pam_systemd(crond:session): Failed to create session: Input/output error Expected Results: did not expect to see segfault message in /var/log/messages, or thousands of defunct processes. I have two computers exhibiting this problem: One system exhibiting this problem is an email server running kernel 3.11.10-25-default in multiuser text mode (not running X11). The other computer is running KDE and is my desktop computer running kernel 3.11.10-25-desktop with NVIDIA-Linux-x86_64-346.35.run. Another system running in text mode does not exhibit the problem at all (at least not yet). Thank you for looking into this!! Please let me know if I can be of further assistance. -- You are receiving this mail because: You are on the CC list for the bug.