[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200904022212.06118.a.miskiewicz@gmail.com>
Date: Thu, 2 Apr 2009 22:12:05 +0200
From: Arkadiusz Miskiewicz <a.miskiewicz@...il.com>
To: Chris Wright <chrisw@...s-sol.org>
Cc: linux-kernel@...r.kernel.org, Mike Travis <travis@....com>,
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
On Wednesday 01 of April 2009, Chris Wright wrote:
> * 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.
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 Team
arekm / maven.pl http://ftp.pld-linux.org/
--
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