[mdlug] hanging machine kernel panic - on going

[Jonathan Billings]

On Feb 27, 2012, at 8:57 PM, Gmail-otakurider wrote:

> Feb 27 16:53:41 kuza kernel: BUG: unable to handle kernel NULL pointer
> dereference at virtual address 00000000
> Feb 27 16:53:41 kuza kernel:  printing eip:
> Feb 27 16:53:41 kuza kernel: cab88e5c
> Feb 27 16:53:41 kuza kernel: *pde = 09606067
> Feb 27 16:53:41 kuza kernel: Oops: 0002 [#1]
> Feb 27 16:53:41 kuza kernel: last sysfs file: /block/hda/hda1/size
> Feb 27 16:53:41 kuza kernel: Modules linked in: nfsd exportfs lockd
> nfs_acl autofs4 hidp l2cap bluetooth sunrpc dm_mirror dm_mod video sbs
> i2c_ec dock container button battery asus_acpi backlight ac ipv6 lp
> parport_pc parport floppy ohci_hcd 8139too i2c_ali15x3 serio_raw mii
> i2c_ali1535 i2c_core pcspkr ide_cd cdrom ext3 jbd
> Feb 27 16:53:41 kuza kernel: CPU:    0
> Feb 27 16:53:41 kuza kernel: EIP:    0060:[<cab88e5c>]    Not tainted VLI
> Feb 27 16:53:41 kuza kernel: EFLAGS: 00210206   (2.6.20-1.2320.fc5 #1)
> Feb 27 16:53:41 kuza kernel: EIP is at 0xcab88e5c
> Feb 27 16:53:41 kuza kernel: eax: 00000000   ebx: cab88f9c   ecx:
> ca3c3610   edx: c137c980
> Feb 27 16:53:41 kuza kernel: esi: cab88f48   edi: 00000006   ebp:
> cab88e58   esp: cab88ba4
> Feb 27 16:53:41 kuza kernel: ds: 007b   es: 007b   ss: 0068
> Feb 27 16:53:41 kuza kernel: Process python (pid: 1745, ti=cab88000
> task=cfec30d0 task.ti=cab88000)

Ok, so python was the current task when it panicked.  This is most likely not the cause, just what happened to be currently operating.

> Feb 27 16:53:41 kuza kernel: Stack: cab88e60 cab88e4c cab88e50 cab88e54
> 00000030 00000000 00000000 00000030
> Feb 27 16:53:41 kuza kernel:        00000000 00000000 00000000 00000000
> 00000000 00000000 c046ad08 00000000
> Feb 27 16:53:41 kuza kernel:        00000000 00000002 ccd0f320 00000000
> cfec30d0 c0419bdc 00100100 00200200
> Feb 27 16:53:41 kuza kernel: Call Trace:
> Feb 27 16:53:41 kuza kernel:  [<c046ad08>] __pollwait+0x0/0xab
> Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
> Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
> Feb 27 16:53:41 kuza kernel:  [<d082fb73>]
> do_get_write_access+0x48b/0x4b8 [jbd]
> Feb 27 16:53:41 kuza kernel:  [<d08885f8>]
> __ext3_get_inode_loc+0x10a/0x2fd [ext3]
> Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
> Feb 27 16:53:41 kuza kernel:  [<d0893712>]
> __ext3_journal_dirty_metadata+0x16/0x3a [ext3]
> Feb 27 16:53:41 kuza kernel:  [<d082fbc1>]
> journal_get_write_access+0x21/0x26 [jbd]
> Feb 27 16:53:41 kuza kernel:  [<d0888489>]
> ext3_mark_iloc_dirty+0x275/0x2da [ext3]
> Feb 27 16:53:41 kuza kernel:  [<c0418de8>] __wake_up+0x32/0x43
> Feb 27 16:53:41 kuza kernel:  [<d082f6dc>] journal_stop+0x1cb/0x1d7 [jbd]
> Feb 27 16:53:41 kuza kernel:  [<d088f703>] __ext3_journal_stop+0x19/0x34
> [ext3]
> Feb 27 16:53:41 kuza kernel:  [<d088a6b2>]
> ext3_ordered_commit_write+0xba/0xd8 [ext3]
> Feb 27 16:53:41 kuza kernel:  [<c044aaa7>] __pagevec_lru_add+0x7a/0x85
> Feb 27 16:53:41 kuza kernel:  [<c0446328>]
> generic_file_buffered_write+0x579/0x5e8
> Feb 27 16:53:41 kuza kernel:  [<c047aa2a>] __getblk+0x3b/0x287
> Feb 27 16:53:41 kuza kernel:  [<c0420638>] current_fs_time+0x45/0x51
> Feb 27 16:53:41 kuza kernel:  [<c0405e65>] do_IRQ+0xbf/0xd6
> Feb 27 16:53:41 kuza kernel:  [<c0404763>] common_interrupt+0x23/0x28
> Feb 27 16:53:41 kuza kernel:  [<c046aa67>] core_sys_select+0x2d2/0x2f3
> Feb 27 16:53:41 kuza kernel:  [<c0448dff>] __alloc_pages+0x68/0x29c
> Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
> Feb 27 16:53:41 kuza kernel:  [<c0444c30>] find_get_page+0x35/0x3a
> Feb 27 16:53:41 kuza kernel:  [<c044710b>] filemap_nopage+0x159/0x2d4
> Feb 27 16:53:41 kuza kernel:  [<c044f9c9>] __handle_mm_fault+0x858/0x87a
> Feb 27 16:53:41 kuza kernel:  [<c0452bf4>] do_mmap_pgoff+0x587/0x6e8
> Feb 27 16:53:41 kuza kernel:  [<c046b04e>] sys_select+0xa0/0x186
> Feb 27 16:53:41 kuza kernel:  [<c0403dc8>] syscall_call+0x7/0xb
> Feb 27 16:53:41 kuza kernel:  =======================

The above call stack seems to indicate it was in the middle of a kernel operation with opearting on the ext3 journal.  If I recall how this works, it looks like a case of running out of memory during a kernel system call?

> Feb 27 16:53:41 kuza kernel: Code: aa 46 c0 48 4b c3 bf ea ff ff ff 00
> e0 9a 08 00 e0 9a 08 06 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 <00> 00 00 00 44 00 00 00 46 02 20 00 01 00 00 00
> 00 00 00 00 d2
> Feb 27 16:53:41 kuza kernel: EIP: [<cab88e5c>] 0xcab88e5c SS:ESP
> 0068:cab88ba4
> Feb 27 20:04:54 kuza avahi-daemon[2006]: Invalid query packet.
> Feb 27 20:05:38 kuza last message repeated 30 times
> Feb 27 20:49:41 kuza syslogd 1.4.1: restart.
> Feb 27 20:49:41 kuza kernel: klogd 1.4.1, log source = /proc/kmsg started.

I see a couple avahi-daemon entries before the machine was reset, making me think that some part of the system was still responding, enough to write log entries, unless you grabbed this off a remote syslog.

--
Jonathan Billings <billings at negate.org>