From: thomas schorpp <t.schorpp@gmx.de>
To: Mark Lord <liml@rtr.ca>
Cc: linux-ide@vger.kernel.org
Subject: Re: hdparm ATA Security Options return errors
Date: Wed, 19 Oct 2005 18:24:47 +0200 [thread overview]
Message-ID: <4356734F.6050303@gmx.de> (raw)
In-Reply-To: <4356624A.2000307@rtr.ca>
Mark Lord wrote:
> thomas schorpp wrote:
>
>> Mark Lord wrote:
>>
>>> I think the entire set of ATA security patches that were
>>> sent to me for hdparm are bogus -- I lack the setup here
>>> to try them, but another kind person is preparing patches
>>> for hdparm to fix them.
>
>
> hdparm-6.3 is now out, with working security commands.
>
> But there is still a bug deep in the IDE taskfile code
> that sometimes causes problems. Someday I might have time
> to dig deeper into the kernel and fix that issue.
>
> -ml
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
test01:
vanilla kernel 2.6.13.4
no security enabled before, no passwort.
hdparm --security-disable xxxx /dev/hde
Oct 19 18:15:51 tom1 kernel: hde: status timeout: status=0xd0 { Busy }
Oct 19 18:15:51 tom1 kernel: ide: failed opcode was: 0xf2
Oct 19 18:15:51 tom1 kernel: hde: no DRQ after issuing MULTWRITE_EXT
Oct 19 18:15:51 tom1 kernel: hde: status error: status=0x00 { }
Oct 19 18:15:51 tom1 kernel: ide: failed opcode was: 0xf6
Oct 19 18:15:51 tom1 kernel: hde: no DRQ after issuing MULTWRITE_EXT
sync problem?
ATA device, with non-removable media
Model Number: ST3120026A
Serial Number: 3JT4RYCB
Firmware Revision: 8.01
Standards:
Used: ATA/ATAPI-6 T13 1410D revision 2
Supported: 6 5 4 3
sil680 controller
i'll test the SET commands on the older seagate
next prev parent reply other threads:[~2005-10-19 16:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1750797AbVJQQjQ/20051017163916Z+71@vger.kernel.org>
2005-10-17 17:14 ` hdparm ATA Security Options return errors thomas schorpp
2005-10-17 17:41 ` thomas schorpp
2005-10-17 20:31 ` Mark Lord
2005-10-17 20:52 ` thomas schorpp
2005-10-19 7:56 ` thomas schorpp
2005-10-19 15:12 ` Mark Lord
2005-10-19 15:20 ` thomas schorpp
2005-10-19 16:24 ` thomas schorpp [this message]
2005-10-20 3:10 ` Mark Lord
2005-10-19 17:35 Timothy Thelin
2005-10-20 3:09 ` Mark Lord
2005-10-20 7:51 ` thomas schorpp
2005-10-20 11:18 ` thomas schorpp
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=4356734F.6050303@gmx.de \
--to=t.schorpp@gmx.de \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).