Comment # 29 on bug 918158 from Ivan Topolsky

Created attachment 629235 [details]
systemd core dump (xz-compressed)

> Also I'd like to know if this also happens with systemd-210 from
> Base:System:Legacy as there are a lot of upstram bug fixes included.

Things were stable for quite some time including going through a few updates
flawlessly, so seemingly my problems have been solved. But then, systemd
crashed again, and this time simply as I was hitting "tab" in bash to
autocomplete the name of a service to be restarted (dnsmasq.service, I think).

> Do you have some optimization
> enabled in the CMOS/BIOS setup that is timing of RAM and/or cache lines?
> Which kind of RAM this is with or without ECC?

It's a Dell Lattitude E6510 laptop running 2x4GB non-ECC RAM from Crucial.

As with most professionnal "enterprise"-y laptops, there aren't much RAM
configuration in the BIOS. The only settings I've changed was turning on EFI
boot a few months back when I've moved my system to a SSD.

I have been running memtest86+ scan for several hours without any reported
problem.

Also, the only affected software are: 
- systemd, which in a few rare occasions segfaults when receiving resquest on
the DBus (usually requests to restart services, but the other day's was simply
answering to an autocomplete bash plugin).
- a few KDE application, which could segfault when quitting, or a few of them
when waking from suspend-to-ram (either a problem while freeing a memory
buffer, or a pointer problem when handling an event received from glib).

These are the only problems I've noticed. None of the remaining software I run
has any problems (I can edit images with GIMP, compile software with GCC, the
background services are running fine, etc. all without crash). I've had RAM
problems in another machine in the past, and the behaviour is completely
different (after a while, random crashes happens, affecting nearly any
program). This isn't the case on the laptop.