public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Witold Szczeponik <Witold.Szczeponik@gmx.net>
To: yakui_zhao <yakui.zhao@intel.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>, Len Brown <lenb@kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	"cedric@belbone.be" <cedric@belbone.be>,
	linux-acpi@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 13243] New: regression from 2.6.29 : can't	suspend on a compaq nc6000, suspend_device(): pnp_bus_suspend+0x0/0x6b	returns -5
Date: Thu, 07 May 2009 21:05:07 +0200	[thread overview]
Message-ID: <4A0330E3.9060909@gmx.net> (raw)
In-Reply-To: <1241660638.3773.90.camel@localhost.localdomain>

yakui_zhao schrieb:

> What you said is right. After applying that commit, the C169 device will
> be switched to D3. And when the C169 device is switched to D3, the power
> resource(C16D) will be turned off.
>    But unfortunately the _OFF object of C16D is bogus. In such case the
> _STA method can't reflect the correct status of power resource and OS
> will complain that the C169 device can't be switched to D3 state.
>    > Method (_OFF, 0, NotSerialized)
>    >                         {
>                                 Store (0x00, Local0)
>    >                         }

I think this is the key to understanding what is going on here: it seems 
as if the BIOS does not allow for disabling the power resource through 
ACPI.  I suspect the Linux' ACPI core tries to set the power resource to 
D3, then evaluates _STA, and relizes that something went wrong.  But I 
am guessing here...  Even more speculation: Windows either does not care 
or makes the transition from D0 to D3 only once...

--- Witold

> 	
>    
>    If we add the boot option of "acpi.power_nocheck=1", the status check
> will be skipped in course of D0/D3 state transition.
> 



  reply	other threads:[~2009-05-07 19:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-13243-10286@http.bugzilla.kernel.org/>
     [not found] ` <20090505150138.92f3ecd6.akpm@linux-foundation.org>
     [not found]   ` <4A02000D.9030400@gmx.net>
     [not found]     ` <200905061616.36707.bjorn.helgaas@hp.com>
2009-05-07  1:43       ` [Bugme-new] [Bug 13243] New: regression from 2.6.29 : can't suspend on a compaq nc6000, suspend_device(): pnp_bus_suspend+0x0/0x6b returns -5 yakui_zhao
2009-05-07 19:05         ` Witold Szczeponik [this message]
2009-05-08  1:31           ` yakui_zhao
2009-05-08  4:39           ` [PATCH] ACPI: suspend: don't let device _PS3 failure prevent suspend Len Brown
2009-05-08 12:23             ` Henrique de Moraes Holschuh
2009-05-10 20:48               ` Witold Szczeponik
2009-05-11  2:43                 ` yakui_zhao
2009-05-11 15:21                   ` Rafael J. Wysocki
2009-05-12  0:48                     ` yakui_zhao
2009-05-12  2:01                       ` Matthew Garrett
2009-05-12  2:26                         ` yakui_zhao
2009-05-12  2:50                           ` Matthew Garrett
2009-05-12  3:06                             ` yakui_zhao
2009-05-12  4:11                               ` Matthew Garrett

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=4A0330E3.9060909@gmx.net \
    --to=witold.szczeponik@gmx.net \
    --cc=bjorn.helgaas@hp.com \
    --cc=cedric@belbone.be \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=yakui.zhao@intel.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