On Sun, Nov 24, 2002 at 10:34:33PM -0500, Brian J. Murrell wrote:
> Very strange.

Well, some more info to go along with this problem.  It would seem
that my kernel has oopsed.  Here is the stack trace, ksymoopsed:

$ ksymoops < /tmp/oops.txt 
ksymoops 2.4.5 on i686 2.4.19-16mdk.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.19-16mdk/ (default)
     -m /boot/System.map-2.4.19-16mdk (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.

Warning (compare_ksyms_lsmod): module ext3 is in lsmod but not in ksyms, probably no 
symbols exported
Warning (compare_maps): mismatch on symbol lvm_name  , lvm-mod says d880863c, 
/lib/modules/2.4.19-16mdk/kernel/drivers/md/lvm-mod.o.gz says d8808700.  Ignoring 
/lib/modules/2.4.19-16mdk/kernel/drivers/md/lvm-mod.o.gz entry
Nov 24 22:19:44 pc kernel: Unable to handle kernel paging request at virtual address 
eeb3afcc
Nov 24 22:19:44 pc kernel: c0132836
Nov 24 22:19:44 pc kernel: *pde = 00000000
Nov 24 22:19:44 pc kernel: Oops: 0002
Nov 24 22:19:44 pc kernel: CPU:    0
Nov 24 22:19:44 pc kernel: EIP:    0010:[kmem_cache_free_one+86/137]    Tainted: PF
Nov 24 22:19:44 pc kernel: EIP:    0010:[<c0132836>]    Tainted: PF
Using defaults from ksymoops -t elf32-i386 -a i386
Nov 24 22:19:44 pc kernel: EFLAGS: 00010046
Nov 24 22:19:44 pc kernel: eax: eeb3afc8   ebx: c953e000   ecx: 00000069   edx: 
c14270c0
Nov 24 22:19:44 pc kernel: esi: c14270c0   edi: 00000000   ebp: c8801f84   esp: 
c8801f6c
Nov 24 22:19:44 pc kernel: ds: 0018   es: 0018   ss: 0018
Nov 24 22:19:44 pc kernel: Process gnome-terminal (pid: 3106, stackpage=c8801000)
Nov 24 22:19:44 pc kernel: Stack: 00000286 0000000f c013220c c14270c0 c953ef00 
c953ef00 c8801fbc c0148fca 
Nov 24 22:19:44 pc kernel:        c953ef00 0000000f 00000000 c8801fa8 c953ef00 
00000001 00000001 00000000 
Nov 24 22:19:44 pc kernel:        c34a4000 c8800000 40d06ee0 08453728 bffff648 
c0108fe3 08453728 0000000f 
Nov 24 22:19:44 pc kernel: Call Trace:    [kfree+44/64] [sys_poll+490/688] 
[system_call+51/64]
Nov 24 22:19:44 pc kernel: Call Trace:    [<c013220c>] [<c0148fca>] [<c0108fe3>]
Nov 24 22:19:44 pc kernel: Code: 89 50 04 8b 46 08 8d 56 08 89 03 89 5e 08 89 58 04 89 
53 04 


>>EIP; c0132836 <kmem_cache_free_one+56/89>   <=====

>>eax; eeb3afc8 <END_OF_CODE+160df7f1/????>
>>ebx; c953e000 <_end+9245428/18509478>
>>edx; c14270c0 <_end+112e4e8/18509478>
>>esi; c14270c0 <_end+112e4e8/18509478>
>>ebp; c8801f84 <_end+85093ac/18509478>
>>esp; c8801f6c <_end+8509394/18509478>

Trace; c013220c <kfree+2c/40>
Trace; c0148fca <sys_poll+1ea/2b0>
Trace; c0108fe3 <system_call+33/40>

Code;  c0132836 <kmem_cache_free_one+56/89>
00000000 <_EIP>:
Code;  c0132836 <kmem_cache_free_one+56/89>   <=====
   0:   89 50 04                  mov    %edx,0x4(%eax)   <=====
Code;  c0132839 <kmem_cache_free_one+59/89>
   3:   8b 46 08                  mov    0x8(%esi),%eax
Code;  c013283c <kmem_cache_free_one+5c/89>
   6:   8d 56 08                  lea    0x8(%esi),%edx
Code;  c013283f <kmem_cache_free_one+5f/89>
   9:   89 03                     mov    %eax,(%ebx)
Code;  c0132841 <kmem_cache_free_one+61/89>
   b:   89 5e 08                  mov    %ebx,0x8(%esi)
Code;  c0132844 <kmem_cache_free_one+64/89>
   e:   89 58 04                  mov    %ebx,0x4(%eax)
Code;  c0132847 <kmem_cache_free_one+67/89>
  11:   89 53 04                  mov    %edx,0x4(%ebx)


3 warnings issued.  Results may not be reliable.

There were 6 more oopses right behind that one (the above is the first
of course!) all in kmem_cache_free_one and __kmem_cache_alloc.

b.

-- 
Brian J. Murrell

Attachment: msg82234/pgp00000.pgp
Description: PGP signature

Reply via email to