Before this, it had been running for about 22 hours fine, lots of disk
activity (though not heavy activity), lots of online stuff.
I'd usually put a whole sequence of crashes down to overheating, but all
the components are quite cool (the video card is the hottest part, and
it is still only warm), the system isn't dusty or anything, none of the
cables are stretched, and most importantly, I've never had these crashes
with 2.0.{29,30}, but always with all the 2.1.x that I've tried.
I should add that this is compiled with GCC 2.8.0. However all earlier
kernels I tried (including several 2.1.x that crashed like this) were
compiled with GCC 2.7.2.3.
All the recent freezes happened during disk activity, while I was here.
I can be reasonably certain the disk has something to do with it.
Of course, it might simply be heavy interrupt activity -- the disk is by
far the biggest generator of interrupts.
As an experiment, I am now using ide0=nodma. (The boot messages are the
same though, so I'm not really sure if DMA was being used before). I
notice 32-bit mode isn't on either. I'll just leave it like that.
If it crashes now, I'll know that has something to do with it.
Unfortunately it isn't terribly reproducible so I'll never be sure, and
it will take a couple of weeks to get a statistically significant idea.
(Going by the best uptime I had with 2.1.82 -- 7 days).
Funny, it hasn't crashed while I write this message.... Could just be
luck though.
-- Jamie
[ I have an AMD K6-233 (without the bug), 64Mb SDRAM, an FIC PA-2011
motherboard (with one of the VIA chipsets), a 6.4G Quantum Fireball ST
disk (IDE), a Matrox Millenium II, and a Creative Labs SoundBlaster 16.
[A Wintel PC with no Windows and no Intel chips <grin>] ].
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu