kerneloops crashed with SIGABRT in __assert_fail_base()

Bug #1026300 reported by Martijn vdS
90
This bug affects 14 people
Affects Status Importance Assigned to Milestone
kerneloops (Ubuntu)
Fix Released
Medium
Brian Murray

Bug Description

Errors bucket: https://errors.ubuntu.com/problem/dc69a3b514edf9e764bb8e0798e7c0ae78868fd2

There are about 50 instances of this on Trusty as of 2014-03-05.

I have no idea what caused this. I just got a pop-up out of nowhere complaining about a system error.

ProblemType: CrashDistroRelease: Ubuntu 12.10
Package: kerneloops-daemon 0.12+git20090217-3ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5
Uname: Linux 3.5.0-3-generic x86_64
ApportVersion: 2.4-0ubuntu2
Architecture: amd64
Date: Wed Jul 18 20:46:43 2012
ExecutablePath: /usr/sbin/kerneloops
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803)
ProcCmdline: /usr/sbin/kerneloops
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
Signal: 6SourcePackage: kerneloops
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
Title: kerneloops crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2011-12-03 (228 days ago)
UserGroups:

Revision history for this message
Martijn vdS (martijn) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=0x403fbb "c9", file=0x403f94 "dmesg.c", line=<optimized out>, function=<optimized out>) at assert.c:94
 __GI___assert_fail (assertion=assertion@entry=0x403fbb "c9", file=file@entry=0x403f94 "dmesg.c", line=line@entry=86, function=function@entry=0x4042b0 "fill_lineinfo") at assert.c:103
 fill_lineinfo (remove_syslog=0, buflen=<optimized out>, buffer=<optimized out>) at dmesg.c:86
 extract_oops (buffer=buffer@entry=0x12c2800 "<5>[1168458.796871] type=1701 audit(1342634220.417:14246): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=14260 comm=\"chrome\" reason=\"seccomp\" sig=0 syscall=2 compat=0 ip=0x7f081ba34257 code=0x5"..., buflen=<optimized out>, remove_syslog=remove_syslog@entry=0) at dmesg.c:167
 scan_dmesg (unused=<error reading variable: value has been optimized out>) at dmesg.c:368

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in kerneloops (Ubuntu):
importance: Undecided → Medium
summary: - kerneloops crashed with SIGABRT in raise()
+ kerneloops crashed with SIGABRT in __assert_fail_base()
tags: removed: need-amd64-retrace
tags: added: running-unity
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in kerneloops (Ubuntu):
status: New → Confirmed
visibility: private → public
Revision history for this message
Karma Dorje (taaroa) wrote :

Apport has detected a possible GPU hang. Did your system recently lock up and/or require a hard reboot?

Revision history for this message
Martijn vdS (martijn) wrote :

Haven't had that for a long time (since before 12.04)

C de-Avillez (hggdh2)
tags: added: qa-manual-testing
Revision history for this message
Bryce Harrington (bryce) wrote :

The user also reported 1026522 as a false gpu lockup subsequent to filing this bug.

Para Siva (psivaa)
tags: added: rls-q-incoming
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This bug hasn't had any comments in some time. Are you still seeing this bug on the latest release of Quantal?

Changed in kerneloops (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
C de-Avillez (hggdh2) wrote :

I have not seen it again on latest kernels.

Revision history for this message
Brian Murray (brian-murray) wrote :

hggdh2 - that's probably because kerneloops is disabled because it was crashing. try manually starting it and see what happens.

Revision history for this message
C de-Avillez (hggdh2) wrote :

Heh. Done, thanks. Now we wait again.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for kerneloops (Ubuntu) because there has been no activity for 60 days.]

Changed in kerneloops (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Vincent Gerris (vgerris) wrote :

I had this on 14.04 dev release today and was directed here?

Changed in kerneloops (Ubuntu):
status: Expired → Triaged
description: updated
tags: added: trusty
Changed in kerneloops (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Brian Murray (brian-murray)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kerneloops - 0.12+git20090217-3ubuntu5

---------------
kerneloops (0.12+git20090217-3ubuntu5) trusty; urgency=medium

  [ Colin King ]
  * fix memleak and add alloc null pointer checks (LP: #1287109)
    - memleak of buffer c in writefunction()
    - null pointer checks in extract_oops() and scan_dmesg() (LP: #1026251)

  [ Brian Murray ]
  * fix null pointer check in fill_lineinfo() (LP: #1026300)
 -- Brian Murray <email address hidden> Wed, 05 Mar 2014 08:58:57 -0800

Changed in kerneloops (Ubuntu):
status: In Progress → Fix Released
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.