That's high ranked on the e.u.c trusty issues

The issue started with 0.12+git20090217-3ubuntu4 it seems (which is when
kerneloops get enabled in trusty, so it's probably not due to changes in
that version)

** Changed in: kerneloops (Ubuntu)
   Importance: Medium => High

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kerneloops in Ubuntu.

  kerneloops crashed with SIGSEGV in _int_malloc()

Status in “kerneloops” package in Ubuntu:

Bug description:
  when ejecting a flash drive

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: kerneloops-daemon 0.12+git20090217-3ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Mon Mar  3 21:26:30 2014
  ExecutablePath: /usr/sbin/kerneloops
  InstallationDate: Installed on 2014-02-14 (16 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211)
  ProcCmdline: /usr/sbin/kerneloops
   PATH=(custom, no user)
   Segfault happened at: 0x7f899491a231 <_int_malloc+2337>:     mov    
   PC (0x7f899491a231) ok
   source "%r13" ok
   destination "(%rax,%r13,1)" (0x6b736964227bbcf0) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: kerneloops
   _int_malloc (av=0x7f8994c58760 <main_arena>, bytes=16000) at malloc.c:3740
   __GI___libc_malloc (bytes=16000) at malloc.c:2891
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/
  Title: kerneloops crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to