Oops in 2.3.99pre5

From: Martin Josefsson (gandalf@wlug.westbo.se)
Date: Thu Apr 13 2000 - 12:27:52 EST


Hi

I've got an Oops here, it occured durin high network activity and running
X. It was a ftp session running at 5.5MB/s and some window switching in X
involved. It began to go very sluggish after a while and then I saw the
Oops. I've fed it throu ksymoops and here's the result:

ksymoops 0.7c on i686 2.3.99-pre5. Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.3.99-pre5/ (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.

kernel BUG at page_alloc.c:104!
invalid operand: 0000
CPU: 0
EIP: 0010:[<c012a0f9>]
EFLAGS: 00010286
eax: 00000020 ebx: c1000a70 ecx: ffffffff edx: 00000000
esi: c1000a70 edi: c75b19d4 ebp: 00000000 esp: c12cfef4
ds: 0018 es: 0018 ss: 0018
Process kswapd (pid: 3, stackpage=c12cf000)
Stack: c01cee67 c01cf033 00000068 08276000 c1000a70 c75b19d4 c0e4b7a0 005d8a00
       c10aa6c0 c0129903 00000001 c10aa6c0 c012981b 08276000 082bd000 c75b19d4
       082bd000 005d8a00 c0129a5f c0e4b7a0 08275000 c75b19d4 00000004 c0e4b7a0
Call Trace: [<c01cee67>] [<c01cf033>] [<c0129903>] [<c012981b>] [<c0129a5f>] [<c0129afb>] [<c0129be0>]
       [<c0129caa>] [<c0129d35>] [<c0108d3c>]
Code: 0f 0b 83 c4 0c 89 f6 89 d8 2b 05 ac e8 1f c0 69 c0 39 8e e3
Reading Oops report from the terminal
invalid operand: 0000
CPU: 0
EIP: 0010:[<c012a0f9>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: 00000020 ebx: c1000a70 ecx: ffffffff edx: 00000000
esi: c1000a70 edi: c75b19d4 ebp: 00000000 esp: c12cfef4
ds: 0018 es: 0018 ss: 0018
Process kswapd (pid: 3, stackpage=c12cf000)
Stack: c01cee67 c01cf033 00000068 08276000 c1000a70 c75b19d4 c0e4b7a0 005d8a00
       c10aa6c0 c0129903 00000001 c10aa6c0 c012981b 08276000 082bd000 c75b19d4
       082bd000 005d8a00 c0129a5f c0e4b7a0 08275000 c75b19d4 00000004 c0e4b7a0
Call Trace: [<c01cee67>] [<c01cf033>] [<c0129903>] [<c012981b>] [<c0129a5f>] [<c0129afb>] [<c0129be0>]
       [<c0129caa>] [<c0129d35>] [<c0108d3c>]
Code: 0f 0b 83 c4 0c 89 f6 89 d8 2b 05 ac e8 1f c0 69 c0 39 8e e3

>>EIP; c012a0f9 <__free_pages_ok+49/298> <=====
Trace; c01cee67 <tvecs+2a23/1123c>
Trace; c01cf033 <tvecs+2bef/1123c>
Trace; c0129903 <try_to_swap_out+1a3/1d4>
Trace; c012981b <try_to_swap_out+bb/1d4>
Trace; c0129a5f <swap_out_vma+12b/190>
Trace; c0129afb <swap_out_mm+37/64>
Trace; c0129be0 <swap_out+b8/104>
Trace; c0129caa <do_try_to_free_pages+7e/94>
Trace; c0129d35 <kswapd+75/f0>
Trace; c0108d3c <kernel_thread+28/38>
Code; c012a0f9 <__free_pages_ok+49/298>
00000000 <_EIP>:
Code; c012a0f9 <__free_pages_ok+49/298> <=====
   0: 0f 0b ud2a <=====
Code; c012a0fb <__free_pages_ok+4b/298>
   2: 83 c4 0c add $0xc,%esp
Code; c012a0fe <__free_pages_ok+4e/298>
   5: 89 f6 mov %esi,%esi
Code; c012a100 <__free_pages_ok+50/298>
   7: 89 d8 mov %ebx,%eax
Code; c012a102 <__free_pages_ok+52/298>
   9: 2b 05 ac e8 1f c0 sub 0xc01fe8ac,%eax
Code; c012a108 <__free_pages_ok+58/298>
   f: 69 c0 39 8e e3 00 imul $0xe38e39,%eax,%eax

1 warning issued. Results may not be reliable.
 
Hope that can help someone figure out what the problem was.

The machine in question is a Celeron 366, 128MB ram, 2x128MB swap
It had been up for 18h when this happend.
The machine is still up and running and now it seems to have recovered
from the oops as it's no longer sluggish.

this is the output from free:

             total used free shared buffers cached
Mem: 126808 124528 2280 0 736 66500
-/+ buffers/cache: 57292 69516
Swap: 268048 29960 238088

It feels a bit strange, why is 29960kB of swap used when I have 69516kB
free.

/Martin

-- 
The three best things about going to school are June, July, and August.

- 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 : Sat Apr 15 2000 - 21:00:21 EST