From: Ingo Molnar <mingo@elte.hu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: xen-devel@lists.xensource.com,
Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
linux-kernel@vger.kernel.org, Mike Travis <travis@sgi.com>,
Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org, Yinghai Lu <yhlu.kernel@gmail.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
Jeremy Fitzhardinge <jeremy@xensource.com>
Subject: Re: 2.6.29 git, resume from ram broken on thinkpad
Date: Thu, 2 Apr 2009 23:04:51 +0200 [thread overview]
Message-ID: <20090402210451.GA4076@elte.hu> (raw)
In-Reply-To: <200904022300.01707.rjw@sisk.pl>
* Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Thursday 02 April 2009, Chris Wright wrote:
> > * Rafael J. Wysocki (rjw@sisk.pl) wrote:
> > > Sorry for the misunderstanding, I thought the breakage might be introduced
> > > between 15f7176eb1cccec0a332541285ee752b935c1c85 and
> > > 0a0c5168df270a50e3518e4f12bddb31f8f5f38f, so I thought it would be a good
> > > idea to verify if 0a0c5168df270a50e3518e4f12bddb31f8f5f38f fails too.
> >
> > Ah, sure. It fails too (both test_suspend=mem and regular suspend/resume).
>
> Having looked at the commit the Arek's bisect turned up I don't
> think it's likely to have caused this problem to appear.
>
> It seems that the regression had been introduced before the PM and
> PCI updates went it, so I bet it's one of the x86 changes. Ingo,
> are there any commits obviously worth testing?
i lost context - a list/range of commits to check would be nice.
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Chris Wright <chrisw@sous-sol.org>,
Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
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 23:04:51 +0200 [thread overview]
Message-ID: <20090402210451.GA4076@elte.hu> (raw)
In-Reply-To: <200904022300.01707.rjw@sisk.pl>
* Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Thursday 02 April 2009, Chris Wright wrote:
> > * Rafael J. Wysocki (rjw@sisk.pl) wrote:
> > > Sorry for the misunderstanding, I thought the breakage might be introduced
> > > between 15f7176eb1cccec0a332541285ee752b935c1c85 and
> > > 0a0c5168df270a50e3518e4f12bddb31f8f5f38f, so I thought it would be a good
> > > idea to verify if 0a0c5168df270a50e3518e4f12bddb31f8f5f38f fails too.
> >
> > Ah, sure. It fails too (both test_suspend=mem and regular suspend/resume).
>
> Having looked at the commit the Arek's bisect turned up I don't
> think it's likely to have caused this problem to appear.
>
> It seems that the regression had been introduced before the PM and
> PCI updates went it, so I bet it's one of the x86 changes. Ingo,
> are there any commits obviously worth testing?
i lost context - a list/range of commits to check would be nice.
Ingo
next prev parent reply other threads:[~2009-04-02 21:04 UTC|newest]
Thread overview: 28+ 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-01 21:00 ` Chris Wright
2009-04-02 20:12 ` Arkadiusz Miskiewicz
2009-04-01 21:29 ` Rafael J. Wysocki
2009-04-01 21:37 ` Chris Wright
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-01 23:06 ` Chris Wright
2009-04-02 21:00 ` Rafael J. Wysocki
2009-04-02 21:04 ` Ingo Molnar [this message]
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 0:35 ` Chris Wright
2009-04-03 6:47 ` Arkadiusz Miskiewicz
2009-04-03 17:32 ` Ingo Molnar
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:39 ` Ingo Molnar
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=20090402210451.GA4076@elte.hu \
--to=mingo@elte.hu \
--cc=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=rjw@sisk.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.