Bug 198671 - slab corruption / slab error in slab_destroy_objs(): cache `bio'
Summary: slab corruption / slab error in slab_destroy_objs(): cache `bio'
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: ia64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Prarit Bhargava
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks: fedora-ia64 209053
TreeView+ depends on / blocked
 
Reported: 2006-07-12 17:18 UTC by Doug Chapman
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-16 18:30:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
kernel messages from slab corruption runing the "busy2" test on hpdiablo1 (22.97 KB, text/plain)
2006-07-12 17:18 UTC, Doug Chapman
no flags Details

Description Doug Chapman 2006-07-12 17:18:01 UTC
Description of problem:
Seen on one of my HP ia64 Integrity servers running a proprietary HP test suite.
   Since all the messages are rather lengthy I wil upload it as an attachment.

But here are some of what think are the more interesting messages:

Slab corruption: (Not tainted) start=e0000040765c2828, len=104
kernel BUG at mm/slab.c:608!
kjournald[541]: bugcheck! 0 [1]

....
slab error in slab_destroy_objs(): cache `bio': start of a freed object was
overwritten


Version-Release number of selected component (if applicable):
kernel-2.6.17-1.2364.fc6


How reproducible:
This took about 10 hours of stress testing before it was seen.  I will update
this BZ if I see it again.


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Doug Chapman 2006-07-12 17:18:01 UTC
Created attachment 132317 [details]
kernel messages from slab corruption runing the "busy2" test on hpdiablo1

Comment 2 Prarit Bhargava 2006-10-16 17:56:25 UTC
We haven't seen this again, have we?  Doug, any objections to closing this out?

P.

Comment 3 Doug Chapman 2006-10-16 18:29:35 UTC
I have not seen this in a while, yes I am OK with closing it.



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