On Wednesday 01 of April 2009, Chris Wright wrote:> * Arkadiusz Miskiewicz (a.miskiewicz@xxxxxxxxx) wrote:> > and this as bad commit:> >> > 7f7ace0cda64c99599c23785f8979a072e118058 is first bad commit>> Does it make any difference if you roll fwd a couple commits to:>> 802bf931f2688ad125b73db597ce63cc842fb27a>> That fixes a possible problem with the cpumask change and interrupt> migration. Will test. >> And to be clear, one commit earlier works?>> fae3e7fba4c664b3a15f2cf15ac439e8d754afc2 Sort of, I got werid things with this commit... after initial suspend and resume it started suspending and resuming in a loop without need for any intervention on my part (so I didn't have to touch for it to start resuming). ... but if it resumed and I started using keyboard it stopped suspending. 32b838b8cfa269d688889b3213e7ee37ee901f72 behaves the same way. Any ranges or commits to test/bisect? > thanks,> -chris -- Arkadiusz Miśkiewicz PLD/Linux Teamarekm / maven.pl http://ftp.pld-linux.org/ _______________________________________________Virtualization mailing listVirtualization@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx://lists.linux-foundation.org/mailman/listinfo/virtualization
