systemd-udevd crashed with SIGABRT in ioctl()

[Danial Behzadi]

Crashes on every boot!

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: udev 231-7
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-16-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CustomUdevRuleFiles: 70-snap.ubuntu-core.rules 79-samsung.rules 20-mm-blacklist-mtk.rules
Date: Wed Sep 28 19:51:24 2016
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2015-04-24 (525 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 2349KEG
ProcCmdline: /lib/systemd/systemd-udevd
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic root=UUID=a1abeb16-2852-43c8-8d5b-330faa072bf8 ro ipv6.disable=1 quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 ioctl () at ../sysdeps/unix/syscall-template.S:84
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: systemd-udevd crashed with SIGABRT in ioctl()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ETB0WW (2.70 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2349KEG
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2349KEG
dmi.product.version: ThinkPad T430
dmi.sys.vendor: LENOVO

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