From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Kjartan Maraas <kmaraas@broadpark.no>,
Tomas Carnecky <tom@dbservice.com>, Pavel Machek <pavel@ucw.cz>,
linux-ide@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: laptop reboots right after hibernation
Date: Wed, 28 Nov 2007 09:11:05 -0500 [thread overview]
Message-ID: <474D76F9.6080504@rtr.ca> (raw)
In-Reply-To: <474D6EA7.2000506@gmail.com>
Tejun Heo wrote:
>
> Your BIOS is probably trying to issue DCO freeze lock to all drives. I
> don't have the faintest idea why it does but it does. I think there are
> several choices here.
>
> 1. Ignore device errors for _GTF commands. Report the failure with
> KERN_DEBUG priority and just keep processing. ISTR there was a patch to
> do this. Anyone knows what happened to it.
..
Since we now *know* that this is how it has to be done
(as otherwise the BIOS would never even attempt DCO here
because most drives don't support it yet),
then ignoring the return value seems to be a useful strategy.
> 2. Filter out certain commands from ACPI. I definitely don't like BIOS
> locking up random features via _GTF commands. It makes debugging difficult.
..
Mmmm.. I agree there, too! I'm not big on filtering out commands
that *we* don't happen to like, but for this specific opcode, yes.
> 3. Look at opcode on failure and ignore error for certain operations.
..
Number 1. would take care of this.
Cheers
next prev parent reply other threads:[~2007-11-28 14:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <473730F6.2010900@dbservice.com>
[not found] ` <20071118105214.GB7299@ucw.cz>
[not found] ` <4740692E.7010801@dbservice.com>
2007-11-18 20:16 ` laptop reboots right after hibernation Tomas Carnecky
2007-11-20 9:32 ` Kjartan Maraas
2007-11-28 1:09 ` Tejun Heo
2007-11-28 12:35 ` Kjartan Maraas
2007-11-28 13:35 ` Tejun Heo
2007-11-28 13:47 ` Jeff Garzik
2007-11-28 14:11 ` Mark Lord [this message]
2007-11-30 10:39 ` Tejun Heo
2007-11-30 21:37 ` Kjartan Maraas
2007-12-05 7:46 ` Tejun Heo
2007-12-05 8:27 ` Kjartan Maraas
2007-12-05 17:09 ` Kjartan Maraas
2007-12-06 2:38 ` Tejun Heo
2007-12-06 16:47 ` Kjartan Maraas
2007-12-09 6:46 ` Tejun Heo
2007-12-09 21:43 ` Kjartan Maraas
2007-12-10 1:03 ` Tejun Heo
2007-12-10 14:05 ` Kjartan Maraas
2007-12-10 14:10 ` Tejun Heo
2007-11-28 8:06 ` Tejun Heo
2007-11-28 10:45 ` Tomas Carnecky
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=474D76F9.6080504@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=kmaraas@broadpark.no \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tom@dbservice.com \
/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).