From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm@lists.linux-foundation.org, <linux-ide@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [linux-pm] 2.6.37-rc5, pata_atiixp, DVD-ROM: kernel log flooded with "rpm_resume flags 0x4", "rpm_resume returns 1"
Date: Sat, 18 Dec 2010 20:08:37 +0100 [thread overview]
Message-ID: <20101218200837.03a23f62@stein> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1012181259080.3334-100000@saphir.localdomain>
On Dec 18 Alan Stern wrote:
> On Fri, 17 Dec 2010, Stefan Richter wrote:
> > On Dec 11 Rafael J. Wysocki wrote:
> > > I guess you have either CONFIG_PM_VERBOSE set or CONFIG_PM_DEBUG unset.
> > >
> > > Which is the case?
> >
> > I have both options off on 2.6.36 and older kernels. I have both
> > options on on 2.6.37-rc5/-rc6 (because I wanted to check something
> > unrelated on 2.6.37).
>
> These messages are produced by dev_dbg() calls. The debug output is
> enabled by either CONFIG_PM_VERBOSE or CONFIG_DEBUG_DRIVER. Since you say
> CONFIG_PM_VERBOSE is off, the other must be on -- unless maybe you have
> CONFIG_DYNAMIC_DEBUG enabled.
No, CONFIG_PM_VERBOSE is of course _on_ in the kernel that spams the
log. It is off in the older kernel that does not spam the log.
--
Stefan Richter
-=====-==-=- ==-- =--=-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2010-12-18 19:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101211173234.77617d3a@stein>
2010-12-11 19:29 ` [linux-pm] 2.6.37-rc5, pata_atiixp, DVD-ROM: kernel log flooded with "rpm_resume flags 0x4", "rpm_resume returns 1" Rafael J. Wysocki
2010-12-11 19:38 ` Alan Stern
2010-12-17 20:15 ` Stefan Richter
2010-12-17 20:30 ` Stefan Richter
2010-12-17 20:32 ` Stefan Richter
2010-12-18 18:14 ` Alan Stern
2010-12-18 19:12 ` Stefan Richter
2010-12-18 18:11 ` Alan Stern
2010-12-18 19:08 ` Stefan Richter [this message]
2010-12-18 22:41 ` Rafael J. Wysocki
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=20101218200837.03a23f62@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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