From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Abdelghani Ouchabane <abdelghani@ezono.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: PCIe can not rescan for new PCIe device ( FPGA board )
Date: Wed, 12 Oct 2011 15:36:41 +0900 [thread overview]
Message-ID: <4E953579.6050807@jp.fujitsu.com> (raw)
In-Reply-To: <4E93FA3D.2030400@ezono.com>
Hello,
According to your dmesg output, pciehp driver doesn't detect any PCIe
hotplug slot. Can you send the following information?
- ls -lR /sys/bus/pci/slots
- lspci -vvvv (as root user)
Regards,
Kenji Kaneshige
(2011/10/11 17:11), Abdelghani Ouchabane wrote:
>
>>>> After I plug my board in, I executed echo 1> /sys/bus/pci/rescan
>>>
>>>
>>
>> Can you try echo 1 > /sys/bus/pci/slots/XXX/power?
>> (XXX: slot number)
> Hallo Kenji,
>
> I am still having the same problem after executing "echo 1 > /sys/bus/pci/slots/0000\:02\:00.0/power"
>
>>
>>> It seems like a pciehp bug that you have to rescan explicitly. But
>>> I'm not a pciehp expert and I haven't looked at the code.
>>
>> The pciehp automatically scans the bus on presence changed event
>> (e.g. board is pluged in) if the hot-plug controller supports
>> surprise removal. Otherwise, you need to power on slot explicitly
>> by "echo 1 > /sys/bus/pci/slots/XXX/power". So one possibility is
>> that your controller doesn't support surprise removal. We can
>> check it by looking at the pciehp's debug output. Can you send
>> whole dmesg output?
>
> I attached to you the whole dmesg log.
>
> Cheers,
> Ghani
>
>
next prev parent reply other threads:[~2011-10-12 6:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 7:16 PCIe can not rescan for new PCIe device ( FPGA board ) Abdelghani Ouchabane
2011-10-07 15:37 ` Bjorn Helgaas
2011-10-07 16:22 ` Abdelghani Ouchabane
2011-10-07 16:36 ` Bjorn Helgaas
2011-10-11 1:39 ` Kenji Kaneshige
2011-10-11 8:11 ` Abdelghani Ouchabane
2011-10-12 6:36 ` Kenji Kaneshige [this message]
2011-10-12 8:35 ` Abdelghani Ouchabane
2011-10-13 12:50 ` Kenji Kaneshige
2011-10-14 9:40 ` Abdelghani Ouchabane
2011-10-24 5:00 ` Kenji Kaneshige
2011-10-24 9:20 ` Abdelghani Ouchabane
2011-10-11 8:10 ` Abdelghani Ouchabane
2011-10-11 15:22 ` Bjorn Helgaas
[not found] ` <4E954251.5020801@ezono.com>
2011-10-12 8:03 ` Abdelghani Ouchabane
2011-10-12 15:58 ` Bjorn Helgaas
2011-10-14 9:27 ` Abdelghani Ouchabane
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=4E953579.6050807@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=abdelghani@ezono.com \
--cc=bhelgaas@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.