linux-kernel - Re: PCIe can not rescan for new PCIe device ( FPGA board )

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 11 Oct 2011 10:11:41 +0200
From:	Abdelghani Ouchabane <abdelghani@...no.com>
To:	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>
CC:	Bjorn Helgaas <bhelgaas@...gle.com>, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org
Subject: Re: PCIe can not rescan for new PCIe device ( FPGA board )


>>> 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



View attachment "dmesg-full.txt" of type "text/plain" (52600 bytes)