From: war <war@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel Panic (NFS, 2.4.2[0-1])
Date: Sun, 10 Aug 2003 17:16:11 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.56.0308101710110.10609@p500> (raw)
>From /etc/fstab:
p500:/d1/x /p500/x nfs rw,hard,intr,rsize=65536,wsize=65536,nfsvers=3 0 0
A small for loop in bash causes 2.4.20 to panic, and 2.4.21 to have
massive network packet loss.
for i in `seq 1 10`
do
/usr/bin/time /bin/cp /p500/x/20GB . ; rm -f 20GB; sync; sleep 5
done
I left the box unattended for an hour or two, I return to find the screen
black, and the and caps key and scroll lock key blinking, however the
numlock key was not blinking.
The run before it crashed was:
-rw-r--r-- 1 war wheel 1.4G 2003-08-10 15:25 20GB
I no longer run any binary only modules.
The modules I run are:
war@war:~$ lsmod
Module Size Used by Not tainted
w83781d 20656 0
i2c-isa 1160 0 (unused)
i2c-algo-pcf 5404 0 (unused)
i2c-algo-bit 7624 0 (unused)
i2c-dev 4452 0 (unused)
i2c-proc 7152 0 [w83781d]
i2c-core 13060 0 [w83781d i2c-isa i2c-algo-pcf i2c-algo-bit i2c-dev i2c-proc]
emu10k1 62344 0
ac97_codec 11080 0 [emu10k1]
sound 58196 0 [emu10k1]
war@war:~$
I will once again run this loop and see if I can get it to produce the
same result or similiar behavior.
I have an Intel i875 based motherboard (Abit IC7-G), P4 2.6GHZ C w/HT
enabled.
So far, the only way it seems to die/messup/etc, is doing large file
transfer operations over NFS.
Also, incase you are wondering, I have used memtest86 several times, and
the ram (2GB) (4x512(333 DDR)) ram passes all tests with no errors.
If anyone has any idea what could be wrong, I'd love to hear them...
next reply other threads:[~2003-08-11 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-10 21:16 war [this message]
2003-08-11 8:45 ` Stephan von Krawczynski
2003-08-11 12:55 ` war
2003-08-11 15:07 ` Trond Myklebust
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=Pine.LNX.4.56.0308101710110.10609@p500 \
--to=war@lucidpixels.com \
--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®