systemd-resolved crashed with SIGABRT in log_assert_failed()

[Walter Garcia-Fontes]

I got this crach just after logged in after the last kernel upgrade

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 231-6git1
ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
Uname: Linux 4.8.0-15-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 25 18:53:47 2016
ExecutablePath: /lib/systemd/systemd-resolved
InstallationDate: Installed on 2013-11-28 (1032 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. Latitude E6530
ProcCmdline: /lib/systemd/systemd-resolved
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-16-generic root=UUID=409b2104-0062-403c-8b6b-f07948051f69 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 log_assert_failed () from /lib/systemd/libsystemd-shared-231.so
 ?? ()
 ?? ()
 ?? () from /lib/systemd/libsystemd-shared-231.so
 sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
Title: systemd-resolved crashed with SIGABRT in log_assert_failed()
UpgradeStatus: Upgraded to yakkety on 2016-08-31 (25 days ago)
UserGroups:

dmi.bios.date: 08/27/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 07Y85M
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA13:bd08/27/2013:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6530
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

[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 #1607884, 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.