> looks like the your adapter need more time to settle down? > Can you check if you can enable slow boot mode in BIOS setup? yes, probably. I'll try to repeat steps with disabled fast boot. > looks like that server is down. should be up now On Tue, Jan 14, 2014 at 11:31 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote: > On Sat, Jan 11, 2014 at 12:38 AM, `VL <vl.homutov@xxxxxxxxx> wrote: >>> there is no 07:00.0 in the print out. >> >> Well, so it looks like procedure, doing earlydump somehow misses this >> device. >> I have collected one more log (without pci=realloc but with debug) so I'm >> pretty sure >> that device is there (it appears later in dmesg output) but still not shown >> in earlydump - >> it shows 00:06, then 00:09. > > looks like the your adapter need more time to settle down? > > Can you check if you can enable slow boot mode in BIOS setup? > >> >> http://inspert.ru/pci/dmesg-earlydump.txt > > looks like that server is down. > >> >> First messages about 00:07 are: >> >> [ 0.402838] pci 0000:07:00.0: [1412:1712] type 00 class 0x040100 >> [ 0.403042] pci 0000:07:00.0: reg 0x10: [io 0x0000-0x001f] >> [ 0.403230] pci 0000:07:00.0: reg 0x14: [io 0x0000-0x000f] >> [ 0.403418] pci 0000:07:00.0: reg 0x18: [io 0x0000-0x000f] >> [ 0.403607] pci 0000:07:00.0: reg 0x1c: [io 0x0000-0x003f] >> [ 0.403888] pci 0000:07:00.0: supports D2, >> -- 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
