Bug 456290 - kernel-2.6.27-0.166.rc0.git8.fc10.i686 :BUG kmalloc-64 (Not tainted): Poison overwritten/Object already free
kernel-2.6.27-0.166.rc0.git8.fc10.i686 :BUG kmalloc-64 (Not tainted): Poison ...
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
Blocks: F10Blocker/F10FinalBlocker
  Show dependency treegraph
Reported: 2008-07-22 12:53 EDT by Tom London
Modified: 2013-01-09 23:44 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-03 19:21:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/var/log/messages snippet with BUG/kmalloc ..... (28.80 KB, text/plain)
2008-07-22 12:53 EDT, Tom London
no flags Details
dmesg output showing several kmalloc-64 traces with 0.186 (84.14 KB, text/plain)
2008-07-28 16:35 EDT, Tom London
no flags Details

  None (edit)
Description Tom London 2008-07-22 12:53:52 EDT
Description of problem:
Get these during boot and after when running in runlevel 3.

Had a previous hard crash when in gnome (runlevel 5) but could recover no log.

Snippet from /var/log messages attached.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Tom London 2008-07-22 12:53:52 EDT
Created attachment 312365 [details]
/var/log/messages snippet with BUG/kmalloc .....
Comment 2 Tom London 2008-07-28 16:35:11 EDT
Created attachment 312815 [details]
dmesg output showing several kmalloc-64 traces with 0.186

Got similar (?) kmalloc-64 traces with 0.186
Comment 3 Tom London 2008-09-07 20:54:32 EDT
Haven't seen these in quite some while.  Certainly don't see them with 0.312.


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