systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
pitti, bug 1433320 seems still not be fixed on my QEMU VM ...
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: udev 225-1ubuntu7
ProcVersionSign
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CustomUdevRuleF
Date: Fri Oct 9 22:02:21 2015
ExecutablePath: /lib/systemd/
ExecutableTimes
InstallationDate: Installed on 2015-03-25 (204 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcCmdline: /lib/systemd/
ProcCwd: /
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: systemd
StacktraceTop:
__epoll_
?? ()
?? ()
?? ()
__libc_start_main (main=0x55e387f
Title: systemd-udevd crashed with SIGABRT in __epoll_
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.
dmi.modalias: dmi:bvnSeaBIOS:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.
dmi.sys.vendor: QEMU
Changed in systemd (Ubuntu): | |
status: | Confirmed → Won't Fix |
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 #1506801, 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.