init crashed with SIGSEGV

Bug #1304676 reported by Maya R. Odinezenko
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I log into Ubuntu 14.04 and immediately am told there was an internal system error.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: upstart 1.12.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-21-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
Date: Wed Apr 2 15:22:35 2014
Disassembly: => 0x7f940930a4d7: Cannot access memory at address 0x7f940930a4d7
ExecutablePath: /sbin/init
InstallationDate: Installed on 2014-03-29 (10 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
ProcCmdline: /sbin/init
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=592d2ff1-746b-43fe-807d-5cec5658b0a1 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet
SegvAnalysis:
 Segfault happened at: 0x7f940930a4d7: Cannot access memory at address 0x7f940930a4d7
 PC (0x7f940930a4d7) not located in a known VMA region (needed executable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: upstart
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
Title: init crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningSystemVersion: init (upstart 1.12.1)
UserGroups:

modified.conffile..etc.default.cups: [modified]
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.default.cups: 2014-03-26T13:38:44
mtime.conffile..etc.pulse.default.pa: 2014-03-29T14:40:34.180833

Revision history for this message
Maya R. Odinezenko (maya923) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x00007f940930a4d7 in ?? ()
 #1 0x0000000000000020 in ?? ()
 #2 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in upstart (Ubuntu):
status: New → Confirmed
Revision history for this message
James Hunt (jamesodhunt) wrote :

@John - do you have a crash file or a state file (/var/crash/_sbin_init.*.crash or /var/log/upstart/upstart.state)? If so, please can you attach them to this bug.

Revision history for this message
John A. Lewis (pointful) wrote :

Here is the crash file. (Got the upload working.) Do not have a state file.

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.