Re: hdb: dma_timer_expiry: dma status == 0x64 [2.5.69]

[Bartlomiej Zolnierkiewicz]

On Wed, 14 May 2003, Jens Axboe wrote:

> On Wed, May 14 2003, Mudama, Eric wrote:
> > 0x5104 is a different can of worms from the other stuff you guys were
> > reporting.
> >
> > 5104 (status register = 0x51, error register 0x04) is the all-encompassing
> > "command abort" which is what the drive does any time you issue a command
> > with bad parameters, an invalid (immoral?) command, or some of the security
> > stuff out of sequence.  Most commonly it is seen attempting to enable
> > features on a drive that doesn't support them.

In reality its harmless, only noisy, ide driver tryied to do something
like checking max native address and drive doesn't support it.

> Which reminds me that it has always annoyed me that Linux doesn't print
> the failed command. Just leaves a lot of guess work... I'll try and
> remedy that.

Which reminds me that somebody (me?) should fix hdparm to not use
WIN_IDENTIFY with HDIO_DRIVE_CMD ioctl but use HDIO_GET_IDENTIFY ioctl.
This command will be aborted by ATAPI device and hdparm don't know
if device is ATA or ATAPI, it currently only works because ioctl handler
reads data from device *before* checking status (or something like that).

Back on topic: Jens, you can also check current status of per driver
->abort() introduced by Alan.

btw. I will be quite busy for next 3 weeks (exams), so expect long
     delays in replies and slower ide progress.

--
Bartlomiej

> --
> Jens Axboe