Hi Al,
Here is the oops caused by runnning lsof(8) on 2.3.99-pre7-8
Also, I will make a patch now that fixes /proc/filesystems to show all the
new FS_ flags you introduced (so you don't have to do it), ok?
Regards,
Tigran
ksymoops 0.7c on i686 2.3.99-pre7. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.3.99-pre7/ (default)
-m /usr/src/linux/System.map (default)
Warning: 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 (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
Reading Oops report from the terminal
invalid operand: 0000
CPU: 0
EIP: 0010:[<c015680f>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: 00000037 ebx: ce797960 ecx: 00000001 edx: 00000002
esi: 0000000c edi: ce810000 ebp: ce811f78 esp: ce811f60
ds: 0018 es: 0018 ss: 0018
Process lsof (pid: 529, stackpage=ce811000)
Stack: c0243c05 c0243be0 0000002c 00000000 ce797960 ce797960 ce811fa4 c013d21b
cfce46a0 bfffea40 00000fff ce797960 ce810000 00001000 bfffe990 bfffe940
ce810000 ce80b640 cff05e80 ce810000 bfffe55c bfffe54c 00000008 00000001
Call Trace: [<c0243c05>] [<c0243be0>] [<c013d21b>] [<c010b87c>]
Code: 0f 0b 83 c4 0c 8d 65 f4 89 f0 5b 5e 89 ec 5d c3 90 83 ec 24
>>EIP; c015680f <proc_pid_readlink+7f/90> <=====
Trace; c0243c05 <tvecs+c27d/d9b8>
Trace; c0243be0 <tvecs+c258/d9b8>
Trace; c013d21b <sys_readlink+ab/100>
Trace; c010b87c <system_call+34/38>
Code; c015680f <proc_pid_readlink+7f/90>
00000000 <_EIP>:
Code; c015680f <proc_pid_readlink+7f/90> <=====
0: 0f 0b ud2a <=====
Code; c0156811 <proc_pid_readlink+81/90>
2: 83 c4 0c add $0xc,%esp
Code; c0156814 <proc_pid_readlink+84/90>
5: 8d 65 f4 lea 0xfffffff4(%ebp),%esp
Code; c0156817 <proc_pid_readlink+87/90>
8: 89 f0 mov %esi,%eax
Code; c0156819 <proc_pid_readlink+89/90>
a: 5b pop %ebx
Code; c015681a <proc_pid_readlink+8a/90>
b: 5e pop %esi
Code; c015681b <proc_pid_readlink+8b/90>
c: 89 ec mov %ebp,%esp
Code; c015681d <proc_pid_readlink+8d/90>
e: 5d pop %ebp
Code; c015681e <proc_pid_readlink+8e/90>
f: c3 ret
Code; c015681f <proc_pid_readlink+8f/90>
10: 90 nop
Code; c0156820 <proc_readfd+0/18c>
11: 83 ec 24 sub $0x24,%esp
2 warnings issued. Results may not be reliable.
-
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/
This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:13 EST