mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andreas Mohr <andi@lisas.de>
Cc: linux-pci@vger.kernel.org,
	ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI / ACPI: Report _OSC control mask returned on failure to get control
Date: Thu, 14 Feb 2013 13:07:02 +0100	[thread overview]
Message-ID: <7634687.RmnPKEe4lz@vostro.rjw.lan> (raw)
In-Reply-To: <20130214011027.GA430@rhlx01.hs-esslingen.de>

On Thursday, February 14, 2013 02:10:27 AM Andreas Mohr wrote:
> Hi,
> 
> to provide an example case, on Aspire One AOA110 v0.3310, 3.8-rc7 prints:
> 
> [    0.515599] ACPI Error: [CAPB] Namespace lookup failure,
> AE_ALREADY_EXISTS (2
> 0121018/dsfield-211)
> [    0.515629] ACPI Error: Method parse/execution failed
> [\_SB_.PCI0._OSC] (Node f5449680), AE_ALREADY_EXISTS
> (20121018/psparse-537)
> [    0.515672] ACPI: Marking method _OSC as Serialized because of
> AE_ALREADY_EXISTS error
> [    0.516081] ACPI Error: [CAPB] Namespace lookup failure,
> AE_ALREADY_EXISTS (20121018/dsfield-211)
> [    0.516107] ACPI Error: Method parse/execution failed
> [\_SB_.PCI0._OSC] (Node f5449680), AE_ALREADY_EXISTS
> (20121018/psparse-537)
> [    0.516168] pci_root PNP0A08:00: ACPI _OSC support notification
> failed, disabling PCIe ASPM
> [    0.516179] pci_root PNP0A08:00: Unable to request _OSC control (_OSC
> support mask: 0x08)
> 
> HTH,

Unfortunately, it doesn't, because I've lost track of the whole thread in the
meantime.  Care to give a pointer?

Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2013-02-14 12:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 22:21 Rafael J. Wysocki
2011-05-09 19:30 ` Jesse Barnes
2013-02-14  1:10 ` Andreas Mohr
2013-02-14 12:07   ` Rafael J. Wysocki [this message]
2013-02-14 13:47     ` Andreas Mohr

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=7634687.RmnPKEe4lz@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=andi@lisas.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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®