[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090401210054.GS18394@sequoia.sous-sol.org>
Date: Wed, 1 Apr 2009 14:00:54 -0700
From: Chris Wright <chrisw@...s-sol.org>
To: Arkadiusz Miskiewicz <a.miskiewicz@...il.com>
Cc: linux-kernel@...r.kernel.org, Mike Travis <travis@....com>,
Chris Wright <chrisw@...s-sol.org>,
Jeremy Fitzhardinge <jeremy@...source.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
virtualization@...ts.osdl.org, xen-devel@...ts.xensource.com,
Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: 2.6.29 git, resume from ram broken on thinkpad
* Arkadiusz Miskiewicz (a.miskiewicz@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists