public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Chiang <achiang@hp.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Mark Lord <lkml@rtr.ca>, Greg KH <greg@kroah.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org
Subject: Re: pci-express hotplug
Date: Mon, 12 Oct 2009 15:48:54 -0600	[thread overview]
Message-ID: <20091012214854.GA14102@ldl.fc.hp.com> (raw)
In-Reply-To: <20091012150603.GK9228@kernel.dk>

> >>> On Mon, Oct 12, 2009 at 02:06:20PM +0200, Jens Axboe wrote:
> >>>> I'm trying to get pci-express hotplug working in a box here. I don't
> >>>> really care about the hotplug aspect, I just want the darn pci-e slots
> >>>> that are designated hotplug slots to actually WORK. When I load pciehp,
> >>>> I get:
> >>>>
> >>>> Firmware did not grant requested _OSC control
> >>>> Firmware did not grant requested _OSC control
> >>>> Firmware did not grant requested _OSC control
> >>>> Firmware did not grant requested _OSC control

This isn't just a benign message. It means the OS asked to take
over control of the slots and firmware really did say, "nope,
sorry".

Which means that this:

> On Mon, Oct 12 2009, Mark Lord wrote:
> > Tried this yet:
> >
> >   options pciehp pciehp_force=1

Is generally a bad idea.

Don't do it unless you really know your platform well.

> >> On Mon, Oct 12 2009, Greg KH wrote:
> >>> Can you try the acpiphp driver instead?  That's usually the
> >>> driver you want to use for "modern" systems (i.e. anything
> >>> made in the past 5 years.)
> >>
> >> I should have mentioned that I tried that too. It doesn't
> >> complain, but I don't see my cards anywhere afterwards. I'm
> >> a hotplug newbie, do I need to do anything else?

Can you modprobe acpiphp with debug=1? And send the output?

Thanks.

/ac


  reply	other threads:[~2009-10-12 21:49 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 12:06 pci-express hotplug Jens Axboe
2009-10-12 14:52 ` Greg KH
2009-10-12 14:57   ` Jens Axboe
2009-10-12 15:00     ` Mark Lord
2009-10-12 15:06       ` Jens Axboe
2009-10-12 21:48         ` Alex Chiang [this message]
2009-10-13  8:29           ` Jens Axboe
2009-10-13 17:27             ` Alex Chiang
2009-10-14  8:13               ` Jens Axboe
2009-10-20 19:07                 ` Alex Chiang
2009-10-26 10:54                   ` Jens Axboe
2009-10-27  2:48                     ` Alex Chiang
2009-10-27  8:26                       ` Jens Axboe
2009-10-27  8:34                         ` Jens Axboe
2009-10-27 15:15                           ` Alex Chiang
2009-10-28  9:18                             ` Jens Axboe
2009-10-28 19:55                               ` Alex Chiang
2009-10-29 18:55                                 ` Jens Axboe
2009-10-28 20:46                         ` Alex Chiang
2009-10-28 21:39                         ` Alex Chiang
2009-10-29  8:57                           ` Jens Axboe
2009-10-27  6:31                     ` Kenji Kaneshige
2009-10-27  8:27                       ` Jens Axboe
2009-10-27  8:36                         ` Jens Axboe
2009-10-27  8:46                         ` Kenji Kaneshige
2009-10-28  6:15                         ` Kenji Kaneshige
2009-10-28  9:23                           ` Jens Axboe
2009-10-29  7:44                             ` Kenji Kaneshige
2009-10-29  8:58                               ` Jens Axboe
2009-10-29  9:23                                 ` Kenji Kaneshige
2009-10-29  9:24                                   ` Jens Axboe
2009-11-02  5:27                                     ` Kenji Kaneshige
2009-10-13  3:19 ` Kenji Kaneshige
2009-10-13  8:31   ` Jens Axboe
2009-10-13 10:48     ` Kenji Kaneshige
2009-10-13 11:25       ` Jens Axboe
2009-10-14  5:26         ` Kenji Kaneshige
2009-10-14  8:47           ` Jens Axboe
2009-10-15  5:41             ` Kenji Kaneshige
2009-10-15  9:42               ` Jens Axboe

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=20091012214854.GA14102@ldl.fc.hp.com \
    --to=achiang@hp.com \
    --cc=greg@kroah.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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