* "Device is not power manageable" @ 2006-02-21 12:27 Andrew Morton 2006-02-21 15:41 ` Randy.Dunlap 2006-02-22 2:59 ` Randy.Dunlap 0 siblings, 2 replies; 5+ messages in thread From: Andrew Morton @ 2006-02-21 12:27 UTC (permalink / raw) To: linux-acpi What does this mean? sony:/home/akpm> dmesg -s 1000000 | grep 199 Detected 1995.262 MHz processor. Sangoma WANPIPE Router v1.1 (c) 1995-2000 Sangoma Technologies Inc. ACPI (acpi_bus-0199): Device is not power manageable [20060210] e100: Copyright(c) 1999-2005 Intel Corporation ACPI (acpi_bus-0199): Device is not power manageable [20060210] ACPI (acpi_bus-0199): Device is not power manageable [20060210] ACPI (acpi_bus-0199): Device is not power manageable [20060210] ACPI (acpi_bus-0199): Device is not power manageable [20060210] ACPI (acpi_bus-0199): Device is not power manageable [20060210] ACPI (acpi_bus-0199): Device is not power manageable [20060210] ACPI (acpi_bus-0199): Device is not power manageable [20060210] ACPI (acpi_bus-0199): Device is not power manageable [20060210] ACPI (acpi_bus-0199): Device is not power manageable [20060210] ACPI (acpi_bus-0199): Device is not power manageable [20060210] ACPI (acpi_bus-0199): Device is not power manageable [20060210] <suspend-to-ram> <resume> ACPI Error (evevent-0314): No installed handler for fixed event [00000002] [20060210] And how does one identify that device? ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: "Device is not power manageable" 2006-02-21 12:27 "Device is not power manageable" Andrew Morton @ 2006-02-21 15:41 ` Randy.Dunlap 2006-02-22 2:59 ` Randy.Dunlap 1 sibling, 0 replies; 5+ messages in thread From: Randy.Dunlap @ 2006-02-21 15:41 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-acpi On Tue, 21 Feb 2006, Andrew Morton wrote: > > What does this mean? > > sony:/home/akpm> dmesg -s 1000000 | grep 199 > Detected 1995.262 MHz processor. > Sangoma WANPIPE Router v1.1 (c) 1995-2000 Sangoma Technologies Inc. > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > e100: Copyright(c) 1999-2005 Intel Corporation > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > > <suspend-to-ram> > <resume> > > ACPI Error (evevent-0314): No installed handler for fixed event [00000002] [20060210] > > > And how does one identify that device? I have posted a patch for that (2 times iirc) but it seems to have been dropped/lost (I can't even find it in the email archives). It's at home, I can repost it tonight, but it's fairly trivial: just print something like dev->bus_id (just guessing from not recent memory). I'll send it tonight. -- ~Randy ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: "Device is not power manageable" 2006-02-21 12:27 "Device is not power manageable" Andrew Morton 2006-02-21 15:41 ` Randy.Dunlap @ 2006-02-22 2:59 ` Randy.Dunlap 2006-02-22 3:08 ` Andrew Morton 1 sibling, 1 reply; 5+ messages in thread From: Randy.Dunlap @ 2006-02-22 2:59 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-acpi On Tue, 21 Feb 2006 04:27:08 -0800 Andrew Morton wrote: > > What does this mean? > > sony:/home/akpm> dmesg -s 1000000 | grep 199 > Detected 1995.262 MHz processor. > Sangoma WANPIPE Router v1.1 (c) 1995-2000 Sangoma Technologies Inc. > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > e100: Copyright(c) 1999-2005 Intel Corporation > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > ACPI (acpi_bus-0199): Device is not power manageable [20060210] > > <suspend-to-ram> > <resume> > > ACPI Error (evevent-0314): No installed handler for fixed event [00000002] [20060210] > > > And how does one identify that device? Here's the patch that I have used. -- From: Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp> Identify which device is not power-manageable to make the message more useful. Signed-off-by: Randy Dunlap <rdunlap@xenotime.net> --- drivers/acpi/bus.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) --- linux-2616-rc4.orig/drivers/acpi/bus.c +++ linux-2616-rc4/drivers/acpi/bus.c @@ -197,8 +197,9 @@ int acpi_bus_set_power(acpi_handle handl /* Make sure this is a valid target state */ if (!device->flags.power_manageable) { - ACPI_DEBUG_PRINT((ACPI_DB_WARN, - "Device is not power manageable\n")); + ACPI_DEBUG_PRINT((ACPI_DB_INFO, + "Device '%s' is not power manageable\n", + device->kobj.name)); return_VALUE(-ENODEV); } /* ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: "Device is not power manageable" 2006-02-22 2:59 ` Randy.Dunlap @ 2006-02-22 3:08 ` Andrew Morton 2006-02-22 11:44 ` Thomas Renninger 0 siblings, 1 reply; 5+ messages in thread From: Andrew Morton @ 2006-02-22 3:08 UTC (permalink / raw) To: Randy.Dunlap; +Cc: linux-acpi "Randy.Dunlap" <rdunlap@xenotime.net> wrote: > > Here's the patch that I have used. > > -- > > From: Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp> > > Identify which device is not power-manageable to make > the message more useful. > > Signed-off-by: Randy Dunlap <rdunlap@xenotime.net> > --- > drivers/acpi/bus.c | 5 +++-- > 1 files changed, 3 insertions(+), 2 deletions(-) > > --- linux-2616-rc4.orig/drivers/acpi/bus.c > +++ linux-2616-rc4/drivers/acpi/bus.c > @@ -197,8 +197,9 @@ int acpi_bus_set_power(acpi_handle handl > /* Make sure this is a valid target state */ > > if (!device->flags.power_manageable) { > - ACPI_DEBUG_PRINT((ACPI_DB_WARN, > - "Device is not power manageable\n")); > + ACPI_DEBUG_PRINT((ACPI_DB_INFO, > + "Device '%s' is not power manageable\n", > + device->kobj.name)); > return_VALUE(-ENODEV); > } > /* Thanks. I guess that won't be very popular due to using linux-specific stuff in a generic file, but I'll merge it. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: "Device is not power manageable" 2006-02-22 3:08 ` Andrew Morton @ 2006-02-22 11:44 ` Thomas Renninger 0 siblings, 0 replies; 5+ messages in thread From: Thomas Renninger @ 2006-02-22 11:44 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-acpi, rdunlap On Wednesday 22 February 2006 04:08, you wrote: > "Randy.Dunlap" <rdunlap@xenotime.net> wrote: > > > > Here's the patch that I have used. > > > > -- > > > > From: Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp> > > > > Identify which device is not power-manageable to make > > the message more useful. > > > > Signed-off-by: Randy Dunlap <rdunlap@xenotime.net> > > --- > > drivers/acpi/bus.c | 5 +++-- > > 1 files changed, 3 insertions(+), 2 deletions(-) > > > > --- linux-2616-rc4.orig/drivers/acpi/bus.c > > +++ linux-2616-rc4/drivers/acpi/bus.c > > @@ -197,8 +197,9 @@ int acpi_bus_set_power(acpi_handle handl > > /* Make sure this is a valid target state */ > > > > if (!device->flags.power_manageable) { > > - ACPI_DEBUG_PRINT((ACPI_DB_WARN, > > - "Device is not power manageable\n")); > > + ACPI_DEBUG_PRINT((ACPI_DB_INFO, > > + "Device '%s' is not power manageable\n", > > + device->kobj.name)); > > return_VALUE(-ENODEV); > > } > > /* > > Thanks. I guess that won't be very popular due to using linux-specific > stuff in a generic file, but I'll merge it. That will conflict with latest patches: ACPI_DEBUG_PRINT((ACPI_DB_WARN, ...)) have been converted to ACPI_WARNING((AE_INFO, ...)). This was done because a lot real error/warning messages were only printed with ACPI_DEBUG=y (like all ACPI_DEBUG_PRINT messages). In this case I used ACPI_INFO((AE_INFO,...)) as I knew the message pops up here and there. This one lets the message vanish totally and only shows it with ACPI_DEBUG=y and acpi_dbg_level | ACPI_DEBUG_INFO: signed-off-by: Randy Dunlap <rdunlap@xenotime.net> signed-off-by: Thomas Renninger <trenn@suse.de> bus.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletion(-) Index: linux-2.6.15/drivers/acpi/bus.c =================================================================== --- linux-2.6.15.orig/drivers/acpi/bus.c +++ linux-2.6.15/drivers/acpi/bus.c @@ -196,7 +196,9 @@ int acpi_bus_set_power(acpi_handle handl /* Make sure this is a valid target state */ if (!device->flags.power_manageable) { - ACPI_INFO((AE_INFO, "Device is not power manageable")); + ACPI_DEBUG_PRINT((ACPI_DB_INFO, + "Device %s is not power manageable", + device->kobj.name)); return_VALUE(-ENODEV); } /* ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-02-22 11:44 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2006-02-21 12:27 "Device is not power manageable" Andrew Morton 2006-02-21 15:41 ` Randy.Dunlap 2006-02-22 2:59 ` Randy.Dunlap 2006-02-22 3:08 ` Andrew Morton 2006-02-22 11:44 ` Thomas Renninger
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox