From: Tejun Heo <tj@kernel.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Christof Warlich <christof@warlich.name>,
Tejun Heo <htejun@gmail.com>,
linux-kernel@vger.kernel.org, ide <linux-ide@vger.kernel.org>
Subject: Re: "EXT3-fs error" after resume from s2ram
Date: Fri, 10 Jul 2009 22:21:13 +0900 [thread overview]
Message-ID: <4A574049.5090708@kernel.org> (raw)
In-Reply-To: <51f3faa70907091631s329255en5fc197091b9ae4f0@mail.gmail.com>
Hello,
Robert Hancock wrote:
> On Thu, Jul 9, 2009 at 12:17 PM, Christof Warlich<christof@warlich.name> wrote:
>> Just one clarification: From what I understood so far, it will be impossible
>> to ever utilize the full disk capacity as long as the BIOS applies the HPA
>> on boot, right?
>
> I believe that's the case, yes.. if the BIOS is applying the HPA on
> each boot, then we can't change the max address again without a
> hardware reset..
This is one of the reasons why libata was switched to prefer hardreset
so that BIOS lock downs can be circumvented. PATA drivers
unfortunately usually don't implement hardreset. :-(
I'll forward the patch upstream.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-07-10 13:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 13:37 "EXT3-fs error" after resume from s2ram Christof Warlich
2009-06-29 0:18 ` Robert Hancock
2009-06-29 13:54 ` Christof Warlich
2009-06-30 0:28 ` Robert Hancock
2009-06-30 5:37 ` Christof Warlich
2009-07-02 5:17 ` Robert Hancock
2009-07-06 9:51 ` Christof Warlich
2009-07-07 0:13 ` Robert Hancock
2009-07-07 7:04 ` Christof Warlich
2009-07-07 9:13 ` Christof Warlich
2009-07-07 14:19 ` Robert Hancock
2009-07-07 17:42 ` Christof Warlich
2009-07-07 23:30 ` Robert Hancock
2009-07-08 6:41 ` Christof Warlich
2009-07-08 14:28 ` Tejun Heo
2009-07-08 15:21 ` Tejun Heo
2009-07-09 18:17 ` Christof Warlich
2009-07-09 23:31 ` Robert Hancock
2009-07-10 13:21 ` Tejun Heo [this message]
2009-07-08 15:50 ` Christof Warlich
2009-07-09 23:19 ` Pavel Machek
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=4A574049.5090708@kernel.org \
--to=tj@kernel.org \
--cc=christof@warlich.name \
--cc=hancockrwd@gmail.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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 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.