systemd-udevd crashed with SIGABRT in __open_nocancel()

[hms]

systemd crashes when writing zeroes to usb stick

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: udev 229-3ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-16.32-lowlatency 4.4.6
Uname: Linux 4.4.0-16-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CustomUdevRuleFiles: 79-udev-epson.rules 60-vboxdrv.rules 55-Argyll.rules
Date: Wed Apr 6 23:27:35 2016
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2015-11-07 (151 days ago)
InstallationMedia: Ubuntu-Studio 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcCmdline: /lib/systemd/systemd-udevd
ProcEnviron:
 LANG=fi_FI.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-lowlatency root=UUID=72391ac8-8397-480f-af5a-267c24cd024c ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __open_nocancel () at ../sysdeps/unix/syscall-template.S:84
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 10/23/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F15
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B75M-D3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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