linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Kernel Panic (NFS, 2.4.2[0-1])
@ 2003-08-10 21:16 war
  2003-08-11  8:45 ` Stephan von Krawczynski
  2003-08-11 15:07 ` Trond Myklebust
  0 siblings, 2 replies; 4+ messages in thread
From: war @ 2003-08-10 21:16 UTC (permalink / raw)
  To: linux-kernel

>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...

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Kernel Panic (NFS, 2.4.2[0-1])
  2003-08-10 21:16 Kernel Panic (NFS, 2.4.2[0-1]) war
@ 2003-08-11  8:45 ` Stephan von Krawczynski
  2003-08-11 12:55   ` war
  2003-08-11 15:07 ` Trond Myklebust
  1 sibling, 1 reply; 4+ messages in thread
From: Stephan von Krawczynski @ 2003-08-11  8:45 UTC (permalink / raw)
  To: war; +Cc: linux-kernel

On Sun, 10 Aug 2003 17:16:11 -0400 (EDT)
war <war@lucidpixels.com> wrote:

> >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.

What filesystem are you using?

Regards,
Stephan


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Kernel Panic (NFS, 2.4.2[0-1])
  2003-08-11  8:45 ` Stephan von Krawczynski
@ 2003-08-11 12:55   ` war
  0 siblings, 0 replies; 4+ messages in thread
From: war @ 2003-08-11 12:55 UTC (permalink / raw)
  To: Stephan von Krawczynski; +Cc: linux-kernel

ext2fs w/ 4096bytes per inode on all my Linux machines

On Mon, 11 Aug 2003, Stephan von Krawczynski wrote:

> On Sun, 10 Aug 2003 17:16:11 -0400 (EDT)
> war <war@lucidpixels.com> wrote:
>
> > >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.
>
> What filesystem are you using?
>
> Regards,
> Stephan
>
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Kernel Panic (NFS, 2.4.2[0-1])
  2003-08-10 21:16 Kernel Panic (NFS, 2.4.2[0-1]) war
  2003-08-11  8:45 ` Stephan von Krawczynski
@ 2003-08-11 15:07 ` Trond Myklebust
  1 sibling, 0 replies; 4+ messages in thread
From: Trond Myklebust @ 2003-08-11 15:07 UTC (permalink / raw)
  To: war; +Cc: linux-kernel


>From what I could see, the Oops you posted appeared rather to be
occurring in swapd before propagating to nfs. It would help if you
could decode it through ksymoops first though (see
linux/REPORTING-BUGS).

It would also help if you could try this out on the latest 2.4.22-rc kernel.

Cheers,
  Trond

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2003-08-12  0:03 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-08-10 21:16 Kernel Panic (NFS, 2.4.2[0-1]) war
2003-08-11  8:45 ` Stephan von Krawczynski
2003-08-11 12:55   ` war
2003-08-11 15:07 ` Trond Myklebust

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).