From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Peter Jones <pjones@redhat.com>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Mario Limonciello <Mario_Limonciello@dell.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.
Date: Thu, 16 Jun 2016 16:56:57 +0200 [thread overview]
Message-ID: <CAJZ5v0ifNFP5jzPf+zMC3rJ1HKzBmCz1AdhsAsmj75EpndoPTQ@mail.gmail.com> (raw)
In-Reply-To: <CAJZ5v0g5_M=iNLE_P4eOcwJet=jPm_EifAMdDtvG+TR=1AnU2Q@mail.gmail.com>
On Thu, Jun 16, 2016 at 2:12 AM, Rafael J. Wysocki <rafael@kernel.org> wrote:
> On Thu, Jun 16, 2016 at 12:15 AM, Peter Jones <pjones@redhat.com> wrote:
>> Right now when booting, on many laptops the firmware manages the PCIe
>> bus. As a result, when we call the _OSC ACPI method, it returns an
>> error code. Unfortunately the errors are not very articulate.
>
> What exactly do you mean here?
>
>> As a result, we show:
>>
>> ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
>> acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
>> \_SB_.PCI0 (33DB4D5B-1FF7-401C-9657-7441C03DD766): _OSC invalid UUID
>> _OSC request data: 1 1f 0
>
> So _OSC told us that the UUID was invalid, didn't it?
BTW, the above messages are KERN_DEBUG, so at least in theory they
shouldn't be visible in production runs.
Maybe the bug to fix is that they show up when they aren't supposed to?
next prev parent reply other threads:[~2016-06-16 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 22:15 [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug Peter Jones
2016-06-16 0:12 ` Rafael J. Wysocki
2016-06-16 14:56 ` Rafael J. Wysocki [this message]
2016-06-21 15:18 ` Peter Jones
2016-06-21 18:01 ` Mario_Limonciello
2016-06-21 18:07 ` Andy Lutomirski
2016-06-21 22:54 ` Rafael J. Wysocki
2016-06-21 22:51 ` Rafael J. Wysocki
2016-06-22 19:43 ` Mario_Limonciello
2016-06-22 20:53 ` Andy Lutomirski
2016-06-22 22:47 ` Rafael J. Wysocki
2016-06-23 15:38 ` Mario_Limonciello
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=CAJZ5v0ifNFP5jzPf+zMC3rJ1HKzBmCz1AdhsAsmj75EpndoPTQ@mail.gmail.com \
--to=rafael@kernel.org \
--cc=Mario_Limonciello@dell.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=pjones@redhat.com \
--cc=rjw@rjwysocki.net \
/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).