linux-kernel - Kernel Panic on Kernel 2.6.36.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <7a37f54158514d80971d22947a74341c@BY2PR08MB347.namprd08.prod.outlook.com>
Date:	Tue, 4 Mar 2014 15:14:35 +0000
From:	Jason Zhu <jzhu@...edium.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Kernel Panic on Kernel 2.6.36.1

Hello,

I have had two separate instances of kernel panics on the 2.6.36.1 kernel. I do not have the expertise necessary to interpret the traces and I would like to see if there is anyone who can explain what the traces are saying so that I may get some insight as to the cause of the issue. 

 [<ffffffff8104866c>] ? wake_bit_function+0x0/0x23 
 [<ffffffff8104855f>] ? bit_waitqueue+0x10/0xa0 
 [<ffffffff8104862d>] ? wake_up_bit+0x11/0x22 
 [<ffffffff810eeb38>] ? ext3_handle_error+0xb3/0xb7 
 [<ffffffff810eeb99>] ? __ext3_std_error+0x5d/0x64 
 [<ffffffff810ec550>] ? ext3_orphan_add+0x165/0x176 
 [<ffffffff810e5b63>] ? walk_page_buffers+0x67/0x8d 
 [<ffffffff810e74b9>] ? journal_dirty_data_fn+0x0/0x16 
 [<ffffffff810e8fea>] ? ext3_ordered_write_end+0xc5/0x10f 
 [<ffffffff8106a08d>] ? generic_file_buffered_write+0x16f/0x22c 
 [<ffffffff8106b9af>] ? __generic_file_aio_write+0x33b/0x36f 
 [<ffffffff8106bf9a>] ? generic_file_aio_read+0x51e/0x5b7 
 [<ffffffff8108770e>] ? page_add_new_anon_rmap+0x65/0x86 
 [<ffffffff8106ba36>] ? generic_file_aio_write+0x53/0x99 
 [<ffffffff81099b44>] ? do_sync_write+0xb0/0xf2 
 [<ffffffff81006df0>] ? __switch_to+0x1dd/0x2a4 
 [<ffffffff81008a8e>] ? apic_timer_interrupt+0xe/0x20 
 [<ffffffff8100e929>] ? read_tsc+0xa/0x20 
 [<ffffffff8109a3c9>] ? vfs_write+0xad/0x134 
 [<ffffffff8109a50c>] ? sys_write+0x45/0x6e 
 [<ffffffff81026bac>] ? sysenter_dispatch+0x7/0x32

 [<ffffffff813c6336>] ? panic+0x9d/0x1a4 
 [<ffffffff813c648b>] ? printk+0x4e/0x56 
 [<ffffffff810ee546>] ? ext3_abort+0x95/0xff 
 [<ffffffff812c7787>] ? __sk_free+0xd7/0xed 
 [<ffffffff81357208>] ? unix_destruct_scm+0xb2/0xb9 
 [<ffffffff812ccedb>] ? memcpy_toiovec+0x34/0x62 
 [<ffffffff810f0230>] ? ext3_journal_start_sb+0x32/0x4a 
 [<ffffffff810e6610>] ? ext3_dirty_inode+0x28/0x7b 
 [<ffffffff810b376a>] ? __mark_inode_dirty+0x27/0x1ad 
 [<ffffffff810aac50>] ? file_update_time+0x100/0x12f 
 [<ffffffff8106b8cf>] ? __generic_file_aio_write+0x25b/0x36f 
 [<ffffffff810a88e6>] ? dput+0x37/0x152 
 [<ffffffff8106ba36>] ? generic_file_aio_write+0x53/0x99 
 [<ffffffff8106b9e3>] ? generic_file_aio_write+0x0/0x99 
 [<ffffffff81099a50>] ? do_sync_readv_writev+0x9a/0xde 
 [<ffffffff810a47b3>] ? user_path_at+0x59/0x7f 
 [<ffffffff81006df0>] ? __switch_to+0x1dd/0x2a4 
 [<ffffffff810cb4ae>] ? compat_do_readv_writev+0xe9/0x1b1 
 [<ffffffff810279fe>] ? sys32_stat64+0x20/0x29 
 [<ffffffff810cb682>] ? compat_sys_writev+0x64/0x8d 
 [<ffffffff81026bac>] ? sysenter_dispatch+0x7/0x32

Let me know if you need any additional details.

Please C.C. me in any further answers/discussions for this question. 

Regards,
Jason