systemd-journald crashed with SIGABRT in timerfd_settime()

[Till Kamppeter]

.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 230-5
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.2-0ubuntu1
Architecture: amd64
Date: Sun Jul 3 09:22:25 2016
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2015-03-25 (466 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcCmdline: /lib/systemd/systemd-journald
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 timerfd_settime () at ../sysdeps/unix/syscall-template.S:84
 ?? () from /lib/systemd/libsystemd-shared-230.so
 sd_event_prepare () from /lib/systemd/libsystemd-shared-230.so
 sd_event_run () from /lib/systemd/libsystemd-shared-230.so
 ?? ()
Title: systemd-journald crashed with SIGABRT in timerfd_settime()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-vivid
dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-vivid:cvnQEMU:ct1:cvrpc-i440fx-vivid:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-vivid
dmi.sys.vendor: QEMU

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1593013, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.