Hi, This is first time, I am actually happy about a regression.... I have a notebook, aspire 5720G that fails to do two suspends to ram in row. for example I can do s2ram->s2disk->s2ram->... but can't s2ram->s2ram. Well that at least was the situation till now. Also there is no way to debug this - bios doesn't pass control back to linux on failed resume. I tried probably every guess I could come with. Now, after a commit a0d4922da2e4ccb0973095d8d29f36f6b1b5f703 which I finally bisected, I can't anymore do two suspends to ram at all, regardless of suspend to disk in between. Also bios doesn't pass control when resume fails. I actually did 3 bisects, as I had to find fixes to 2 more s2ram bugs that were fixed. the fixes are: a0e280e0f33f6c859a235fb69a875ed8f3420388 1e70c7f7a9d4a3d2cc78b40e1d7768d99cd79899 Now, why I am happy about this: It seems that a suspend cycle changes something that explodes on next resume. a s2disk cycle cleared this, but not anymore, thus the poison must be somehow connected to the a0d4922da2e4ccb0973095d8d29f36f6b1b5f703 PCI state?? I tried restoring it from saved file, (created on suspend) but this didn't help. (Only a single register, which looks like a clear or write register changed). Also this commits narrows down the search, now it is clear that this is usb related. No wonder bios pokes at usb on resume and stalls..... It could even be connected to bios handoff, maybe we don't do that on resume? (Note: this regression is present all way to latest -git) What do you think? Best regards, Maxim Levitsky -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
