Here is the output from ksymoops done on a freshly generated oops.
(This is the umsdos + ppa zip drive + ls == oops problem)
My feet may be wet, but I'm still pretty new to tracing down kernel
bugs.
Jack Neely
-- Jack Neely AKA C4Man AKA The QuackMaster E-mail: jjneely@eos.ncsu.edu Home Page: http://www.ac.net/~hneely ICQ UIN: 3738590 --------------4DD629A386E8EEF9EFFB29E2 Content-Type: text/plain; charset=us-ascii; name="oops" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="oops"Options used: -V (default) -o /lib/modules/2.3.6/ (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 Warning, no symbols in lsmod, is /proc/modules a valid lsmod file? Unable to handle kernel NULL pointer dereference at virtual address 00000000 current->tss.cr3 = 0130b000, %cr3 = 0130b000 *pde = 00000000 Oops: 0002 CPU: 0 EIP: 0010:[<c010f642>] EFLAGS: 00010082 eax: 00000016 ebx: c12a1874 ecx: c01fce70 edx: c1aac000 esi: 00000000 edi: 00000000 ebp: c130db84 esp: c130db70 ds: 0018 es: 0018 ss: 0018 Process ls (pid: 97, process nr: 24, stackpage=c130d000) Stack: 00000000 00000000 00000286 00000000 00000003 c12a1808 c015feea c130de70 c015df4a c12a17a0 00000000 c13e7420 c12a17a0 c12a1808 00000000 c011dd63 c140bcc0 4000638c 00000001 c1309018 c1217000 00000246 c027e5d8 08055b14 Call Trace: [<c015feea>] [<c015df4a>] [<c011dd63>] [<c011dd63>] [<c011b0e8>] [<c011b25c>] [<c010d073>] [<c0107d5d>] [<c01cff1a>] [<c01b79c1>] [<c0136854>] [<c011d700>] [<c015d9e0>] [<c011b016>] [<c011b0be>] [<c015dfc8>] [<c015d9e0>] [<c010d073>] [<c012e1f4>] [<c012e340>] [<c012e6d3>] [<c0130b70>] [<c0130d0d>] [<c0130b70>] [<c015df60>] [<c0107c24>] Code: c7 05 00 00 00 00 00 00 00 00 83 c4 04 8d 4b 04 89 4d f8 83
>>EIP: c010f642 <__wake_up+42/f0> Trace: c015feea <umsdos_endlookup+3a/40> Trace: c015df4a <umsdos_readdir_x+51a/530> Trace: c011dd63 <filemap_nopage+173/370> Trace: c011dd63 <filemap_nopage+173/370> Trace: c011b0e8 <do_no_page+58/f0> Trace: c0107d5d <error_code+2d/40> Trace: c015d9e0 <umsdos_dir_once+0/50> Trace: c015dfc8 <UMSDOS_readdir+68/a0> Trace: c012e6d3 <open_namei+253/3b0> Trace: c0130b70 <filldir+0/90> Code: c010f642 <__wake_up+42/f0> 00000000 <_EIP>: <=== Code: c010f642 <__wake_up+42/f0> 0: c7 05 00 00 00 movl $0x0,0x0 <=== Code: c010f647 <__wake_up+47/f0> 5: 00 00 00 00 00 Code: c010f64c <__wake_up+4c/f0> a: 83 c4 04 addl $0x4,%esp Code: c010f64f <__wake_up+4f/f0> d: 8d 4b 04 leal 0x4(%ebx),%ecx Code: c010f652 <__wake_up+52/f0> 10: 89 4d f8 movl %ecx,0xfffffff8(%ebp) Code: c010f655 <__wake_up+55/f0> 13: 83 00 00 addl $0x0,(%eax)
2 warnings issued. Results may not be reliable.
--------------4DD629A386E8EEF9EFFB29E2--
- 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/