Re: Kernel oops in 2.2.10, scsi related?

Carlos Hwa (chwa@corp.adaptec.com)
Fri, 18 Jun 1999 16:24:16 -0700


Sorry about the html, i guess outlook still sends in html even if you
say plain text. trying netscape this time :)
ksymoop<oops_message on the kernel i was using...

Options used: -V (default)
-o /lib/modules/2.2.10/ (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-m /usr/src/linux/System.map (default)
-c 1 (default)

You did not tell me where to find symbol information. I will assume
that the log matches the kernel and modules that are running right now
and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.

No modules in ksyms, skipping objects
Unable to handle kernel paging request at virtual address 00b10334
current->tss.cr3 = 07c66000, %cr3 = 07c66000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c012617e>]
EFLAGS: 00010203
eax: 00b10320 ebx: c0305a30 ecx: 00005b0e edx: 00010000
esi: 00b10320 edi: c5b10440 ebp: c0305a30 esp: c7357cec
ds: 0018 es: 0018 ss: 0018
Process iozone2 (pid: 719, process nr: 33, stackpage=c7357000)
Stack: 00000003 00000900 c011b8a2 c0305a30 00000010 00000006 c0120562
00000006
00000003 00000001 00000003 00000003 c012069b 00000003 00000400
00000400
c0120e14 00000003 00000400 00000400 00000004 00000900 c0125895
c7356000
Call Trace: [<c011b8a2>] [<c0120562>] [<c012069b>] [<c0120e14>]
[<c0125895>] [<c01260bc>] [<c01252a6>]
[<c0125452>] [<c013685c>] [<c0125443>] [<c0138a30>] [<c0138fe1>]
[<c0139321>] [<c0137744>] [<c0110d0e>]
[<c011723d>] [<c010a0c3>] [<c0108f84>] [<c0123bd4>] [<c0137290>]
[<c0108ee8>]
Code: 8b 76 14 83 78 20 00 75 06 f6 40 18 46 74 0f 6a 00 e8 6c 01

>>EIP: c012617e <try_to_free_buffers+12/84>
Trace: c011b8a2 <shrink_mmap+d6/12c>
Trace: c0120562 <do_try_to_free_pages+26/78>
Trace: c012069b <try_to_free_pages+23/30>
Trace: c0120e14 <__get_free_pages+6c/1b8>
Trace: c0125895 <put_unused_buffer_head+21/4c>
Trace: c01260bc <grow_buffers+3c/ec>
Trace: c01252a6 <refill_freelist+a/30>
Trace: c0125452 <getblk+11e/144>
Trace: c011723d <do_bottom_half+45/64>
Code: c012617e <try_to_free_buffers+12/84> 00000000 <_EIP>: <===
Code: c012617e <try_to_free_buffers+12/84> 0: 8b 76
14 movl 0x14(%esi),%esi <===
Code: c0126181 <try_to_free_buffers+15/84> 3: 83 78 20
00 cmpl $0x0,0x20(%eax)
Code: c0126185 <try_to_free_buffers+19/84> 7: 75
06 jne c012618d <try_to_free_buffers+21/84>
Code: c0126187 <try_to_free_buffers+1b/84> 9: f6 40 18
46 testb $0x46,0x18(%eax)
Code: c012618b <try_to_free_buffers+1f/84> d: 74
0f je c012619c <try_to_free_buffers+30/84>
Code: c012618d <try_to_free_buffers+21/84> f: 6a
00 pushl $0x0
Code: c012618f <try_to_free_buffers+23/84> 11: e8 6c 01 00
00 call c0126300 <wakeup_bdflush+0/78>

2 warnings issued. Results may not be reliable.

Alan Cox wrote:
>
> Feed the symbols through ksymoops or look them up by hand in the
> System.map file for the EIP and the call track symbols. Then I can
> see where it died and guess what cuased it

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/