From: Ingo Molnar <mingo@elte.hu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
NetDev <netdev@vger.kernel.org>,
linux-acpi <linux-acpi@vger.kernel.org>,
tglx@tglx.de, Theodore Ts'o <tytso@mit.edu>,
linux-ide@vger.kernel.org
Subject: Re: Top kernel oopses/warnings for the week of October 7th, 2008
Date: Tue, 7 Oct 2008 22:16:17 +0200 [thread overview]
Message-ID: <20081007201617.GA20655@elte.hu> (raw)
In-Reply-To: <200810072213.16103.rjw@sisk.pl>
* Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > Rank 9: device_pm_add (warning)
> > Reported 81 times (323 total reports)
> > Drivers with suspect suspend/resume logic; a patch is queued for 2.6.28 to identify
> > which drivers are involved.
> > This warning was last seen in version 2.6.27-rc4, and first seen in 2.6.26-rc5.
> > More info: http://www.kerneloops.org/searchweek.php?search=device_pm_add
>
> This should have been fixed by:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f5a6d958b5d0a10e7e7a9dee1862fb31d08c6d26
hm, that is:
| From f5a6d958b5d0a10e7e7a9dee1862fb31d08c6d26 Mon Sep 17 00:00:00 2001
| From: Rafael J. Wysocki <rjw@sisk.pl>
| Date: Sat, 9 Aug 2008 01:05:13 +0200
| Subject: [PATCH] PM: Remove WARN_ON from device_pm_add
|
| PM: Remove WARN_ON from device_pm_add
|
| Fix message in device_pm_add() saying that the device will not be
| added to dpm_list, although in fact the device is going to be added
| to the list regardless of the ordering violation.
|
| Remove the WARN_ON(true) triggered in that situation, because it is
| hit by USB very often and spams the users' logs.
|
| This patch fixes bug #11263
+ if (dev->parent->power.status >= DPM_SUSPENDING)
+ dev_warn(dev, "parent %s should not be sleeping\n",
dev->parent->bus_id);
- WARN_ON(true);
- }
i.e. no bug was fixed in reality - we still emit a kernel log entry, but
the WARN_ON() was removed, so that it does not fall under the scope of
kerneloops.org, right?
Ingo
next prev parent reply other threads:[~2008-10-07 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 19:52 Top kernel oopses/warnings for the week of October 7th, 2008 Arjan van de Ven
2008-10-07 20:13 ` Rafael J. Wysocki
2008-10-07 20:16 ` Ingo Molnar [this message]
2008-10-07 20:37 ` Rafael J. Wysocki
2008-10-07 22:58 ` Alan Cox
2008-10-07 23:08 ` David Miller
2008-10-08 9:06 ` Rafael J. Wysocki
2008-10-08 9:21 ` Ingo Molnar
2008-10-08 12:43 ` 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=20081007201617.GA20655@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tglx@tglx.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.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;
as well as URLs for NNTP newsgroup(s).