From: Nate Lawson <nate@root.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ACPI] IDE failure on ACPI resume
Date: Thu, 17 Mar 2005 12:34:02 -0800 [thread overview]
Message-ID: <4239E9BA.7050105@root.org> (raw)
In-Reply-To: <1111072221.8136.171.camel@tyrosine>
Matthew Garrett wrote:
> On Sun, 2005-03-13 at 20:53 -0800, Nate Lawson wrote:
>
>
>>Sounds like PCI not being completely restored. We had to work around
>>some weird ATA issues in FreeBSD with the status register being invalid
>>for quite a while after resume. A retry loop was the solution.
>
>
> FreeBSD seems to fail in the same way on the same hardware,
> unfortunately. I'm leaning towards suspecting that we need to be doing
> something with the contents of the _GTF method, but by the looks of that
> that requires us to be able to work out which methods correspond to
> which hardware. Is anyone working on implementing this?
>
Very interesting. I was hoping to someday have _GTF et al implemented
but the ATA knowledge required was above my head. I also strongly
suspected that the info published by _GTF would likely be invalid. Does
Windows actually use that method or just hardcoded ATA initialization?
--
Nate
next prev parent reply other threads:[~2005-03-17 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 19:14 IDE failure on ACPI resume Matthew Garrett
2005-03-14 4:53 ` [ACPI] " Nate Lawson
2005-03-17 15:10 ` Matthew Garrett
2005-03-17 20:34 ` Nate Lawson [this message]
2005-03-18 0:02 ` Matthew Garrett
2005-03-18 0:08 ` Nate Lawson
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=4239E9BA.7050105@root.org \
--to=nate@root.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox