From: David Flynn <davidf@woaf.net>
To: linux-kernel@vger.kernel.org
Subject: Oops with 2.4.17 + NFS patches
Date: Mon, 18 Nov 2002 23:59:36 +0000 [thread overview]
Message-ID: <20021118235936.GB18838@woaf.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2771 bytes --]
Hello lkml people,
The following is the output of an oops that occurred on an AMD Athlon XP
running kernel 2.4.17 with all the 2.4.17 NFS patches applied (from
http://nfs.sf.net/). The kernel is optimised for P3(Cu).
Something which may be quite important is that we are seeing some quite
random behavior with this machine, it will be fine for a good few hours
then we will get random processes being killed with SIGSEGV / SIGBUS.
All RAM has been replaced in the machine, and we have changed kernels from
2.4.18 to 2.4.17, both show the same behavior.
Any information would be most appreciated!
Kind Regards,
David
--an oops--
Unable to handle kernel paging request at virtual address 3d3f3f4f
c0113211
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<c0113211>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010202
eax: 3d3f3f3b ebx: cbd15e00 ecx: ca62c848 edx: 000000ef
esi: c6ee3b40 edi: cbd15e40 ebp: c16eb844 esp: cdac5f54
ds: 0018 es: 0018 ss: 0018
Process root (pid: 3140, stackpage=cdac5000)
Stack: c999e000 cdac45a0 c999e5a0 00000011 00000008 00000100 ca62c848 c6ee3b00
c0113552 00000011 c999e000 cdac4000 bffff8ec 00000000 cdac5fbc 00000000
fffffff4 00000000 c012df24 cdac4000 bffff804 c01059e0 00000011 bffff850
Call Trace: [<c0113552>] [<c012df24>] [<c01059e0>] [<c0106d1b>]
Code: ff 40 14 89 45 00 83 c5 04 4a 75 e3 8b 43 08 2b 44 24 14 8d
>>EIP; c0113211 <copy_files+189/260> <=====
>>ebx; cbd15e00 <_end+ba343e4/1061f5e4>
>>ecx; ca62c848 <_end+a34ae2c/1061f5e4>
>>esi; c6ee3b40 <_end+6c02124/1061f5e4>
>>edi; cbd15e40 <_end+ba34424/1061f5e4>
>>ebp; c16eb844 <_end+1409e28/1061f5e4>
>>esp; cdac5f54 <_end+d7e4538/1061f5e4>
Trace; c0113552 <do_fork+26a/650>
Trace; c012df24 <sys_llseek+120/12c>
Trace; c01059e0 <sys_fork+14/1c>
Trace; c0106d1b <system_call+33/38>
Code; c0113211 <copy_files+189/260>
00000000 <_EIP>:
Code; c0113211 <copy_files+189/260> <=====
0: ff 40 14 incl 0x14(%eax) <=====
Code; c0113214 <copy_files+18c/260>
3: 89 45 00 mov %eax,0x0(%ebp)
Code; c0113217 <copy_files+18f/260>
6: 83 c5 04 add $0x4,%ebp
Code; c011321a <copy_files+192/260>
9: 4a dec %edx
Code; c011321b <copy_files+193/260>
a: 75 e3 jne ffffffef <_EIP+0xffffffef> c0113200 <copy_files+178/260>
Code; c011321d <copy_files+195/260>
c: 8b 43 08 mov 0x8(%ebx),%eax
Code; c0113220 <copy_files+198/260>
f: 2b 44 24 14 sub 0x14(%esp,1),%eax
Code; c0113224 <copy_files+19c/260>
13: 8d 00 lea (%eax),%eax
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
reply other threads:[~2002-11-18 23:52 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=20021118235936.GB18838@woaf.net \
--to=davidf@woaf.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®