[tproxy] Re: Development version 1.9.2 released - Oops

[James MacLean]

Hello Everyone,

This happened only once. But we have only brought up a kernel with it 
today :). It appeared to occur when an iptables cmd was issued. Since then 
(and the PC rebooting) we have not had it happen. We are not using the 
tproxy filter yet.

Also, where is a FAQ on a typical install of this for Squid? I have Squid 
now patched and I believe I can fuddle through it, but would rather use 
someone else's notes ;).

thanks,
JES

ksymoops 2.4.5 on i686 2.6.4-rc2.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.6.4-rc2/ (default)
     -m /boot/System.map-2.6.4-rc2 (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.

Error (regular_file): read_ksyms stat /proc/ksyms failed
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Mar  8 12:07:13 pink kernel: kernel BUG at mm/slab.c:1316!
Mar  8 12:07:13 pink kernel: invalid operand: 0000 [#1]
Mar  8 12:07:13 pink kernel: CPU:    1
Mar  8 12:07:13 pink kernel: EIP:    0060:[<c013c159>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Mar  8 12:07:13 pink kernel: EFLAGS: 00010202
Mar  8 12:07:13 pink kernel: eax: 00000033   ebx: f6ee3fec   ecx: c03b4e30   edx: c0306c7c
Mar  8 12:07:13 pink kernel: esi: f8a1dc18   edi: f8a1dc18   ebp: f6ee3e68   esp: e433df3c
Mar  8 12:07:13 pink kernel: ds: 007b   es: 007b   ss: 0068
Mar  8 12:07:13 pink kernel: Stack: c02c8c60 f8a1dc08 00002000 e433df58 f6ee3eb0 c0000000 ffffffc0 00000080 
Mar  8 12:07:13 pink kernel:        00000000 f8a20f00 e433c000 c03082f0 f88b40b6 f8a1dc08 00000040 00000080 
Mar  8 12:07:13 pink kernel:        00002000 00000000 00000000 00000000 f8a1a3a4 0807d6a0 c030830c f88b400f 
Mar  8 12:07:13 pink kernel:  [<f88b40b6>] ip_nat_init+0x42/0x1bf [iptable_nat]
Mar  8 12:07:13 pink kernel:  [<f8a1a3a4>] init_or_cleanup+0x2a/0xba [iptable_nat]
Mar  8 12:07:13 pink kernel:  [<f88b400f>] init+0xf/0x13 [iptable_nat]
Mar  8 12:07:13 pink kernel:  [<c01346dc>] sys_init_module+0x11d/0x20e
Mar  8 12:07:13 pink kernel:  [<c0108d7f>] syscall_call+0x7/0xb
Mar  8 12:07:13 pink kernel: Code: 0f 0b 24 05 ce 84 2c c0 8b 0b e9 74 ff ff ff 8b 47 40 c7 04 


>>EIP; c013c159 <kmem_cache_create+438/506>   <=====

>>ebx; f6ee3fec <__crc_net_ratelimit+27fb1/13b36f>
>>ecx; c03b4e30 <cache_chain_sem+0/14>
>>edx; c0306c7c <log_wait+4/c>
>>esi; f8a1dc18 <__crc_pm_idle+10dd99/244fc7>
>>edi; f8a1dc18 <__crc_pm_idle+10dd99/244fc7>
>>ebp; f6ee3e68 <__crc_net_ratelimit+27e2d/13b36f>
>>esp; e433df3c <__crc_skb_clone_fraglist+37fe19/9833c6>

Code;  c013c159 <kmem_cache_create+438/506>
00000000 <_EIP>:
Code;  c013c159 <kmem_cache_create+438/506>   <=====
   0:   0f 0b                     ud2a      <=====
Code;  c013c15b <kmem_cache_create+43a/506>
   2:   24 05                     and    $0x5,%al
Code;  c013c15d <kmem_cache_create+43c/506>
   4:   ce                        into   
Code;  c013c15e <kmem_cache_create+43d/506>
   5:   84 2c c0                  test   %ch,(%eax,%eax,8)
Code;  c013c161 <kmem_cache_create+440/506>
   8:   8b 0b                     mov    (%ebx),%ecx
Code;  c013c163 <kmem_cache_create+442/506>
   a:   e9 74 ff ff ff            jmp    ffffff83 <_EIP+0xffffff83>
Code;  c013c168 <kmem_cache_create+447/506>
   f:   8b 47 40                  mov    0x40(%edi),%eax
Code;  c013c16b <kmem_cache_create+44a/506>
  12:   c7 04 00 00 00 00 00      movl   $0x0,(%eax,%eax,1)


1 warning and 1 error issued.  Results may not be reliable.

-- 
James B. MacLean        macleajb@ednet.ns.ca
Department of Education 
Nova Scotia, Canada