Re: oops on 2.4.13-pre5 in prune_dcache

Dave Airlie (airlied@csn.ul.ie)
Wed, 31 Oct 2001 10:37:31 +0000 (GMT)

> and because dentry->d_op isn't NULL, we oops on the d_op->d_iput
> dereference.
>
> Something is setting a bit in your dentry. Either RAM errors (do you
> have ECC memory or a history of SIGSEGV's to give any indication either
> way?) or a wild "set_bit()" pointer or similar.
>

well I've never seen any OOPS on this machine before or segv on this
machine and I use it for cross-compiling glibc/gdb/binutils/gcc/kernels
etc for the VAX port of Linux so I'm sure I'd have seen one before if it
was memory... I can run memtest on it at some stage over the next couple
of days but I'm pretty confident the RAM is okay.. granted its not ECC...

I have nothing unusual in my config I don't think,

ext2, nfsd, vfat, sb16, parport, ne2k-pci (x2 cards)...I can post my
.config later on today when I get back home..

Dave.

>

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied@skynet.ie
pam_smb / Linux DecStation / Linux VAX / ILUG person




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/