On Wed, Nov 6, 2013 at 10:50 AM, Emmanuel Grumbach <egrumbach@xxxxxxxxx> wrote: > Hi, > > adding PCI folks. > Here is the story: > > * Wzyboy has a Lenovo laptop with _OSC control *not* granted > * L1 Active is enabled > * kernel: 3.12.0 > * Nic is PCIe (Gen2 but not sure...) > > At some random point, the driver loses access to the NIC: all readl > operation return 0xff. > Even lspci returns 0xff: > > 03:00.0 Network controller: Intel Corporation Wireless 7260 (rev ff) > 00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > > here is the output of lspci *before* the issue hits: > > 03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b) > 00: 86 80 b2 08 06 04 10 00 6b 00 80 02 10 00 00 00 > 10: 04 00 40 f0 00 00 00 00 00 00 00 00 00 00 00 00 > 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 62 c2 > 30: 00 00 00 00 c8 00 00 00 00 00 00 00 09 01 00 00 > > have you any idea of what we can do to understand what it going wrong here? 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 Bjorn > On 11/06/2013 09:12 AM, wzyboy wrote: >> 2013/11/6 Grumbach, Emmanuel <emmanuel.grumbach@xxxxxxxxx>: >>> Wait - you mean that after the bug occurred before you rebooted, lspci -xxx show all 00? >>> I can see 0xff here. >>> Anyway - this is very bad... checking with HW guys... >> >> >> Sorry, that's my typo. They are all 0xff... (I don't know what do they >> mean but it look bad...) >> >> Thanks for your effort! I'm waiting for good news from you and HW guys. :-) >> -- 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
