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

[Mudama, Eric]

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.

--eric

-----Original Message-----
From: Rafal Bujnowski [mailto:[e-mail]]
Sent: Wednesday, May 14, 2003 10:06 AM
To: linux-kernel
Cc: Maciej Soltysiak
Subject: Re: hdb: dma_timer_expiry: dma status == 0x64 [2.5.69]

A Maciej Soltysiak <[e-mail]> na to:

> Exactly like me.
> Someone suggested Bartlomiej Zolnierkiewicz's patch.
> Try this on for size. I haven't tested it yet, but please give it a
> shot.

Hello!

It doesn't work. I still get:

hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }

I'll try Dany's hint.

rafal

-- 

[              Rafal Bujnowski ][ e-mail: bujnor<at>go2.pl            ]
[     http://www.bujnor.iq.pl/ ][ e-mail: bujnor<at>poczta.onet.pl    ]
[   ICQ: 85602025  GG: 4174829 ][ Jabber: [e-mail]           ]