Why does system panic with "Unable to handle kernel NULL pointer dereference at 0000000000000010"?

Solution Unverified - Updated -

Issue

  • Kernel panic with error message "Unable to handle kernel NULL pointer dereference at 0000000000000010"
RIP:
[<ffffffff88032cf1>] :jbd:journal_dirty_metadata+0x44/0x1e3
  • Stack trace shows
Call Trace:
[<ffffffff8804f079>] :ext3:ext3_free_data+0xc6/0xff
[<ffffffff8804f194>] :ext3:ext3_free_branches+0xe2/0x1dc
[<ffffffff8804fa12>] :ext3:ext3_truncate+0x784/0x8e0
[<ffffffff880559f3>] :ext3:__ext3_journal_stop+0x1f/0x3d
[<ffffffff88032152>] :jbd:journal_start+0xc9/0x100
[<ffffffff88050193>] :ext3:ext3_delete_inode+0x7d/0xd5
[<ffffffff88050116>] :ext3:ext3_delete_inode+0x0/0xd5
[<ffffffff8002f114>] generic_delete_inode+0xc6/0x143
[<ffffffff8000d19e>] dput+0xf6/0x114
[<ffffffff80036643>] sys_renameat+0x18a/0x1eb
[<ffffffff80066bcd>] do_page_fault+0x4fe/0x830
[<ffffffff80022fd9>] sys_newstat+0x28/0x31
[<ffffffff8005d116>] system_call+0x7e/0x83


Code: 83 7d 10 00 75 44 c7 45 10 01 00 00 00 41 83 7c 24 08 00 7f
RIP  [<ffffffff88032cf1>] :jbd:journal_dirty_metadata+0x44/0x1e3
RSP <ffff81007ad9fbf8>
CR2: 0000000000000010

Environment

  • Red Hat Enterprise Linux 5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.