On Thu, Apr 05, 2001 at 06:09:28PM +0300, Ville Herva wrote:
> I wonder if there might still be a bug in 2.0.39 sys_new(l)stat.
> Today, one of my trustworthy servers crashed (see details below), and
> it has actually given me two slightly similar looking oopses before.
>
> While this might be a hardware problem (I'll run memory test asap), it
> seems that the oopses are quite similar and could perhaps be caused by
> a kernel bug.
>
> This is vanilla 2.0.39 (2.0.37 before), gcc-2.7.2.3, Ppro-200, Intel
> motherboard etc. It has been very reliable in past. These oopses are
> the _only_ problems. It runs qmail, samba, cvs, rsync, apache, pop,
> sshd and oracle. All local fs's are plain ext2.
>
> I hope somebody (with more kernel hacking experience than me) is still
> interested in the 2.0.39. I'll be happy to provide any additional
> details or try something. The oops will propably be hard to reproduce,
> however.
I'll look into it. A note, however: the additional oops:es that follow
the first one are almost never ever useful, because the system is no
longer in a consistent state after the first one.
/David, maintainer of the v2.0.xx kernel series
_ _
// David Weinehall <[EMAIL PROTECTED]> /> Northern lights wander \\
// Project MCA Linux hacker // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
