mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jure Pecar <pegasus@telemach.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19-pre10aa2: BUG at exit.c:530
Date: Tue, 18 Jun 2002 00:16:23 +0200	[thread overview]
Message-ID: <20020618001623.5b4b63db.pegasus@telemach.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 2966 bytes --]

Hi all,

I'm getting the following oops every now and then:

ksymoops 2.4.4 on i686 2.4.19-pre10.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.19-pre10/ (default)
     -m /boot/System.map-2.4.19-pre10 (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_maps): ksyms_base symbol
set_cpus_allowed_R__ver_set_cpus_allowed not found in System.map. 
Ignoring ksyms_base entry
kernel BUG at exit.c:530!
invalid operand: 0000
CPU:    0
EIP:    0010:[<c011dedd>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: cf382000   ebx: c281b200   ecx: 00000000   edx: 00000000
esi: cf382000   edi: 00000000   ebp: cf382000   esp: cf383fa8
ds: 0018   es: 0018   ss: 0018
Process slapd (pid: 5249, stackpage=cf383000)
Stack: cf382000 401cef1c 00000000 bfff6bc4 c011df12 00000000 c0108b5b
00000f21 
       bedffe38 bedffe40 080b67fc bedfff24 080b6724 00000000 0000002b
0000002b 
       00000078 4011a13e 00000023 00000292 bedffe38 0000002b 
Call Trace: [<c011df12>] [<c0108b5b>] 
Code: 0f 0b 12 02 40 34 28 c0 e9 5d fd ff ff 89 f6 8b 44 24 04 85 

>>EIP; c011dedd <do_exit+2f9/308>   <=====
Trace; c011df12 <sys_exit+e/10>
Trace; c0108b5b <system_call+2f/34>
Code;  c011dedd <do_exit+2f9/308>
00000000 <_EIP>:
Code;  c011dedd <do_exit+2f9/308>   <=====
   0:   0f 0b                     ud2a      <=====
Code;  c011dedf <do_exit+2fb/308>
   2:   12 02                     adc    (%edx),%al
Code;  c011dee1 <do_exit+2fd/308>
   4:   40                        inc    %eax
Code;  c011dee2 <do_exit+2fe/308>
   5:   34 28                     xor    $0x28,%al
Code;  c011dee4 <do_exit+300/308>
   7:   c0 e9 5d                  shr    $0x5d,%cl
Code;  c011dee7 <do_exit+303/308>
   a:   fd                        std    
Code;  c011dee8 <do_exit+304/308>
   b:   ff                        (bad)  
Code;  c011dee9 <do_exit+305/308>
   c:   ff 89 f6 8b 44 24         decl   0x24448bf6(%ecx)
Code;  c011deef <complete_and_exit+3/18>
  12:   04 85                     add    $0x85,%al


The system is a 4way xeon with 2gb ram, running sendmail+openldap+cyrus,
gcc version egcs-2.91.66. This is the fourth such oops in six days and
it always happened on slapd process. Before this kernel i was running
2.4.18rc2aa2 and everything was smooth, except the ext3 problem (that's
why i want to upgrade). Only modification i did to this kernel was
adding the ext3 0.9.18 patch.

Any ideas? Altough the box keeps on crunching mails, i'd sleep better
without these oopsen occuring.

-- 


Jure Pecar

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2002-06-17 22:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020618001623.5b4b63db.pegasus@telemach.net \
    --to=pegasus@telemach.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®