systemd-resolved crashed with SIGSEGV

Bug #1621316 reported by Danial Behzadi
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Crashed in startup.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 231-5
ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5
Uname: Linux 4.6.0-10-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Thu Sep 1 16:45:25 2016
ExecutablePath: /lib/systemd/systemd-resolved
InstallationDate: Installed on 2015-04-24 (502 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 2349KEG
ProcCmdline: /lib/systemd/systemd-resolved
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-10-generic root=UUID=a1abeb16-2852-43c8-8d5b-330faa072bf8 ro ipv6.disable=1 quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x5648282051f6: mov 0x8(%rdi),%eax
 PC (0x5648282051f6) ok
 source "0x8(%rdi)" (0x00000099) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: systemd
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: systemd-resolved crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ETB0WW (2.70 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2349KEG
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2349KEG
dmi.product.version: ThinkPad T430
dmi.sys.vendor: LENOVO

Revision history for this message
Danial Behzadi (dani.behzi) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 dns_search_domain_unref (d=0x91) at ../src/resolve/resolved-dns-search-domain.c:100
 dns_query_reset_answer.lto_priv.106 (q=0x56482938fbb0) at ../src/resolve/resolved-dns-query.c:381
 dns_query_free.part.12 (q=0x56482938fbb0) at ../src/resolve/resolved-dns-query.c:402
 dns_query_free () at ../src/resolve/resolved-dns-query.c:384
 dns_stub_query_complete (q=0x56482938fbb0) at ../src/resolve/resolved-dns-stub.c:232

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in systemd (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Steve Beattie (sbeattie)
information type: Private → Public
Revision history for this message
Steve Langasek (vorlon) wrote :

Thank you for reporting this issue and helping to improve Ubuntu.

This bug was reported against the version of systemd in Ubuntu 16.10, which has reached End Of Life. As such, we will not be fixing bugs in this version of the package. If this problem is reproducible on later supported versions of Ubuntu, please open a new bug (preferably with a fresh backtrace and crashdump) against that version.

Changed in systemd (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.