linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy_d_dunlap@linux.intel.com>
To: Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH/RFC 0/7] SATA ACPI suspend/resume support
Date: Thu, 22 Dec 2005 10:31:53 -0800	[thread overview]
Message-ID: <20051222103153.15a988f6.randy_d_dunlap@linux.intel.com> (raw)
In-Reply-To: <87zmmtthtv.fsf@marrow.phys.tohoku.ac.jp>

On 22 Dec 2005 21:52:12 +0900
Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp> wrote:

> Randy Dunlap <randy_d_dunlap@linux.intel.com> writes:
> 
> > > The screen is cleared and the following is displayed:
> > > 
> > > Stopping tasks: ==========|
> > > acpi_bus-0201 [57] bus_set_power         : Device is not power manageable
> > > PM: Entering mem sleep
> > 
> > I've asked for some clarification on this message, including
> > how serious (problematic) it is to the suspend process,
> > but have received no answer yet (on the acpi-devel mailing
> > list).  It appears to mostly be a debugging information message.
> 
> I hope the following information is useful.
> I changed part of drivers/acpi/bus.c
> 
>         if (!device->flags.power_manageable) {
>                 ACPI_DEBUG_PRINT((ACPI_DB_WARN,
>                                   "Device is not power manageable\n"));
>                 return_VALUE(-ENODEV);
>         }
> 
> to
> 
>         if (!device->flags.power_manageable) {
>                 ACPI_DEBUG_PRINT((ACPI_DB_WARN,
>                                   "Device %s is not power manageable\n",
>                                   device->kobj.name));
>                 return_VALUE(-ENODEV);
>         }
>         
> And the kobj.name included in the warning was:
> 
> acpi_bus-0202 [57] bus_set_power         : Device IDE0 is not power manageable
> 
> Looks like this is related to a hard drive controller?

Yes, but from looking at the code, it still doesn't look
like a critical error to me, just a warning.
Nevertheless, we should get your patch merged IMO.

Thanks,
---
~Randy

  reply	other threads:[~2005-12-22 18:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19 15:18 [PATCH/RFC 0/7] SATA ACPI suspend/resume support Jae-hyeon Park
2005-12-20 18:55 ` Randy Dunlap
2005-12-22 12:52   ` Jae-hyeon Park
2005-12-22 18:31     ` Randy Dunlap [this message]
2005-12-26  5:10   ` Jae-hyeon Park
  -- strict thread matches above, loose matches on Subject: below --
2005-12-14  0:10 Randy Dunlap
2005-12-14 22:29 ` Jeff Garzik
2005-12-17 22:06   ` Randy.Dunlap
2005-12-15  3:04 ` Mark Lord
2005-12-15  3:31   ` Randy.Dunlap

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=20051222103153.15a988f6.randy_d_dunlap@linux.intel.com \
    --to=randy_d_dunlap@linux.intel.com \
    --cc=jhpark@tuhep.phys.tohoku.ac.jp \
    --cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).