All of lore.kernel.org
 help / color / mirror / Atom feed
From: yakui_zhao <yakui.zhao@intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [patch]: ACPI: Add the Pansonic CF51 box to the dmi check table
Date: Thu, 19 Mar 2009 09:16:07 +0800	[thread overview]
Message-ID: <1237425368.3640.61.camel@localhost.localdomain> (raw)
In-Reply-To: <20090318134153.GA28461@srcf.ucam.org>

On Wed, 2009-03-18 at 21:41 +0800, Matthew Garrett wrote:
> On Wed, Mar 18, 2009 at 04:36:25PM +0800, yakui_zhao wrote:
> > Subject: ACPI: Add the Pansonic CF51 box to the dmi check table
> > From: Zhao Yakui <yakui.zhao@intel.com>
> > 
> > The Pansonic CF51-2L box can't be resumed if the boot option of
> > "acpi_sleep=old_ordering" is not added.
> 
> Do we have any idea what's going on here, yet?
>  Several of the machines 
> on this blacklist are modern, so it's not a workaround for ancient 
> hardware.
Now we have no idea how the behaviour is changed with the boot option.
In fact the boot option is useful for all the boxes that can't be
resumed unless it is added. 

Although the machine is modern, the ACPI 1.0 is followed on this box.
Without the boot option of "acpi_sleep=old_ordering", it can't be
resumed from S3 correctly. But after adding the boot option, the box can
be resumed. 
      
> 


  reply	other threads:[~2009-03-19  1:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18  8:36 [patch]: ACPI: Add the Pansonic CF51 box to the dmi check table yakui_zhao
2009-03-18 13:41 ` Matthew Garrett
2009-03-19  1:16   ` yakui_zhao [this message]
2009-03-19  1:21     ` Matthew Garrett
2009-03-19  2:42       ` yakui_zhao
2009-03-19  2:43         ` Matthew Garrett
2009-03-19  2:50           ` yakui_zhao
2009-03-19  2:56             ` Matthew Garrett
2009-03-28  2:21 ` Len Brown

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=1237425368.3640.61.camel@localhost.localdomain \
    --to=yakui.zhao@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@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.