From: Sergey Vlasov <vsu@altlinux.ru>
To: Tejun Heo <htejun@gmail.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
linux-ide@vger.kernel.org, B.Zolnierkiewicz@elka.pw.edu.pl
Subject: Re: Host protected area on suspend/resume
Date: Wed, 13 Jul 2005 15:25:15 +0400 [thread overview]
Message-ID: <20050713152515.61c61ee2.vsu@altlinux.ru> (raw)
In-Reply-To: <42D3D87F.5040901@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
On Tue, 12 Jul 2005 23:49:35 +0900 Tejun Heo wrote:
> Matthew Garrett wrote:
> > On boot, Linux will attempt to disable the host protected area on a
> > disk. After a suspend/resume cycle, the BIOS may reenable it (seen on a
> > Thinkpad T40 and R40). As a result, the kernel is now unable to access
> > the HPA.
> >
> > Is there any issue with just adding a call to idedisk_check_hpa() in the
> > IDE resume code?
>
> This has come up several times now. One thing I'm curious about is
> why we are disabling HPA on boot without consent from the user. AFAIK,
> HPA is mostly used to implement hidden recovery/suspend storage areas
> and disabling automatically on boot increases the likeliness of
> destroying them. What do we gain by disabling HPA on boot? Are there
> some dumb machines which unnecessarily sets HPA and reduces the capacity
> of drives excessively? Even in such cases, wouldn't it be better to do
> idedisk_check_hpa() only when kernel parameter explicitly says so?
Support for disabling HPA during boot is needed mainly for old
machines with BIOS limitations. Some disks have jumpers which limit
capacity to 32 GB, so that such old BIOSes can recognize the disk
without hanging at boot; disabling HPA gives access to the whole
capacity.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-07-13 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 11:30 Host protected area on suspend/resume Matthew Garrett
2005-07-12 14:49 ` Tejun Heo
2005-07-12 15:07 ` Matthew Garrett
2005-07-12 15:15 ` Tejun Heo
2005-07-12 15:23 ` Greg Freemyer
2005-07-13 4:28 ` Grant Coady
2005-07-13 11:25 ` Sergey Vlasov [this message]
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=20050713152515.61c61ee2.vsu@altlinux.ru \
--to=vsu@altlinux.ru \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mjg59@srcf.ucam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.