Coping image to Micro SD card with dd and on completion seen systemd-udevd crashed with SIGABRT in __open_nocancel()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I was coping the same image as in bug 1665020 onto another SD card and I again saw an error when it completed.
$ sudo dd bs=4M if=2016-
[sudo] password for user:
422+1 records in
422+1 records out
1772094464 bytes (1.8 GB, 1.7 GiB) copied, 297.19 s, 6.0 MB/s
user@machine:
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu16
ProcVersionSign
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CrashCounter: 1
CustomUdevRuleF
Date: Wed Feb 15 16:38:13 2017
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2015-03-12 (705 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V
ProcCmdline: /lib/systemd/
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: systemd
StacktraceTop:
__open_nocancel () at ../sysdeps/
?? ()
?? ()
?? ()
?? ()
Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 08/11/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F6
dmi.board.
dmi.board.name: H81M-DS2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: H81M-DS2V
dmi.product.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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.