From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262823AbUDAJHc (ORCPT ); Thu, 1 Apr 2004 04:07:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262814AbUDAJHb (ORCPT ); Thu, 1 Apr 2004 04:07:31 -0500 Received: from ua-online.net ([213.179.225.6]:52867 "EHLO center.hqhost.net") by vger.kernel.org with ESMTP id S262807AbUDAJEr (ORCPT ); Thu, 1 Apr 2004 04:04:47 -0500 From: Vladimir Klenov Date: Thu, 1 Apr 2004 12:04:40 +0300 To: linux-kernel@vger.kernel.org Subject: oops on same place on two different machines (2.4.23,2.4.24) Message-ID: <20040401090440.GA24164@valinor.localnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hello! On two different machines running 2.4.23-grsec, 2.4.24-grsec with last holes patched appearing oopses in same place. Both serving dynamic http content with apache 1.3 ksymoops output first, 4G RAM, 2xP4 xeon 2.4G, HT, 64G RAM support enabled, ext3 as root, reiserfs as /home with noatime,nodiratime, 2.4.23-grsec-2 ksymoops 2.4.9 on i686 2.4.23-grsec-2. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.23-grsec-2/ (default) -m /boot2/System.map-2.4.23-grsec-2 (specified) eip: c01c6c50 kernel BUG at /home/src/kernel/linux-2.4.23/include/asm/spinlock.h:133! invalid operand: 0000 CPU: 3 EIP: 0010:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010086 eax: 0000000e ebx: d9cda2c0 ecx: ffffffff edx: c010256c esi: f02cfde4 edi: 00000246 ebp: f02cfdc0 esp: f02cfdac ds: 0018 es: 0018 ss: 0018 Process httpd (pid: 14513, stackpage=f02cf000) Stack: c0346eb5 c01c6c50 f02ce000 f02cfde4 d9cda2c0 f02cfdf4 c020a9d9 d9cda204 d9cda204 c0242418 00000000 f02ce000 00000000 00000000 00000000 f02ce000 d9cda2c8 d9cda2c8 f02cfe0c c020bf8a d9cda204 00000000 f7d16cd0 0043bbf6 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 85 00 80 6e 34 c0 f0 fe 0b 0f 88 53 17 00 00 8d 4e 08 >>EIP; c01c6c68 <===== >>ebx; d9cda2c0 <_end+19944f58/386d0cf8> >>edx; c010256c >>esi; f02cfde4 <_end+2ff3aa7c/386d0cf8> <_end+2ff3aa58/386d0cf8> >>esp; f02cfdac <_end+2ff3aa44/386d0cf8> Trace; c01c6c50 Trace; c020a9d9 <__wait_on_freeing_inode+9d/d8> Trace; c0242418 Trace; c020bf8a Trace; c020c59a Trace; c0242418 Trace; c02424de Trace; c0242418 Trace; c023e1c0 Trace; c01fd79d Trace; c01fe404 Trace; c01fe77d Trace; c01fe946 Trace; c01feced <__user_walk+2d/48> Trace; c01fa5fe Trace; c01b5693 Code; c01c6c68 00000000 <_EIP>: Code; c01c6c68 <===== 0: 0f 0b ud2a <===== Code; c01c6c6a 2: 85 00 test %eax,(%eax) Code; c01c6c6c 4: 80 6e 34 c0 subb $0xc0,0x34(%esi) Code; c01c6c70 8: f0 fe 0b lock decb (%ebx) Code; c01c6c73 b: 0f 88 53 17 00 00 js 1764 <_EIP+0x1764> Code; c01c6c79 11: 8d 4e 08 lea 0x8(%esi),%ecx second, 4G RAM, 2xP4 xeon 2.4G, HT, 64G RAM support enabled, ext3, /home with noatime,nodiratime ksymoops 2.4.9 on i686 2.4.24-grsec-1. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.24-grsec-1/ (default) -m /boot/System.map-2.4.24-grsec-1 (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. eip: c01dc180 kernel BUG at /usr/src/kernel/linux-2.4.24-grsec/include/asm/spinlock.h:133! invalid operand: 0000 CPU: 0 EIP: 0010:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010082 eax: 0000000e ebx: d4a6de00 ecx: 00000002 edx: f6213f74 esi: efd5613c edi: 00000292 ebp: d4a6ddd8 esp: d4a6ddbc ds: 0018 es: 0018 ss: 0018 Process httpd (pid: 29534, stackpage=d4a6d000) Stack: c03b04d8 c01dc180 c011a080 c011a090 d4a6c000 d4a6de00 efd5613c d4a6de1c c0226e6d f774d600 f774d600 00000e00 00000000 00000000 d4a6c000 00000000 00000000 00000000 d4a6c000 efd56144 efd56144 efd56080 efd56080 f7c81f48 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 85 00 e0 07 3b c0 f0 fe 0e 0f 88 40 1b 00 00 8d 4b 08 >>EIP; c01dc1b4 <===== >>ebx; d4a6de00 <_end+146766c0/38544920> >>edx; f6213f74 <_end+35e1c834/38544920> >>esi; efd5613c <_end+2f95e9fc/38544920> >>ebp; d4a6ddd8 <_end+14676698/38544920> >>esp; d4a6ddbc <_end+1467667c/38544920> Trace; c01dc180 Trace; c0226e6d <__wait_on_freeing_inode+8d/d0> Trace; c0227f1d Trace; c02285b9 Trace; c0242e2c Trace; c0219630 Trace; c02194cb Trace; c0219cb4 Trace; c02248e1 Trace; c021a39a Trace; c021a9ac Trace; c0337bd5 Trace; c020a30c Trace; c0219063 Trace; c020a721 Trace; c01c7da3 Code; c01dc1b4 00000000 <_EIP>: Code; c01dc1b4 <===== 0: 0f 0b ud2a <===== Code; c01dc1b6 2: 85 00 test %eax,(%eax) Code; c01dc1b8 4: e0 07 loopne d <_EIP+0xd> Code; c01dc1ba 6: 3b c0 cmp %eax,%eax Code; c01dc1bc 8: f0 fe 0e lock decb (%esi) Code; c01dc1bf b: 0f 88 40 1b 00 00 js 1b51 <_EIP+0x1b51> Code; c01dc1c5 11: 8d 4b 08 lea 0x8(%ebx),%ecx 1 warning issued. Results may not be reliable. I can provide more information if needed SY, Vladimir