From: James Courtier-Dutton: > > On 13 April 2012 21:47, Mikko Vinni <mmvinni@xxxxxxxxx> wrote: >> 1 firewire_ohci 0000:0a:00.0: Refused to change power state, > currently in D3 >> 10 firewire_ohci 0000:0a:00.0: restoring config space at offset 0xf > (was 0xffffffff, writing 0x10a) >> 10 firewire_ohci 0000:0a:00.0: restoring config space at offset 0xe > (was 0xffffffff, writing 0x0) > <snip> >> 1 sdhci-pci 0000:0a:00.1: Refused to change power state, currently in > D3 >> 10 sdhci-pci 0000:0a:00.1: restoring config space at offset 0xf (was > 0xffffffff, writing 0x10a) >> 10 sdhci-pci 0000:0a:00.1: restoring config space at offset 0xe (was > 0xffffffff, writing 0x0) > <snip> > > Could the problem be more due to "Refused to change power state, > currently in D3". > the "was 0xffffffff" would be returned if their was no power to the > device. > Don't you need power, before you can write to the config space? > Those messages and the problem of the combo card reader and firewire not working after s2ram has been present for long (https://bugzilla.kernel.org/show_bug.cgi?id=35452 dmesg here: https://lkml.org/lkml/2011/5/15/55). Before 3.4-rc1 there was nothing wrong with the touchpad (and keyboard and reboot) after s2ram, and the problems are somehow separate. Rafael's patch fixes the new problem, any suggestions for the old one would be warmly appreciated. Mikko -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
