[Bug 1304676] Re: init crashed with SIGSEGV

John A. Lewis 1304676 at bugs.launchpad.net
Fri Apr 11 17:04:35 UTC 2014


I do have a crash file, but do not have a state file. Unfortunately,
Launchpad is throwing an error message when I try to attach the file to
this comment. :(

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1304676

Title:
  init crashed with SIGSEGV

Status in “upstart” package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1304676/+subscriptions



More information about the foundations-bugs mailing list