From: Jens Axboe <axboe@suse.de>
To: "Mudama, Eric" <eric_mudama@maxtor.com>
Cc: "'Rafal Bujnowski'" <bujnor@go2.pl>,
linux-kernel <linux-kernel@vger.kernel.org>,
Maciej Soltysiak <solt@dns.toxicfilms.tv>
Subject: Re: hdb: dma_timer_expiry: dma status == 0x64 [2.5.69]
Date: Wed, 14 May 2003 19:40:50 +0200 [thread overview]
Message-ID: <20030514174050.GQ15261@suse.de> (raw)
In-Reply-To: <785F348679A4D5119A0C009027DE33C102E0D35F@mcoexc04.mlm.maxtor.com>
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.
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.
--
Jens Axboe
next prev parent reply other threads:[~2003-05-14 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 17:29 hdb: dma_timer_expiry: dma status == 0x64 [2.5.69] Mudama, Eric
2003-05-14 17:40 ` Jens Axboe [this message]
2003-05-14 18:50 ` Bartlomiej Zolnierkiewicz
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 19:48 Maciej Soltysiak
2003-05-14 13:47 ` Zephaniah E. Hull
2003-05-14 14:13 ` Maciej Soltysiak
2003-05-14 15:22 ` Zephaniah E. Hull
2003-05-14 16:06 ` Rafal Bujnowski
2003-05-14 14:14 ` Danny ter Haar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030514174050.GQ15261@suse.de \
--to=axboe@suse.de \
--cc=bujnor@go2.pl \
--cc=eric_mudama@maxtor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=solt@dns.toxicfilms.tv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox