Comment # 25 on bug 918158 from
(In reply to Ivan Topolsky from comment #24)
> Created attachment 626122 [details]
> 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.

Thanks, this time I have the full backtrace and I can see that it crashes in a
hashmap removal function:

-->---
#3  unlink_entry (h=h@entry=0x7f8de5ea8120, e=e@entry=0x7f8de5f2ffe0, hash=9)
at src/shared/hashmap.c:291
291                    e->bucket_previous->bucket_next = e->bucket_next;
--<--

e->bucket_previous is invalid:

-->--
(gdb) print e->bucket_previous
$6 = (struct hashmap_entry *) 0xf2fe0000
(gdb) print *e->bucket_previous
Cannot access memory at address 0xf2fe0000
--<--

Continuning investigation.


You are receiving this mail because: