[Bug 1300235] Re: init crashed with SIGSEGV

James Hunt 1300235 at bugs.launchpad.net
Mon Jun 23 08:31:40 UTC 2014


Jeremie and Peter - thanks for attaching the crash files, but like the
others affected the core file encoded inside '_sbin_init.0.crash'  were
generated by chrome / chromium-browser so we cannot use these to debug
the system crash. There seems to be some strange interaction between
chrome, upstart, the kernel and apport but without further information
or the ability to reproduce the problem we can't investigate further.

To those affected, you may want to consider either running the packaged
version of chromium-browser in Ubuntu, or using a different browser
entirely, or even running chrome inside an unprivileged LXC container as
documented here:

https://www.stgraber.org/2014/02/09/lxc-1-0-gui-in-containers/

-- 
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/1300235

Title:
  init crashed with SIGSEGV

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 31 09:53:16 2014
  Disassembly: => 0x7fa2b65e94d7:	Cannot access memory at address 0x7fa2b65e94d7
  ExecutablePath: /sbin/init
  InstallationDate: Installed on 2014-03-05 (25 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140305)
  ProcCmdline: /sbin/init
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7fa2b65e94d7:	Cannot access memory at address 0x7fa2b65e94d7
   PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable region)!
   Stack pointer not within 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]
  mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893

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



More information about the foundations-bugs mailing list