Bug 1074141 - [abrt] ODEBUG: 18 of 18 active objects replaced
Summary: [abrt] ODEBUG: 18 of 18 active objects replaced
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:da39a3ee5e6b4b0d3255bfef956...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-08 07:12 UTC by Moez Roy
Modified: 2014-07-25 17:42 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-03-10 13:41:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (33.74 KB, text/plain)
2014-03-08 07:12 UTC, Moez Roy
no flags Details
Most recent dmesg for error condition (93.65 KB, text/plain)
2014-07-25 17:42 UTC, D. Charles Pyle
no flags Details

Description Moez Roy 2014-03-08 07:12:21 UTC
Additional info:
reporter:       libreport-2.2.0
ODEBUG: 18 of 18 active objects replaced

Potential duplicate: bug 863229

Comment 1 Moez Roy 2014-03-08 07:12:24 UTC
Created attachment 872103 [details]
File: dmesg

Comment 2 Josh Boyer 2014-03-10 13:41:55 UTC
There's no bug here.  I have no idea what libreport thinks the problem is.

Comment 3 D. Charles Pyle 2014-07-25 17:42:28 UTC
Created attachment 921020 [details]
Most recent dmesg for error condition

Any idea yet as to what this error message is? I'm seeing it about every couple minutes, along with a message that says "kernel crashed."  ABRT won't let me actually report it to bugzilla, saying that something is wrong with the data, such as corruption, etc, but the mesage from the server is "invalid JSON."

I've only begun seeing it since kernel-3.16.0-0.rc6.git1.1.fc21.x86_64.

I see no usable backtrace.  The only contents of the backtrace file is:

ODEBUG: 24 of 24 active objects replaced

Given the contents of the dmesg file (attached) it might be related to how the kernel interacts with alsa and cx18.

I tried turning off debugging but this error condition persists in showing up every couple minutes or so.


Note You need to log in before you can comment on or make changes to this bug.