[clue-tech] Re: kernel drivers (linux kernel: hde: drive_cmd:

[John Reilly]

On Wed, 2006-01-04 at 15:53 -0800, Hex Star wrote:
> Jan 3 15:45:05 linux kernel: hde: drive_cmd: status=0x51 { DriveReady
> SeekComplete Error }
> Jan 3 15:45:05 linux kernel: hde: drive_cmd: error=0x04 { DriveStatusError }
> Jan 3 15:45:05 linux kernel: hdf: drive_cmd: status=0x51 { DriveReady
> SeekComplete Error }
> Jan 3 15:45:05 linux kernel: hdf: drive_cmd: error=0x04 { DriveStatusError }
> Jan 3 15:45:05 linux [powersave_proxy][2336]: WARNING: hdparm returned error 5
> Jan 3 15:45:05 linux kernel: hdf: task_no_data_intr: status=0x51 {
> DriveReady SeekComplete Error }
> Jan 3 15:45:05 linux kernel: hdf: task_no_data_intr: error=0x04 {
> DriveStatusError }

Hi Hex,

According to hdreg.h, the error codes are

  /* Bits for HD_ERROR */
  #define MARK_ERR        0x01    /* Bad address mark */
  #define TRK0_ERR        0x02    /* couldn't find track 0 */
  #define ABRT_ERR        0x04    /* Command aborted */
  #define MCR_ERR         0x08    /* media change request */
  #define ID_ERR          0x10    /* ID field not found */
  #define MC_ERR          0x20    /* media changed */
  #define ECC_ERR         0x40    /* Uncorrectable ECC error */
  #define BBD_ERR         0x80    /* pre-EIDE meaning:  block marked bad
*/
  #define ICRC_ERR        0x80    /* new meaning:  CRC error during
transfer */


So you are seeing a Command Aborted error....and at the exact same time
I see a message from the powersave_proxy.  Is it possible that some
power saving action happening at that time and caused the hard drive to
abort what it was doing?

Regards,
John


_______________________________________________
CLUE-tech mailing list
CLUE-tech at cluedenver.org
http://cluedenver.org/mailman/listinfo/clue-tech