From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: linux-kernel@vger.kernel.org, Mike Travis <travis@sgi.com>,
Jeremy Fitzhardinge <jeremy@xensource.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
virtualization@lists.osdl.org, xen-devel@lists.xensource.com,
Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: 2.6.29 git, resume from ram broken on thinkpad
Date: Thu, 2 Apr 2009 22:12:05 +0200 [thread overview]
Message-ID: <200904022212.06118.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <20090401210054.GS18394@sequoia.sous-sol.org>
On Wednesday 01 of April 2009, Chris Wright wrote:
> * 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.
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/
next prev parent reply other threads:[~2009-04-02 20:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 9:55 2.6.29 git, resume from ram broken on thinkpad Arkadiusz Miskiewicz
2009-04-01 21:00 ` Chris Wright
2009-04-02 20:12 ` Arkadiusz Miskiewicz [this message]
2009-04-01 21:29 ` Rafael J. Wysocki
2009-04-01 21:37 ` Chris Wright
2009-04-01 21:49 ` Rafael J. Wysocki
2009-04-01 22:14 ` Chris Wright
2009-04-01 22:23 ` Rafael J. Wysocki
2009-04-01 23:06 ` Chris Wright
2009-04-02 21:00 ` Rafael J. Wysocki
2009-04-02 21:04 ` Ingo Molnar
2009-04-02 21:28 ` Rafael J. Wysocki
2009-04-03 0:22 ` Arkadiusz Miskiewicz
2009-04-03 0:35 ` Chris Wright
2009-04-03 6:47 ` Arkadiusz Miskiewicz
2009-04-03 17:32 ` Ingo Molnar
2009-04-03 17:36 ` Chris Wright
2009-04-03 17:39 ` Ingo Molnar
2009-04-03 17:45 ` Chris Wright
2009-04-07 8:54 ` Arkadiusz Miskiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200904022212.06118.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=chrisw@sous-sol.org \
--cc=jeremy@xensource.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=travis@sgi.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=yhlu.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).