systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
not sure what happened, the error screen pops up without any active program crashing or anything else visible happening.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 231-5
ProcVersionSign
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 11 14:06:30 2016
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2013-06-06 (1193 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Dell Inc. Dell System XPS L322X
ProcCmdline: /lib/systemd/
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x5558e9d5c257: cmpl $0x1,0x4(%rax)
PC (0x5558e9d5c257) ok
source "$0x1" ok
destination "0x4(%rax)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: systemd
StacktraceTop:
?? ()
?? ()
?? () from /lib/systemd/
sd_event_dispatch () from /lib/systemd/
sd_event_run () from /lib/systemd/
Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
UpgradeStatus: Upgraded to yakkety on 2016-09-03 (8 days ago)
UserGroups:
dmi.bios.date: 04/18/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0PJHXN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Dell System XPS L322X
dmi.sys.vendor: Dell Inc.
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 #1621396, 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.