From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Christian Ruediger Bahls <lkml@qb352.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Len Brown <len.brown@intel.com>,
linux-kernel@vger.kernel.org,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: intel_idle .. Was: __pm_runtime_resume() returns -1 Was: Regression in 2.6.36
Date: Sat, 23 Oct 2010 19:57:28 +0200 [thread overview]
Message-ID: <201010231957.28276.rjw@sisk.pl> (raw)
In-Reply-To: <20101023042607.GB449@pfau.e-technik1.uni-rostock.de>
On Saturday, October 23, 2010, Christian Ruediger Bahls wrote:
> [2010-10-23 01:58] Andrew Morton <akpm@linux-foundation.org> wrote:
> > On Fri, 22 Oct 2010 15:38:01 +0200
> > Christian Bahls <lkml@qb352.de> wrote:
> > > The regression seems to have been introduced by the merge:
> > > 92b4522f72916ff2675060e29e4b24cf26ab59ce
> > >
> >
> > I suspect your bisection went wrong :(
> ...
> > It's really hard to see how that change could break the resume
> > operation.
>
> you were right ..
>
> btw: this is not resume but system boot .. either cold or warm
> [pressing any button(even the power-button) makes the boot continue]
>
> the failure has lots of different incarnations:
> during booting it sometimes stalls:
> on initializing the sata drive
> while mounting/un-mounting the sata drive
> or other obscure occasions (syncing drives/initializing hardware)
>
> in later versions of the kernel it throws the
> "__pm_runtime_resume() returns -1"-warnings
Do you have CONFIG_PM_VERBOSE set in your .config by chance?
Rafael
prev parent reply other threads:[~2010-10-23 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 13:38 Christian Bahls
2010-10-22 23:57 ` Andrew Morton
2010-10-23 4:26 ` intel_idle .. Was: " Christian Ruediger Bahls
2010-10-23 17:48 ` Len Brown
2010-10-24 2:40 ` Christian Ruediger Bahls
2010-10-23 17:57 ` Rafael J. Wysocki [this message]
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=201010231957.28276.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@qb352.de \
/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
Powered by JetHome