The machine will appear to work fine, but then the disk will spindown
and immediately restart, then the drive light stays on and the machine
is hung solid. It will not respond to SysRq, or anything other than
holding the power button down until it turns off. The last time the
disk restarted I noticed that it made similar seeking noises to what
it makes when being powered on. It is NOT crashing when making that
IBM click-boing noise.
Obviously this may be a hardware related problem, but IBM's drive
fitness test reports the drive to be OK, and I have not had the
problem when using kernels <= 2.4.17 (even after observing the problem
with 2.4.18). No IDE errors appear in the log before the crash.
The problem happens both when using noflushd and with noflushd
disabled. The lockups have all occured during low disk activity, but
95% of the time disk activity is low, so this may just be a
coincidence.
I would be happy to privide any further information that would be
useful in debugging this problem, but I am not sure how to provide
useful diagnostics for such a total and sudden lockup.
As long as I am posting IDE problems... On a different computer, every
time the machine boots I get the errors
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
repeated 4 times. hdc is an IBM-DTLA-307045 attached to an Intel
PIIX4 controller (440BX). IBM's drive fitness test does not report
any errors, and I have no other errors or difficulties in using the
drive. Should I be concerned?
-- Thanks, Jeff Lessem. - 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/