On 04/20/2013 11:26 AM, Frank Rizzo wrote: > On Fri, 19 Apr 2013 19:59:58 -0700, Yijing Wang <wangyijing@xxxxxxxxxx> wrote: > >> On 2013/4/20 10:22, Frank Rizzo wrote: >>> (with device powered on AFTER boot) >>> >>> root@frank-System-Product-Name:~# echo 1 > /sys/bus/pci/rescan >> >> Hi Frank, >> When you do rescan here, any new message info will print in dmesg? >> Compare the two lspci info, it seems like your external device is >> 02.0-[02]----00.0 Device 1a39:0004, which include a pci bridge and a pci endpoint device. >> But let me confused is that after you rescan (with device powered on AFTER boot), >> there is no any new device found, normally, at least we should found the bridge device. >> Maybe the link between host bridge and your external device got some problems? I am not sure. > > > Yijing, when powered on, the device works fine. I can talk to all the registers, and do everything that I need to do. This "late power-on issue" is the only thing holding me back. > > This is what I get in dmesg. (Cleared first) > > root@frank-System-Product-Name:~# dmesg -c > (SNIP!) > root@frank-System-Product-Name:~# echo 1 > /sys/bus/pci/rescan > root@frank-System-Product-Name:~# dmesg > [ 1180.917841] fglrx_pci 0000:01:05.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment > root@frank-System-Product-Name:~# > -- > To unsubscribe from this list: send the line "unsubscribe linux-pci" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html Hi Frank, Message from "sudo lspci -vvv" gives more information, including PCIe capabilities, so please help to send out "sudo lspci -vvv" instead of "lspci -v". Thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
