From: Jan Tim Schueszler <Jan.Tim.Schueszler@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: {Kernel 2.4.17-pre8] Another kernel-oops
Date: Sun, 16 Dec 2001 22:01:23 +0000 [thread overview]
Message-ID: <01121622012300.04669@erde> (raw)
I just discovered another kernel-oops with my 2.4.17-pre8-kernel.
It occured during deleting a directory recursively.
Dec 16 21:53:49 erde kernel: invalid operand: 0000
Dec 16 21:53:49 erde kernel: CPU: 0
Dec 16 21:53:49 erde kernel: EIP: 0010:[prune_dcache+93/304]
Not tainted
Dec 16 21:53:49 erde kernel: EFLAGS: 00010202
Dec 16 21:53:49 erde kernel: eax: 00000010 ebx: c77db1d8 ecx:
c77db000 edx: c77db258
Dec 16 21:53:49 erde kernel: esi: c77db1c0 edi: 00000000 ebp:
00000008 esp: c7b71f48
Dec 16 21:53:49 erde kernel: ds: 0018 es: 0018 ss: 0018
Dec 16 21:53:49 erde kernel: Process rm (pid: 13831,
stackpage=c7b71000)
Dec 16 21:53:49 erde kernel: Stack: c655b840 c6a46dfc c655b840
c6a46d80 c013fd0d 00000074 c655b840 c01398e0
Dec 16 21:53:49 erde kernel: c655b840 c655e33c c0139a21
c655b840 c655b840 c655b840 cd8e2000 c7b71fa4
Dec 16 21:53:49 erde kernel: c0139b7f c6a46d80 c655b840
c7b70000 bfffebf4 0804f0c0 bfffec9c c6c03140
Dec 16 21:53:49 erde kernel: Call Trace:
[shrink_dcache_parent+13/32] [d_unhash+32/80] [vfs_rmdir+273/432]
[sys_rmdir+191/256] [system_call+51/56]
Dec 16 21:53:49 erde kernel: Code: 0f 0b 8d 46 10 8b 48 04 8b 53 f8
89 4a 04 89 11 89 43 f8 89
Code; d0d373f1 <END_OF_CODE+3c7bb0/????>
00000000 <_EIP>:
Code; d0d373f1 <END_OF_CODE+3c7bb0/????>
0: 0f 0b ud2a
Code; d0d373f3 <END_OF_CODE+3c7bb2/????>
2: 8d 46 10 lea 0x10(%esi),%eax
Code; d0d373f6 <END_OF_CODE+3c7bb5/????>
5: 8b 48 04 mov 0x4(%eax),%ecx
Code; d0d373f9 <END_OF_CODE+3c7bb8/????>
8: 8b 53 f8 mov 0xfffffff8(%ebx),%edx
Code; d0d373fc <END_OF_CODE+3c7bbb/????>
b: 89 4a 04 mov %ecx,0x4(%edx)
Code; d0d373ff <END_OF_CODE+3c7bbe/????>
e: 89 11 mov %edx,(%ecx)
Code; d0d37401 <END_OF_CODE+3c7bc0/????>
10: 89 43 f8 mov %eax,0xfffffff8(%ebx)
Code; d0d37404 <END_OF_CODE+3c7bc3/????>
13: 89 00 mov %eax,(%eax)
1 warning issued. Results may not be reliable.
reply other threads:[~2001-12-16 21:02 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=01121622012300.04669@erde \
--to=jan.tim.schueszler@gmx.de \
--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