[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <474D76F9.6080504@rtr.ca>
Date: Wed, 28 Nov 2007 09:11:05 -0500
From: Mark Lord <liml@....ca>
To: Tejun Heo <htejun@...il.com>
Cc: Kjartan Maraas <kmaraas@...adpark.no>,
Tomas Carnecky <tom@...ervice.com>,
Pavel Machek <pavel@....cz>, linux-ide@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>,
Jeff Garzik <jeff@...zik.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: laptop reboots right after hibernation
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists