systemd-udevd crashed with SIGABRT in __recvmsg_nocancel()

[howefield]

systemd-udevd crashed with SIGABRT in __recvmsg_nocancel()

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: udev 228-4ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
Uname: Linux 4.3.0-7-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.19.4-0ubuntu1
Architecture: amd64
CustomUdevRuleFiles: 60_smfpautoconf_samsung.rules 61_smfpautoconf_samsung.rules
Date: Sat Jan 30 12:35:00 2016
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2016-01-26 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
MachineType: Dell Inc. Inspiron N5010
ProcCmdline: /lib/systemd/systemd-udevd
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-7-generic root=UUID=8e9b8370-51db-43b0-9d96-b7120e6e69f5 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __recvmsg_nocancel () at ../sysdeps/unix/syscall-template.S:81
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: systemd-udevd crashed with SIGABRT in __recvmsg_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/25/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0YXXJJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn0YXXJJ:rvrA12:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Inspiron N5010
dmi.product.version: A12
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 #1499171, 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.