Ubuntu
systemd package

systemd-logind crashed with SIGSEGV in __strlen_ia32()

Bug #1499863 reported by Arno Waschk on 2015-09-25

This bug report is a duplicate of: Bug #1495178: Failed to set wall message, ignoring: Message recipient disconnected from message bus without replying. Edit Remove

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	systemd (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

during startup

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
Uname: Linux 4.2.0-10-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.18.1-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Thu Sep 24 01:35:05 2015
ExecutablePath: /lib/systemd/systemd-logind
InstallationDate: Installed on 2012-03-15 (1289 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120312)
MachineType: Dell Inc. Vostro 3300
ProcCmdline: /lib/systemd/systemd-logind
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic root=UUID=6dfe08c1-e85f-4ec7-9bc6-d020b3958d5c ro quiet splash vt.handoff=7
SegvAnalysis:
Segfault happened at: 0xb75d16f1 <__strlen_ia32+49>: mov (%eax),%ecx
PC (0xb75d16f1) ok
source "(%eax)" (0x80000000) not located in a known VMA region (needed readable region)!
destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: systemd
StacktraceTop:
__strlen_ia32 () at ../sysdeps/i386/i686/multiarch/../../i586/strlen.S:94
__GI___strdup (s=0x80000000 <error: Cannot access memory at address 0x80000000>) at strdup.c:41
?? ()
?? ()
?? ()
Title: systemd-logind crashed with SIGSEGV in __strlen_ia32()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 10/25/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 07JC8T
dmi.board.vendor: Dell Inc.
dmi.board.version: A10
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A10
dmi.modalias: dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn07JC8T:rvrA10:cvnDellInc.:ct8:cvrA10:
dmi.product.name: Vostro 3300
dmi.product.version: A10
dmi.sys.vendor: Dell Inc.

Tags:

Revision history for this message

Arno Waschk (bug-ubuntu) wrote on 2015-09-25:

CurrentDmesg.txt Edit (88.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (892 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (49.6 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (32.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (654 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.9 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (4.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (831 bytes, text/plain; charset="utf-8")
Registers.txt Edit (488 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")
SystemdDelta.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (147.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (330.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2015-09-25:

StacktraceTop:
__strlen_ia32 () at ../sysdeps/i386/i686/multiarch/../../i586/strlen.S:94
__GI___strdup (s=0x80000000 <error: Cannot access memory at address 0x80000000>) at strdup.c:41
free_and_strdup (p=0x8080a0c4, s=0x80000000 <error: Cannot access memory at address 0x80000000>) at ../src/basic/util.c:6023
method_set_wall_message.lto_priv.424 (message=0x8081a810, userdata=0x8080a008, error=0xbfd6d074) at ../src/login/logind-dbus.c:2321
method_callbacks_run (found_object=0xbfd6d14c, require_fallback=<optimized out>, c=0x8080ead0, m=0x8081a810, bus=0x8080c368) at ../src/libsystemd/sd-bus/bus-objects.c:410

Revision history for this message

Apport retracing service (apport) wrote on 2015-09-25: Stacktrace.txt

Stacktrace.txt Edit (3.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2015-09-25: StacktraceSource.txt

StacktraceSource.txt Edit (7.9 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2015-09-25: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (3.5 KiB, text/plain)

Changed in systemd (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-09-29:

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

Changed in systemd (Ubuntu):
status:	New → Confirmed

Martin Pitt (pitti) on 2015-09-29

information type:

Private → Public

Revision history for this message

Nicholas Sharp (nsharpent) wrote on 2015-09-29:

This may be something the devs already caught; but if I'm reading my logs correctly, the crash seems to be actually occurring during the service recycling procedure at shutdown. Just thought I'd point that out.

Revision history for this message

Mario Chamorro (mochaman) wrote on 2015-09-30:

A minor comment that the bug didn't really affect me. The laptop started up slowly and then displayed the crash dialog when I logged in. I did not personally see any effects of this bug.