[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200910010001.23869.rjw@sisk.pl>
Date: Thu, 1 Oct 2009 00:01:23 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Kelly Bowa <kbpm@...edu.org>
Cc: Alan Stern <stern@...land.harvard.edu>,
Magnus Damm <magnus.damm@...il.com>, Greg KH <gregkh@...e.de>,
Pavel Machek <pavel@....cz>, Len Brown <lenb@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Matthew Garrett <mjg59@...f.ucam.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Paul Mundt <lethal@...ux-sh.org>
Subject: Re: __pm_runtime_idle() returns -11!
On Wednesday 30 September 2009, Kelly Bowa wrote:
> Hi Rafael,
>
> I get the following error messages in dmesg:
>
> [ 0.488758] ACPI: Enumerating devices from [\]
> [ 0.489673] PM: Adding info for acpi:LNXSYSTM:00
> [ 0.489856] acpi LNXSYSTM:00: __pm_runtime_idle()!
> [ 0.489862] acpi LNXSYSTM:00: __pm_runtime_idle() returns -11!
> [ 0.490952] PM: Adding info for acpi:LNXCPU:00
> [ 0.491154] acpi LNXCPU:00: __pm_runtime_idle()!
> [ 0.491161] acpi LNXCPU:00: __pm_runtime_idle() returns -11!
> ....
>
> full dmesg: www.tuxedu.org/kbpm/dmesg2.txt
>
> __pm_runtime_idle() returns -11 which could be that it is waiting for other
> suspend running in parallel or that pm_runtime_cancel() fails to suspend the
> given device ?.. this causes a noticeable delay in boot time. I get this on
> 2.6.31-mm1 and ill soon test against 2.6.32-rc1..
This is a result of a debug message which is not supposed to be enabled on
production systems. What debug options are enabled in your kernel config?
Rafael
--
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