Le 21/11/2013 12:17, Jingoo Han a écrit : [...] >> >>> Also I took a look at the changes between v3.11 and v3.12 in this area >>> and those changes match the issue I'm facing: >>> >>> $ git log --oneline v3.11..v3.12 -- drivers/mfd/rtsx_pcr.c >>> 09fd867 mfd: rtsx: Copyright modifications >>> eb891c6 mfd: rtsx: Configure to enter a deeper power-saving mode in S3 >>> 7140812 mfd: rtsx: Move some actions from rtsx_pci_init_hw to individual >>> extra_init_hw >>> 5947c16 mfd: rtsx: Add shutdown callback in rtsx_pci_driver >>> 773ccdf mfd: rtsx: Read vendor setting from config space > > In my opinion, rtsx_pci_resume()/rtsx_pci_suspend() in realtek PCIe card > reader driver may make the kernel panic. > > I think that the commit "mfd: rtsx: Configure to enter a deeper > power-saving mode in S3" may be the culprit.
Unfortunately no, reverting this commit on top of v3.12 doesn't help. I also reverted 7140812, 5947c16 but it didn't improve anything. The good news is that I managed to have a "light" kernel configuration which is faster to build and more important it seems that the bug is almost 100% reproductible now. So I'll try to do another git-bisect session later. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/