Messages in this thread | | | Date | Wed, 1 Apr 2009 14:00:54 -0700 | From | Chris Wright <> | Subject | Re: 2.6.29 git, resume from ram broken on thinkpad |
| |
* Arkadiusz Miskiewicz (a.miskiewicz@gmail.com) 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.
And to be clear, one commit earlier works?
fae3e7fba4c664b3a15f2cf15ac439e8d754afc2
thanks, -chris
| |