On Sun, 13 May 2007 14:21:14 +0200 Lukas Hejtmanek <[EMAIL PROTECTED]> wrote:
> On Sun, May 13, 2007 at 02:11:19AM -0700, Andrew Morton wrote: > > > I've also noticed that someone pointed out that for some reason, PCI > > > config > > > space is saved twice, the first is OK, the second saves already disabled > > > devices. Unfortunately, I'm unable to find this discussion in LKM. > > > > Yeah, that sounds risky. > > > > Can you put a dump_stack() call into the PCI saving function? That way > > we'll see what the two call paths are. > > I did it, but it seems to be OK. PCI saves only once each device. So the issue > was not related to this. > > So what should I try next? > So.... we don't know 0xffffffff's are getting into dev->saved_config_space[]? Possibly we're saving the device's state when it is already partway or fully through the suspend process, dunno. What if you were to put code into pci_save_state() to detect when it reads an oxffffffff? Do a dump_stack() and print pci_dev->current_state and ->enable_cnt and various other things in there? Or maybe we've done something in the wrong order which has affected our ability to access this device. Print the order in which devices are getting suspended, let's see if we're taking down the bridge(s) in the correct order. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
