From: "crisper@optonline.net" <crisper@optonline.net>
To: linux-kernel@vger.kernel.org
Subject: Oops in 2.4.4-ac6, ksymoops output included
Date: Fri, 11 May 2001 17:52:24 -0400 (EDT) [thread overview]
Message-ID: <0GD600C9PY3CHH@mta4.srv.hcvlny.cv.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 5679 bytes --]
I got this oops while running 2.4.4-ac6 and trying to open a file to edit with
vi. I have had this happen before while I was opening a text file but I
suspect that it is just coincidence. I have included the ksymoops output for
the oops and also my kernel configuration. If there are any patches or if
there is any more information that anyone needs then please let me know.
Thanks,
Sean
ksymoops info:
ksymoops 2.4.1 on i686 2.4.4-ac6. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.4-ac6/ (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.
Warning (read_object): no symbols in
/lib/modules/2.4.4-ac6/build/drivers/pnp/pnp.o
Warning (read_object): no symbols in
/lib/modules/2.4.4-ac6/build/drivers/misc/misc.o
Warning (read_object): no symbols in
/lib/modules/2.4.4-ac6/build/drivers/media/radio/radio.o
Warning (read_object): no symbols in
/lib/modules/2.4.4-ac6/build/drivers/media/video/video.o
Warning (read_object): no symbols in
/lib/modules/2.4.4-ac6/build/drivers/media/media.o
Warning (read_object): no symbols in
/lib/modules/2.4.4-ac6/build/drivers/parport/driver.o
Warning (read_object): no symbols in
/lib/modules/2.4.4-ac6/build/crypto/crypto.o
May 10 18:01:49 hehehe kernel: c0116008
May 10 18:01:49 hehehe kernel: Oops: 0002
May 10 18:01:49 hehehe kernel: CPU: 0
May 10 18:01:49 hehehe kernel: EIP: 0010:[release_task+24/336]
May 10 18:01:49 hehehe kernel: EIP: 0010:[<c0116008>]
Using defaults from ksymoops -t elf32-i386 -a i386
May 10 18:01:49 hehehe kernel: EFLAGS: 00013246
May 10 18:01:49 hehehe kernel: eax: 00000100 ebx: d51b2000 ecx: 00000000
edx: bfffe49c
May 10 18:01:49 hehehe kernel: esi: c672c000 edi: 00003c46 ebp: 00000000
esp: c672df84
May 10 18:01:49 hehehe kernel: ds: 0018 es: 0018 ss: 0018
May 10 18:01:49 hehehe kernel: Process configure (pid: 15429,
stackpage=c672d000)
May 10 18:01:49 hehehe kernel: Stack: d51b2000 c0116c56 d51b2000 00000000
c672c000 00000000 00000000 00000000
May 10 18:01:49 hehehe kernel: c672c000 c672c0ac c672c0ac c672c000
00000000 0810608c bfffe468 c0106d47
May 10 18:01:49 hehehe kernel: ffffffff bfffe49c 00000000 00000000
0810608c bfffe468 00000072 0000002b
May 10 18:01:49 hehehe kernel: Call Trace: [sys_wait4+790/928]
[system_call+51/56]
May 10 18:01:49 hehehe kernel: Call Trace: [<c0116c56>] [<c0106d47>]
May 10 18:01:49 hehehe kernel: Code: 00 00 ff 48 04 8b 8b d4 01 00 00 51 e8 17
4d 00 00 8b 43 3c
>>EIP; c0116008 <release_task+18/150> <=====
Trace; c0116c56 <sys_wait4+316/3a0>
Trace; c0106d47 <system_call+33/38>
Code; c0116008 <release_task+18/150>
00000000 <_EIP>:
Code; c0116008 <release_task+18/150> <=====
0: 00 00 add %al,(%eax) <=====
Code; c011600a <release_task+1a/150>
2: ff 48 04 decl 0x4(%eax)
Code; c011600d <release_task+1d/150>
5: 8b 8b d4 01 00 00 mov 0x1d4(%ebx),%ecx
Code; c0116013 <release_task+23/150>
b: 51 push %ecx
Code; c0116014 <release_task+24/150>
c: e8 17 4d 00 00 call 4d28 <_EIP+0x4d28> c011ad30
<free_uid+0/30>
Code; c0116019 <release_task+29/150>
11: 8b 43 3c mov 0x3c(%ebx),%eax
May 10 18:01:49 hehehe kernel: <1>Unable to handle kernel NULL pointer
dereference at virtual address 00000100
May 10 18:01:49 hehehe kernel: c0116008
May 10 18:01:49 hehehe kernel: Oops: 0002
May 10 18:01:49 hehehe kernel: CPU: 0
May 10 18:01:49 hehehe kernel: EIP: 0010:[release_task+24/336]
May 10 18:01:49 hehehe kernel: EIP: 0010:[<c0116008>]
May 10 18:01:49 hehehe kernel: EFLAGS: 00010246
May 10 18:01:49 hehehe kernel: eax: 00000100 ebx: d51b2000 ecx: 00000000
edx: bffff3cc
May 10 18:01:49 hehehe kernel: esi: c188e000 edi: 00003c46 ebp: 00000000
esp: c188ff84
May 10 18:01:49 hehehe kernel: ds: 0018 es: 0018 ss: 0018
May 10 18:01:49 hehehe kernel: Process init (pid: 1, stackpage=c188f000)
May 10 18:01:49 hehehe kernel: Stack: d51b2000 c0116c56 d51b2000 00000000
c188e000 00000000 00000000 00000000
May 10 18:01:49 hehehe kernel: c188e000 c188e0ac c188e0ac c188e000
00000000 bffff3cc bffff3ac c0106d47
May 10 18:01:49 hehehe kernel: ffffffff bffff3cc 00000001 00000000
bffff3cc bffff3ac 00000072 0000002b
May 10 18:01:49 hehehe kernel: Call Trace: [sys_wait4+790/928]
[system_call+51/56]
May 10 18:01:49 hehehe kernel: Call Trace: [<c0116c56>] [<c0106d47>]
May 10 18:01:49 hehehe kernel: Code: 00 00 ff 48 04 8b 8b d4 01 00 00 51 e8 17
4d 00 00 8b 43 3c
>>EIP; c0116008 <release_task+18/150> <=====
Trace; c0116c56 <sys_wait4+316/3a0>
Trace; c0106d47 <system_call+33/38>
Code; c0116008 <release_task+18/150>
00000000 <_EIP>:
Code; c0116008 <release_task+18/150> <=====
0: 00 00 add %al,(%eax) <=====
Code; c011600a <release_task+1a/150>
2: ff 48 04 decl 0x4(%eax)
Code; c011600d <release_task+1d/150>
5: 8b 8b d4 01 00 00 mov 0x1d4(%ebx),%ecx
Code; c0116013 <release_task+23/150>
b: 51 push %ecx
Code; c0116014 <release_task+24/150>
c: e8 17 4d 00 00 call 4d28 <_EIP+0x4d28> c011ad30
<free_uid+0/30>
Code; c0116019 <release_task+29/150>
11: 8b 43 3c mov 0x3c(%ebx),%eax
May 10 18:01:49 hehehe kernel: <0>Kernel panic: Attempted to kill init!
8 warnings issued. Results may not be reliable.
[-- Attachment #2: .config --]
[-- Type: application/x-unknown, Size: 18511 bytes --]
next reply other threads:[~2001-05-11 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 21:52 crisper [this message]
2001-05-12 4:47 ` Keith Owens
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=0GD600C9PY3CHH@mta4.srv.hcvlny.cv.net \
--to=crisper@optonline.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®