linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rajesh Shah <rajesh.shah@intel.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: pci-e hotplug on Intel SE7520HPAF2 board
Date: Tue, 08 Mar 2005 19:58:53 +0000	[thread overview]
Message-ID: <20050308115853.A12953@unix-os.sc.intel.com> (raw)
In-Reply-To: <1110243507.30761.8.camel@duffman>

On Tue, Mar 08, 2005 at 10:02:51AM -0800, Tom Duffy wrote:
> 
> > > [root@intlhotp-1 ~]# echo 1 > /sys/bus/pci/slots/3/power
> > > acpiphp_glue: No new device found
> > > [root@intlhotp-1 ~]# echo 1 > /sys/bus/pci/slots/4/power
> > > acpiphp_glue: No new device found
> > 
> > That's not good.  But you are using the acpi driver, not the pciexpress
> > driver, is that what you mean to do?
> 
I didn't think this board (firmware) supported ACPI based hotplug
but you did get a couple of slots registered messages. You could
load the acpiphp driver with debug enabled so it prints more info
about where it found the acpi hotpluggable slots. Perhaps the
hotpluggable slots it found are not where you're plugging the
card in.

Looking at the system specs, it looks like some slots are pci-e
slots and should be hotpluggable using pciehp, while other slots
are pci(x) and hotpluggable using shpchp. Could you also try to
load and use shpchp if you were using one of those slots?

> I was hoping that I could use the ACPI driver since the pci express
> native one will not work on the nvidia CK804 which is the real reason I
> am trying out pci express hotplug.
> 
Hmm... the hotplug drivers shouldn't care which card you are
hotplugging. They should simply pci-initialize the card and
cause the hotplug event to get the corresponding driver to load.
Do you know why the nvidia cards would only work with ACPI hotplug?

> 
> pciehp: acpi_pciehprm:\_SB_.PCI0.EPC0 OSHP fails=0x5
> pciehp: acpi_pciehprm:\_SB_.PCI0.EPC0 OSHP fails=0x5
> 
> Not sure what those messages are telling me...
> 
It's telling you the firmware hasn't defined the ACPI OSHP methods
for those hotpluggable slots. OSHP is used to tell firmware that
the OS supports native pcie/shpc hotplug, so it shouldn't try to
emulate acpi hotplug on the slot. Lack of this method is harmless
if the firmware never supported acpi hotplug on this slot anyway.

I'm CC'ing Dely who may know more about what's going on.

Rajesh


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2005-03-08 19:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08  0:58 pci-e hotplug on Intel SE7520HPAF2 board Tom Duffy
2005-03-08  6:55 ` Greg KH
2005-03-08 17:09 ` Tom Duffy
2005-03-08 17:33 ` Greg KH
2005-03-08 18:02 ` Tom Duffy
2005-03-08 19:58 ` Rajesh Shah [this message]
2005-03-08 20:44 ` Sy, Dely L
2005-03-08 21:45 ` Tom Duffy

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=20050308115853.A12953@unix-os.sc.intel.com \
    --to=rajesh.shah@intel.com \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).