From: Axel Siebenwirth <axel@hh59.org>
To: linux-kernel@vger.kernel.org
Subject: 2.5.30: kernel BUG at slab.c:1290!
Date: Sat, 3 Aug 2002 20:33:20 +0200 [thread overview]
Message-ID: <20020803183320.GA283@prester.freenet.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2313 bytes --]
Hi,
following oops occured during normal operation.
Gzipped .config attached.
kernel BUG at slab.c:1290!
invalid operand: 0000
CPU: 0
EIP: 0010:[<c0136e31>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010013
eax: cb840fff ebx: cb840c00 ecx: cb840c00 edx: 00012800
esi: c11e36f8 edi: 00000400 ebp: 00000000 esp: c8323e7c
ds: 0018 es: 0018 ss: 0018
Stack: 0000007b 00000400 cb840c00 00000246 c11e36f8 c11e3700 000001d0
c0136b2a
c11e36f8 cbadb614 000000ff fffffff4 c98913cc 00000100 c015a261
c11e36f8
000001d0 c015a332 00000100 c11e20c8 000001d0 00000246 c11e20c0
c9891040
Call Trace: [<c0136b2a>] [<c015a261>] [<c015a332>] [<c0118449>] [<c0117dd3>]
[<c0118911>] [<c0122aaa>] [<c0122866>] [<c01233d0>] [<c0118d0f>]
[<c0141f57>]
[<c0105cd7>] [<c010762f>]
Code: 0f 0b 0a 05 aa eb 27 c0 81 e2 00 04 00 00 74 37 b8 a5 c2 0f
>>EIP; c0136e31 <kmem_cache_alloc_one_tail+a1/113> <=====
>>eax; cb840fff <_end+b510a5b/c5e5a5c>
>>ebx; cb840c00 <_end+b51065c/c5e5a5c>
>>ecx; cb840c00 <_end+b51065c/c5e5a5c>
>>esi; c11e36f8 <_end+eb3154/c5e5a5c>
>>esp; c8323e7c <_end+7ff38d8/c5e5a5c>
Trace; c0136b2a <__kmem_cache_alloc+4a/b0>
Trace; c015a261 <alloc_fd_array+21/30>
Trace; c015a332 <expand_fd_array+72/190>
Trace; c0118449 <copy_files+129/300>
Trace; c0117dd3 <dup_task_struct+43/b0>
Trace; c0118911 <copy_process+2f1/6c0>
Trace; c0122aaa <do_timer+7a/80>
Trace; c0122866 <update_wall_time+16/40>
Trace; c01233d0 <update_times+f0/100>
Trace; c0118d0f <do_fork+2f/c0>
Trace; c0141f57 <sys_llseek+d7/f0>
Trace; c0105cd7 <sys_fork+27/40>
Trace; c010762f <syscall_call+7/b>
Code; c0136e31 <kmem_cache_alloc_one_tail+a1/113>
00000000 <_EIP>:
Code; c0136e31 <kmem_cache_alloc_one_tail+a1/113> <=====
0: 0f 0b ud2a <=====
Code; c0136e33 <kmem_cache_alloc_one_tail+a3/113>
2: 0a 05 aa eb 27 c0 or 0xc027ebaa,%al
Code; c0136e39 <kmem_cache_alloc_one_tail+a9/113>
8: 81 e2 00 04 00 00 and $0x400,%edx
Code; c0136e3f <kmem_cache_alloc_one_tail+af/113>
e: 74 37 je 47 <_EIP+0x47> c0136e78
<kmem_cache_alloc_one_tail+e8/113>
Code; c0136e41 <kmem_cache_alloc_one_tail+b1/113>
10: b8 a5 c2 0f 00 mov $0xfc2a5,%eax
Regards,
Axel Siebenwirth
[-- Attachment #2: config-2.5.30.gz --]
[-- Type: application/x-gunzip, Size: 4571 bytes --]
reply other threads:[~2002-08-03 18:29 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=20020803183320.GA283@prester.freenet.de \
--to=axel@hh59.org \
--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