* Jens Axboe <jens.axboe@xxxxxxxxxx>: > > acpiphp: enable_slot - physical_slot = 1 > power_on_slot > no _PS0 > no _PS0 > no _PS0 > no _PS0 > no _PS0 > no _PS0 > no _PS0 > no _PS0 > get_slot_status > reading config space dvid 0xffffffff > reading config space dvid 0xffffffff > reading config space dvid 0xffffffff > reading config space dvid 0xffffffff > reading config space dvid 0xffffffff > reading config space dvid 0xffffffff > reading config space dvid 0xffffffff > reading config space dvid 0xffffffff > acpiphp_glue: acpiphp_enable_slot: Slot status is not ACPI_STA_ALL Hm, as Kenji-san writes in an earlier email: The direct cause of the problem that your slot was not turned on is power fault. I guess acpiphp is suffering the same problem. Unfortunately, it's difficult for me to analyze the root cause of this power fault. Please ask the hardware vendor about it. I hope board replacement will fix the problem. In get_slot_status(), we're trying to read the card's vendor ID, which is a mandatory PCI config space register. The fact that we can't even read that suggests something is going wrong way earlier before we get to this point. Bjorn wondered on irc if your slots are physically working. Do you know if they work under Windows? If they do, then it would be good to find out how your bridges are being programmed, which I believe you can discover with the Device Manager. /ac -- 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
