On Wed, Nov 6, 2013 at 9:49 PM, wzyboy <wzyboy@xxxxxxxxxx> wrote: > 2013/11/7 Bjorn Helgaas <bhelgaas@xxxxxxxxxx>: >> Do you have any more details? Maybe open a bugzilla.kernel.org report >> and attach: >> >> - complete dmesg log >> - lspci -vvxxx output for entire system before issue occurs >> - lspci -vvxxx output for entire system after issue occurs > > > Hi, I have filed a bug on bugzilla: > https://bugzilla.kernel.org/show_bug.cgi?id=64541 > > Actually I have posted some more logs before, you could find them on > the mailing lists archive: > http://thread.gmane.org/gmane.linux.kernel.wireless.general/115259 > > Here is the output of lspci -vxxxx just now. I'll run this command > again when the bug occurs next time: Thanks. But can you please attach the output of "lspci -vvxxx" (not "-vxxxx") for the entire system before the problem occurs? All the info is in the "-xxxx" output, but it's really painful to decode it all by hand. Using "-vv" will decode the PCIe Capability structures where the ASPM configuration is. And the entire system is interesting, because ASPM requires configuration on upstream bridges as well as on the device itself. My only guess is that there's something wrong with the ASPM configuration and the device just stops responding to config accesses (and probably MMIO accesses, too, based on the errors in your dmesg log). Or maybe the device got powered off somehow. Bjorn -- 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
