From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Vinson Lee <vlee@twopensource.com>
Cc: William Dauchy <wdauchy@gmail.com>,
Zdenek Kabelac <zkabelac@redhat.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: WARNING: CPU: 0 PID: 2623 at drivers/pnp/pnpacpi/core.c:96 pnpacpi_set_resource
Date: Tue, 29 Jul 2014 23:10:19 +0200 [thread overview]
Message-ID: <2026468.U7VDB8Dm9m@vostro.rjw.lan> (raw)
In-Reply-To: <CAHTgTXV_kJ=bUOEQjbxM8+tZ+Df--xrZxH5bwkGFqffLd5h9LA@mail.gmail.com>
On Tuesday, July 29, 2014 11:13:55 AM Vinson Lee wrote:
> On Tue, Jul 29, 2014 at 2:53 AM, William Dauchy <wdauchy@gmail.com> wrote:
> > Hi Vinson,
> >
> > On Mon, Jul 28, 2014 at 9:11 PM, Vinson Lee <vlee@twopensource.com> wrote:
> >> The warning first happens with 3.14-rc1. The warning does not occur with 3.13.0.
> >
> > Hitting the same issue here with a similar trace on 3.14.x. Did you
> > start bisecting?
> >
> > Regards,
> > --
> > William
>
>
> I bisected the warning that I'm seeing to this commit.
>
> commit 202317a573b20d77a9abb7c16a3fd5b40cef3d9d
> Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Date: Fri Nov 22 21:54:37 2013 +0100
>
> ACPI / scan: Add acpi_device objects for all device nodes in the namespace
Interesting.
Does the appended patch make any difference?
Rafael
---
drivers/pnp/pnpacpi/core.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Index: linux-pm/drivers/pnp/pnpacpi/core.c
===================================================================
--- linux-pm.orig/drivers/pnp/pnpacpi/core.c
+++ linux-pm/drivers/pnp/pnpacpi/core.c
@@ -319,8 +319,7 @@ static int __init acpi_pnp_match(struct
struct pnp_dev *pnp = _pnp;
/* true means it matched */
- return !acpi->physical_node_count
- && compare_pnp_id(pnp->id, acpi_device_hid(acpi));
+ return pnp->data == acpi;
}
static struct acpi_device * __init acpi_pnp_find_companion(struct device *dev)
next prev parent reply other threads:[~2014-07-29 20:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 8:41 Zdenek Kabelac
2014-05-29 11:14 ` Rafael J. Wysocki
2014-07-25 23:15 ` Vinson Lee
2014-07-27 9:01 ` Vinson Lee
2014-07-28 19:11 ` Vinson Lee
2014-07-29 9:53 ` William Dauchy
2014-07-29 18:13 ` Vinson Lee
2014-07-29 21:10 ` Rafael J. Wysocki [this message]
2014-07-29 21:52 ` Vinson Lee
2014-07-29 22:39 ` Rafael J. Wysocki
2014-07-30 11:49 ` William Dauchy
2014-07-30 12:50 ` 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=2026468.U7VDB8Dm9m@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=vlee@twopensource.com \
--cc=wdauchy@gmail.com \
--cc=zkabelac@redhat.com \
/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
all inboxes | Powered by JetHome®