systemd-udevd crashed with SIGABRT in ioctl()

[cecilpierce]

?

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: udev 225-1ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-10.10-generic 4.2.0
Uname: Linux 4.2.0-10-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Date: Fri Sep 11 10:36:15 2015
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2015-08-16 (25 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816)
Lsusb:
 Bus 001 Device 008: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
 Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Compaq Presario 061 EX318AA-ABA SR1920NX NA630
ProcCmdline: /lib/systemd/systemd-udevd
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda1 ro quiet splash
Signal: 6
SourcePackage: systemd
StacktraceTop:
 ioctl () at ../sysdeps/unix/syscall-template.S:81
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: systemd-udevd crashed with SIGABRT in ioctl()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 09/19/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.11
dmi.board.name: NAGAMI2L
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 2.00
dmi.chassis.type: 3
dmi.chassis.version: 1111
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.11:bd09/19/2006:svnCompaqPresario061:pnEX318AA-ABASR1920NXNA630:pvr0nx1411RE101NAG2L00:rvnASUSTekComputerINC.:rnNAGAMI2L:rvr2.00:cvn:ct3:cvr1111:
dmi.product.name: EX318AA-ABA SR1920NX NA630
dmi.product.version: 0nx1411RE101NAG2L00
dmi.sys.vendor: Compaq Presario 061

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