Re: 2.6.29 git, resume from ram broken on thinkpad

From: Chris Wright
Date: Wed Apr 01 2009 - 17:02:19 EST


* 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.

And to be clear, one commit earlier works?

fae3e7fba4c664b3a15f2cf15ac439e8d754afc2

thanks,
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/