From: Tejun Heo <htejun@gmail.com>
To: "Rus V. Brushkoff" <rus@SoyuzKT.Od.UA>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: SATA HDD password problem
Date: Thu, 06 Mar 2008 18:47:34 +0900 [thread overview]
Message-ID: <47CFBDB6.8040400@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0803051443500.28213@Soyuz-KT.TeNet.Odessa.UA>
Hello,
Rus V. Brushkoff wrote:
> :> kernel, kernel send RESET to SATA drive and password need to be entered
> :again > - so the kernel panics because it cant mount rootfs. How this
> :problem can be solved ?
Which controller are you on? Can you please post full successful boot
log and the result of "hdparm -I /dev/sda"?
As SATA PHY events can happen at any time and PHY events mean COMRESET
which is hardreset for the device and resets most configurations, it's a
bit difficult. Basically, OS should record all relevant configurations
and reprogram the drive after such event. OS can also do thing which
are BIOS dependent via ACPI _GTF but the problem is that _GTF can only
issue no-data command and SECURITY_UNLOCK isn't one of them. Even if
that wasn't the problem, it's pretty dumb to pass clear text to OS via
ACPI method.
To solve the problem, ATA added Software Setting Preservation
featureset, which makes the drive remember configurations over
hardresets but it's an optional feature and not all drives implement it.
I think having SSP support in the drive is the only sane way to support
password locking on SATA; otherwise, the drive can just go away while
the system is running. That said, it would be nice to have a parameter
to force SRST or no reset at all for odd cases.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-03-06 9:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 9:50 SATA HDD password problem Rus V. Brushkoff
2008-03-05 12:30 ` Jeff Garzik
2008-03-05 12:49 ` Rus V. Brushkoff
2008-03-06 9:47 ` Tejun Heo [this message]
2008-03-06 12:31 ` Rus V. Brushkoff
2008-03-07 3:54 ` Tejun Heo
2008-03-07 9:17 ` Rus V. Brushkoff
2008-03-08 1:17 ` Tejun Heo
2008-03-08 16:12 ` Rus V. Brushkoff
2008-03-09 5:13 ` Tejun Heo
2008-03-09 5:13 ` Tejun Heo
2008-03-09 17:42 ` Rus V. Brushkoff
2008-03-10 0:37 ` Tejun Heo
2008-03-10 1:25 ` [PATCH #upstream-fixes] ahci: implement skip_host_reset parameter Tejun Heo
2008-03-17 12:27 ` Jeff Garzik
2008-03-07 14:45 ` SATA HDD password problem Mark Lord
2008-03-08 0:51 ` Tejun Heo
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=47CFBDB6.8040400@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=rus@SoyuzKT.Od.UA \
/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).