What has changed in 2.1.7x ? What can cause the problems?
Are disk operations being performed more agresively?
Controller is on-board (486) ALI chipset based with "ide0=ali14xx" enabled,
but no settings is performed using hdparm (standard settings)
It may be a hardware problem, but why the problem does not appear in older
kernels ????
[hdd is ST157A; similar if connected as hdc]
hdd: write_intr: status=0x90 { Busy }
ide1: reset: master: error (0x00?)
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: drive not ready for command
ide1: reset: success
hdd: write_intr: status=0x65 { DriveReady DeviceFault CorrectedError Error }
hdd: write_intr: error=0x20 { }
hdd: status error: status=0x65 { DriveReady DeviceFault CorrectedError Error }
hdd: status error: error=0x20 { }
hdd: no DRQ after issuing WRITE
hdd: write_intr: status=0x00 { }
hdd: status error: status=0x00 { }
hdd: drive not ready for command
hdd: status error: status=0x00 { }
hdd: drive not ready for command
hdd: status error: status=0x00 { }
hdd: drive not ready for command
ide1: reset: master: error (0x00?)
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: drive not ready for command
ide1: reset: success
hdd: write_intr: status=0x00 { }
hdd: status error: status=0x00 { }
hdd: drive not ready for command
hdd: status error: status=0x00 { }
hdd: drive not ready for command
hdd: status error: status=0x00 { }
hdd: drive not ready for command
ide1: reset: master: error (0x00?)
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: drive not ready for command
ide1: reset: success
[... and so on]
-- ======================================================================= Andrzej M. Krzysztofowicz ankry@mif.pg.gda.pl tel. (0-58) 347 14 61 Wydz.Fizyki Technicznej i Matematyki Stosowanej Politechniki Gdanskiej