http://bugzilla.opensuse.org/show_bug.cgi?id=918158 Martin Pluskal changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpluskal@suse.com Assignee|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=918158 Stefan Botter changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsj@jsj.dyndns.org -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=918158 --- Comment #14 from Ivan Topolsky --- Created attachment 624300 --> http://bugzilla.opensuse.org/attachment.cgi?id=624300&action=edit systemd core dump core dump from systemd 210-25.12.1 (the stock one from the official "OpenSuse 13.2 Update" repository) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=918158 --- Comment #21 from Ivan Topolsky --- Created attachment 625063 --> http://bugzilla.opensuse.org/attachment.cgi?id=625063&action=edit systemd core dump (xz-compressed) New coredump of systemd (this time xz-compressed because of the 10MiB limitations on bugzilla). I did upgrade system to the 210-25.15.1 version found in the tsaupe home repo. It did crash during one update. Given the sequence of message in the terminal, it probably crashed during the installation of VirtualBox. I would imaging: restarting which ever unit is responsible of the host drivers (the modern systemd equivalent of /etc/init.d/vboxdrv ). I haven't installed the debugs symbols, but according to gdb's backtrace it crash on a "free" call. Double free? Free of corrupt buffer ? Seems problematic. (Even when exposed to corrupt data, systemd should handle it gracefully and report an error. Not barf and crash on it) Today, I noticed a new 210-25.15.2 version was available. We'll see how this one survives. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=918158 --- Comment #24 from Ivan Topolsky --- Created attachment 626122 --> http://bugzilla.opensuse.org/attachment.cgi?id=626122&action=edit systemd core dump (xz-compressed) Again crash. As usual: during a system update (to be precies during VirtualBox's update, at the moment the corresponding unit is reloaded). It's still the 210-25.15.2 version from tsauppe repository A different unit is the one causing the crash, this time the Swap device. I've double checked: - no file installed by the RPMs is reported to fail checksum (beside a few unrelated configuration that I might have edited) - there are no funny package (e.g.: left-over from before the upgrades, like consolekit) when comparing to a freshly installed machine - nearly all the files in /usr/bin ../sbin ../lib ../lib64 come from RPMs (I very well know the few files not accounted for) The system should be clean. I really doubt that there's something else causing the crash. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=918158 --- Comment #29 from Ivan Topolsky --- Created attachment 629235 --> http://bugzilla.opensuse.org/attachment.cgi?id=629235&action=edit 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. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=918158 --- Comment #34 from Ivan Topolsky --- Created attachment 632025 --> http://bugzilla.opensuse.org/attachment.cgi?id=632025&action=edit systemd core dump (xz-compressed) Well, got "lucky": did manage to gather a core dump, not too long after moving to your version of systemd (without all the "symbol otpmized out") These kind of weird mis-behaviour are still exclusively happenning after suspend-to-ram/wake up cycles. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=918158 --- Comment #38 from Ivan Topolsky --- Created attachment 633318 --> http://bugzilla.opensuse.org/attachment.cgi?id=633318&action=edit full log since reboot (xz-compressed) Full system log since last boot associated with crash from dump #633311 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=918158 --- Comment #43 from Ivan Topolsky ---

...

RAM corruption is thus very unlikely It becomes more and more likely ...

I still don't buy dammage RAM sticks, as I've tried again memtest86+ for extended periods of time and still no reported problem. I'll side with Thomas on that one.

The question is: do you have any optimization around, that is e.g. preloaded libraries (echo $LD_LIBRARY_PATH $LD_PRELOAD) for the used CPU/chipset and/or selfcompiled and/or third party kernel,

No, the installation is stock. I use my laptop in production and thus haven't optimized much.

third party modules

*That* is what I've been thinking too. Two third party modules : - Nvidia closed source kernel driver. And unlike their good reputation on laptops, Nvidia binary on laptops are usually very problematic. (All the laptops I've been through display random texture corruption, problems text-mode console as they don't do KMS, etc. it's far from being specific to that laptop. Seems more likely that Nvidia concentrates their effort at supporting Desktop/Workstation on Linux and neglect laptops, see the debacle around Optimus) As Nvidia has moved to G04 and excluded my chip from that set, I've switched to opensource Nouveau driver. All the segfaults that happen here and there happen AFTER this switch. (Although I don't have texture corruption anymore. The only problem I have is that the very specific kernel version that opensuse uses, the 3.16 has a bug that prevents nouveau from completely shutting down the backlight when putting the screen in DPMS OFF) - WL restricted source driver for the broadcom WiFi b/g/N mini-PCIe card built-in by Dell. That's what opensuse installed by default back when I acquired this laptop. Back then I tried experimenting with alternative, but b43 was reverse engineered and was missing a lot of feature, and the brdcmsmac opensource driver was too new, and had speed problems (missing 5Ghz, speed droping to 10mbits on 2.5Ghz N). I've noticed in the logs that the wl driver makes the kernel spit messages. As nowadays brcmsmac seems to be in much better shape (only power saving, AP mode and some special channel mode are missing- N is fully functionning, including at 5Ghz), I'll try switching and see if the machine becomes stabler. That's also the main difference between this problematic laptop (has BCM wireless) and the older laptops (external Wifi PC-CARD that I plug when I actually need it) and other destkop/Workstations I use (no Wifi).

Also which modules are unloaded before hibernate/suspend and reload afterwards if any ?

I there a cannonical way to list them ? I would suspect the USB drivers. Currently, the bluetooth (BCM5880) is wired over USB in the laptop, and I have a USB-using microSD reader mini card. They use stock kernel drivers. Also, last but not least: ACPI is of course also 3rd party (byte) code running here. Not sure if I can do anything about that one (BIOS/Firmware from Dell is up-to-date). I'll see what I can do. If the segfaults disappear, It might have been the BCM restricted source driver sliently corrupting the rest. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=918158 --- Comment #46 from Ivan Topolsky --- @Thomas: Yesterday's update from your repository produces "Invalid Hash Bucket Pointer" upon attempts to log in. Reversing to stock opensuse systemd fixes the problem. @Werner: Any further pointers for that direction: - lists with known good/bad drivers ? - recommendation what to put in my /etc/pm/sleep.d ? -- You are receiving this mail because: You are on the CC list for the bug.