From: Soeren Sonnenburg <kernel@nn7.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: kswapd oops in 2.4.20 SMP+NFS
Date: 20 Mar 2003 15:23:24 +0100 [thread overview]
Message-ID: <1048170204.5161.11.camel@calculon> (raw)
Hi.
I got the following oops recently. The machine is still up and running
and was working stably for a year now...
Linux 2.4.20 #1 SMP Tue Dec 10 11:16:20 CET 2002 i686 unknown
2 x AMD K7-MP 1200MHz PCI(5-64) TYAN Thunder K7 S2462 Mainboard 1G ECC Memory
[...]
nfsd-fh: found a name that I didn't expect: sys/oz
nfsd-fh: found a name that I didn't expect: sys/oz
nfsd-fh: found a name that I didn't expect: bin/x86
nfsd-fh: found a name that I didn't expect: bin/x86
nfsd-fh: found a name that I didn't expect: etc/bla
VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
Unable to handle kernel paging request at virtual address 00268eb7
printing eip:
c014f5a3
*pde = 00000000
Oops: 0000
CPU: 1
EIP: 0010:[<c014f5a3>] Not tainted
EFLAGS: 00010202
eax: 00000000 ebx: e34b05c0 ecx: e34b05d0 edx: d1da1c40
esi: d6c03e00 edi: 00268ea7 ebp: 0000318e esp: f7edff34
ds: 0018 es: 0018 ss: 0018
Process kswapd (pid: 5, stackpage=f7edf000)
Stack: d1da1c58 e34b05c0 e34b05c0 c017a75f e34b05c0 d1da1c58 d1da1c40 c014cf20
d1da1c40 e34b05c0 00000006 000001d0 00000020 00000006 c014d2ab 000108c9
c0132046 00000006 000001d0 00000006 00000020 000001d0 c02d94b4 c02d94b4
Call Trace: [<c017a75f>] [<c014cf20>] [<c014d2ab>] [<c0132046>] [<c013209c>]
[<c01321a1>] [<c0132206>] [<c013232d>] [<c0105708>]
Code: 8b 47 10 85 c0 74 06 53 ff d0 83 c4 04 68 f0 a3 2d c0 8d 43
next reply other threads:[~2003-03-20 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 14:23 Soeren Sonnenburg [this message]
2003-03-21 8:28 ` kswapd oops in 2.4.20 SMP+NFS Oleg Drokin
2003-03-21 8:36 ` Soeren Sonnenburg
2003-03-21 9:50 ` Soeren Sonnenburg
2003-03-21 10:04 ` Oleg Drokin
[not found] ` <1048243299.9338.23.camel@fortknox>
[not found] ` <20030321135841.D17440@namesys.com>
2003-03-21 11:20 ` Soeren Sonnenburg
2003-03-21 13:56 ` Oleg Drokin
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=1048170204.5161.11.camel@calculon \
--to=kernel@nn7.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