[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090402210451.GA4076@elte.hu>
Date: Thu, 2 Apr 2009 23:04:51 +0200
From: Ingo Molnar <mingo@...e.hu>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Chris Wright <chrisw@...s-sol.org>,
Arkadiusz Miskiewicz <a.miskiewicz@...il.com>,
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
* Rafael J. Wysocki <rjw@...k.pl> wrote:
> On Thursday 02 April 2009, Chris Wright wrote:
> > * Rafael J. Wysocki (rjw@...k.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
--
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