Comment # 41 on bug 918158 from Thomas Blume

(In reply to Ivan Topolsky from comment #39)
> Created attachment 633326 [details]
> rsyslog (xz-compresesd)
> 
> I just realized that, as systemd has crashed, journald would be missing some
> parts. (systemd's segfault isn't in there).
> 
> Here's rsyslog's output in /var/log/messages of the same time frame.

Uh, there are more processes that show segfaults:

-->--
grep segfault log.20150430.rs 
2015-04-29T02:43:17.104174+02:00 argo kernel: [420779.641913]
Chrome_ChildThr[24640]: segfault at 0 ip 00007f8410d57d6e sp 00007f83ff3ec440
error 6 in libmozalloc.so;553fb361 (deleted)[7f8410d55000+5000]
2015-04-29T02:43:58.943174+02:00 argo kernel: [420821.508383] python[32479]:
segfault at 85c70008 ip 00007f47b484d280 sp 00007ffe9ef8db48 error 4 in
libpython2.7.so.1.0[7f47b4776000+161000]
2015-04-29T02:43:59.221291+02:00 argo kernel: [420821.786844]
bitcoin-opencon[919]: segfault at 12f8fae8 ip 00007fce6215ee4e sp
00007fce2b3037e8 error 4 in libc-2.19.so[7fce620cf000+19e000]
2015-04-30T19:03:43.860876+02:00 argo kernel: [541390.712732] systemd[1]:
segfault at 4a800150 ip 000000000049c1d0 sp 00007ffcb5a303d0 error 4 in
systemd[400000+116000]
2015-04-30T19:58:00.969919+02:00 argo kernel: [544649.967254]
akonadi_agent_l[18453]: segfault at 0 ip 00007fc27e62f150 sp 00007ffdab57b690
error 4 in libQtDBus.so.4.8.6[7fc27e616000+7b000]
2015-04-30T19:58:00.971273+02:00 argo kernel: [544649.967966]
akonadi_agent_l[18436]: segfault at 1200000018 ip 00007f7ddd506bf8 sp
00007ffe84c6e2c0 error 4 in libc-2.19.so[7f7ddd48e000+19e000]
2015-04-30T19:58:01.505877+02:00 argo kernel: [544650.503186] python[19344]:
segfault at 764d0000 ip 00007fa442b95e29 sp 00007ffecf185050 error 4 in
libpython2.7.so.1.0[7fa442adf000+161000]
2015-04-30T19:58:42.586285+02:00 argo kernel: [544691.609727] python[19430]:
segfault at 85c70008 ip 00007fa442bb6280 sp 00007ffecf185458 error 4 in
libpython2.7.so.1.0[7fa442adf000+161000]
--<--

All of them with error 4 or 6 suggesting that there are pointers to invalid
memory addresses.
It is quite unlikely that the code in all of these programs is buggy.
If your physical RAM isn't broken, something else is silently corrupting your
memory.