Slab corruption detected with debug kernel on RHEL5

Solution Unverified - Updated -

Issue

What does the following message mean?

Slab corruption: (Tainted: PF    ) start=f3e9a34c, len=128
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c04b23ea>](remove_proc_entry+0xbf/0x103)
 [<c04797f2>] check_poison_obj+0x6a/0x179
 [<c0479a6a>] cache_alloc_debugcheck_after+0x25/0x148
 [<c047acb8>] __kmalloc+0xe0/0xeb
 [<f8845d48>] start_this_handle+0x88/0x34d [jbd]
 [<f8845d48>] start_this_handle+0x88/0x34d [jbd]
 [<f8845d48>] start_this_handle+0x88/0x34d [jbd]
 [<c047af20>] kmem_cache_alloc+0xa4/0xaf
 [<f8846085>] journal_start+0x78/0xdb [jbd]
 [<f8846085>] journal_start+0x78/0xdb [jbd]
 [<f88460b9>] journal_start+0xac/0xdb [jbd]
 [<f88813ae>] ext3_dirty_inode+0x24/0x66 [ext3]
 [<c049e8bf>] __mark_inode_dirty+0x27/0x144
 [<c04615dd>] __generic_file_aio_write_nolock+0x38d/0x52a
 [<c04617d6>] generic_file_aio_write+0x5c/0xaf
 [<f887ced1>] ext3_file_write+0x19/0x86 [ext3]
 [<c047e60a>] do_sync_write+0xb6/0xf1
 [<c043777f>] autoremove_wake_function+0x0/0x2d
 [<c047e554>] do_sync_write+0x0/0xf1
 [<c047ee93>] vfs_write+0xa1/0x143
 [<c047f4ca>] sys_write+0x3c/0x63
 [<c0404fc3>] syscall_call+0x7/0xb
 =======================
030: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 00 00 00 00
Prev obj: start=f3e9a2c0, len=128
Redzone: 0x170fc2a5/0x170fc2a5.
Last user: [<f8845d48>](start_this_handle+0x88/0x34d [jbd])
000: 20 6f 75 f6 89 0a 00 00 05 00 00 00 64 0b 00 00
010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Next obj: start=f3e9a3d8, len=128
Redzone: 0x170fc2a5/0x170fc2a5.
Last user: [<c05d6b0e>](neigh_resolve_output+0xd7/0x1e5)
000: 00 00 00 00 02 00 00 00 08 00 00 00 0e 00 00 00
010: fe 20 5d c0 00 00 00 01 ed 1e af de ff ff ff ff

Environment

  • Redhat Enterprise Linux 5.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content