Re: 2.1.51 oopses in d_lookup

mb@ichabod.han.de
Sat, 23 Aug 1997 10:50:25 +0200 (MET DST)


You (James Mastros) wrote:
> Sounds like a dentry got corrupted (landed on bad memory). It's happened to
> me a couple of times, and I replaced some memory. <G> If userspace did

Yes, maybe, but I doubt that. The hardware worked flawlessly since
2.1.17. It just happened again a few minutes ago, and again it was
crond which triggered the oops, again in d_lookup, again a 'clear'
looping. Anyway, I'll stress test the memory over the weekend.

-- 
Michail Brzitwa            <mb@ichabod.han.de>            +49-511-343215