From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Roland Dreier <roland@purestorage.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
George McCollister <george.mccollister@gmail.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: Regression in 3.10.80 vs. 3.10.79
Date: Thu, 11 Jun 2015 01:23:32 +0200 [thread overview]
Message-ID: <25627634.TOSvDFmF1a@vostro.rjw.lan> (raw)
In-Reply-To: <CAL1RGDWBd9Y_KLoT+DZX0Js+y9C8c4mTj9b3n+-8C=_vE0=pPw@mail.gmail.com>
On Tuesday, June 09, 2015 04:51:35 PM Roland Dreier wrote:
> On Tue, Jun 9, 2015 at 4:43 PM, Roland Dreier <roland@purestorage.com> wrote:
> > I understand that the change here fixed another regression, but I'm
> > wondering if there's a way to make everyone happy here? I can provide
> > debugging info from my system as required...
>
> Maybe sent my mail too quickly, as I have some thoughts after looking
> at the code.
>
> From the link order, drivers/acpi init wll be called before
> drivers/pnp init, right? In my case, the acpi resources ("ACPI
> PM1a_EVT_BLK") etc are under a pnp bus. But if acpi requests the
> resources first, then pnp can't request the enclosing range.
>
> Is the right fix to make sure the pnp init happens before acpi
> requests resources?
I need to have a deeper look at things.
Can you please file a bug at bugzilla.kernel.org to track this and attach
the output of acpidump from the affected system in there?
Rafael
next parent reply other threads:[~2015-06-10 22:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL1RGDV6hr3_Oa6O-kPzx9EemtOWWtYq+-RkCzN7axNPLz5MJw@mail.gmail.com>
[not found] ` <CAL1RGDWBd9Y_KLoT+DZX0Js+y9C8c4mTj9b3n+-8C=_vE0=pPw@mail.gmail.com>
2015-06-10 23:23 ` Rafael J. Wysocki [this message]
2015-06-11 19:01 ` Regression in 3.10.80 vs. 3.10.79 Roland Dreier
2015-06-11 20:50 ` Rafael J. Wysocki
2015-06-12 15:01 ` Roland Dreier
2015-06-13 2:52 ` Rafael J. Wysocki
2015-06-13 16:56 ` Roland Dreier
2015-06-15 14:56 ` Roland Dreier
2015-06-15 23:00 ` Rafael J. Wysocki
2015-06-17 12:42 ` Rafael J. Wysocki
2015-06-17 21:53 ` 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=25627634.TOSvDFmF1a@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=bhelgaas@google.com \
--cc=george.mccollister@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=roland@purestorage.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