systemd-resolved crashed with SIGSEGV in on_query_timeout.lto_priv.104()

Bug #1620378 reported by PeterPall
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I just got this error. Don't know what triggered it as I wasn't doing anything special. Also I don't see that this error caused any problem besides apport popping up.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 231-5
Uname: Linux 4.8.0-040800rc4-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 5 09:27:40 2016
ExecutablePath: /lib/systemd/systemd-resolved
MachineType: Acer Aspire S7-391
ProcCmdline: /lib/systemd/systemd-resolved
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-040800rc4-lowlatency root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable quiet splash acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x5629512de2f0: and %bh,%cl
 PC (0x5629512de2f0) in non-executable VMA region: 0x5629512d4000-0x5629513c7000 rw-p [heap]
 source "%bh" ok
 destination "%cl" ok
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: systemd
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /lib/systemd/libsystemd-shared-231.so
 sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
 sd_event_run () from /lib/systemd/libsystemd-shared-231.so
Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/16/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.09
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Storm
dmi.board.vendor: Acer
dmi.board.version: V2.09
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.09
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
dmi.product.name: Aspire S7-391
dmi.product.version: V2.09
dmi.sys.vendor: Acer

Revision history for this message
PeterPall (peterpall) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 on_query_timeout.lto_priv.104 (s=<optimized out>, usec=<optimized out>, userdata=<optimized out>) at ../src/resolve/resolved-dns-query.c:564
 source_dispatch.lto_priv.92 (s=0x5629513005f0) at ../src/libsystemd/sd-event/sd-event.c:2275
 sd_event_dispatch (e=e@entry=0x5629512d8240) at ../src/libsystemd/sd-event/sd-event.c:2626
 sd_event_run (e=e@entry=0x5629512d8240, timeout=timeout@entry=18446744073709551615) at ../src/libsystemd/sd-event/sd-event.c:2685

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
summary: - systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
+ systemd-resolved crashed with SIGSEGV in on_query_timeout.lto_priv.104()
tags: removed: need-amd64-retrace
Steve Beattie (sbeattie)
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
angel (correoparaangel)
Changed in systemd (Ubuntu):
status: Confirmed → Fix Released
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.