We have had several hardware problems complicating issues, but the
majority of our inexplicable crashes all take place within +/-15mins of
the same time of day, about every other day. Now _we_ aren't doing
anything at those times of day, so it's our guess that someone _else_ is
doing it to us.
Kudos to Alan Cox, for getting us thinking along the right lines to be
able to see the pattern in the outages.
Does anyone want to assess the relative stability of 2.0.34 or 2.0.35
under these conditions? They're busy production servers, and we can not
afford the bad press of the (presumed) DoS attacks any longer. (Nor can
we do any definitive logging or filtering. The Telco has mandated a
design that takes that out of our hands)
I recall reading that 2.0.34 was 'toxic' to the aic7xxx code (or vice
versa). What we _really_ need is good, stable, immune kernels that we
can slap on our boxes soonest.
Comments, please?
D
-- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GAT d- s++: a C++++$ UL++++B+++S+++C++H++U++V+++$ P+++$ L+++ E- W+++(--)$ N++ w++$>--- t+ 5++ X+() R+ tv b++++ DI+++ e- h-@ ------END GEEK CODE BLOCK------- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html