From: Greg KH <greg@kroah.com>
To: Ryan Hope <rmh3093@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pciehp: Cannot get control of hotplug hardware
Date: Sat, 24 Mar 2007 17:35:57 -0700 [thread overview]
Message-ID: <20070325003557.GA22484@kroah.com> (raw)
In-Reply-To: <48f7fe350703100755i75d2a56al981da1fbda645ddc@mail.gmail.com>
On Sat, Mar 10, 2007 at 10:55:16AM -0500, Ryan Hope wrote:
> Ever since I started playing with suspend I started turning on PCI Hot
> Plug support.... since then I have been seeing messages like whats
> below from dmesg.... I'm not exactly sure how this actually impacts me
> if it does at all. I just thought it didn't look exactly right so I
> wanted to inquire about it. Does anyone know what is going on here?
>
> -Ryan
>
> pci_hotplug: PCI Hot Plug PCI Core version: 0.5
> acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
> decode_hpp: Could not get hotplug parameters. Use defaults
> pciehp: HPC vendor_id 8086 device_id 27d0 ss_vid 0 ss_did 0
> Evaluate _OSC Set fails. Status = 0x0005
> Evaluate _OSC Set fails. Status = 0x0005
> pciehp: Cannot get control of hotplug hardware for pci 0000:00:1c.0
Your pci express hotplug controller does not support the proper hotplug
capabilities. It's probably a bios issue as Windows doesn't support
this just yet (I think Vista now does), so those functions were usually
never tested.
You should be able to just ignore them, unless you want to use your pci
express hotplug functionality. What kind of hardware is this, a laptop
with expresscard? Or something else?
thanks,
greg k-h
prev parent reply other threads:[~2007-03-25 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 15:55 pciehp: Cannot get control of hotplug hardware Ryan Hope
2007-03-25 0:35 ` Greg KH [this message]
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=20070325003557.GA22484@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmh3093@gmail.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