From: Pavel Machek <pavel@ucw.cz>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
kernel list <linux-kernel@vger.kernel.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: 3.15-rc: regression in suspend
Date: Thu, 26 Jun 2014 00:35:22 +0200 [thread overview]
Message-ID: <20140625223522.GA5923@xo-6d-61-c0.localdomain> (raw)
In-Reply-To: <alpine.LNX.2.00.1406091302560.20782@pobox.suse.cz>
On Mon 2014-06-09 13:03:31, Jiri Kosina wrote:
> On Mon, 9 Jun 2014, Pavel Machek wrote:
>
> > > > Strange. It seems 3.15 with the patch reverted only boots in 30% or so
> > > > cases... And I've seen resume failure, too, so maybe I was just lucky
> > > > that it worked for a while.
> > >
> > > git bisect really likes 25f397a429dfa43f22c278d0119a60 - you're about
> > > the 5th report or so that claims this is the culprit but it's
> > > something else. The above code is definitely not used in i915 so bogus
> > > bisect result.
> >
> > Note I did not do the bisect, I only attempted revert and test.
> >
> > And did three boots of successful s2ram.. only to find out that it
> > does not really fix s2ram, I was just lucky :-(.
> >
> > Unfortunately, this means my s2ram problem will be tricky/impossible
> > to bisect :-(.
>
> Welcome to the situation I have been in for past several months.
Ok, so I have set up machines for ktest / autobisect, and found out that 3.16-rc1 no
longer has that problem. Oh well, bisect would not be fun, anyway...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-06-25 22:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 16:09 3.15-rc: regression in suspend Pavel Machek
2014-05-13 16:19 ` Bjørn Mork
2014-05-13 16:50 ` Pavel Machek
2014-05-13 16:37 ` Pavel Machek
2014-05-13 21:41 ` Pavel Machek
2014-05-14 12:39 ` Jiri Kosina
2014-05-14 15:57 ` Pavel Machek
2014-05-14 16:10 ` Jiri Kosina
2014-05-14 20:31 ` Pavel Machek
2014-05-14 18:20 ` Pavel Machek
2014-05-15 15:29 ` Jiri Kosina
2014-05-15 15:31 ` Daniel Vetter
2014-06-07 12:05 ` Pavel Machek
2014-06-07 12:06 ` Pavel Machek
2014-06-07 23:11 ` Pavel Machek
2014-06-09 9:25 ` Daniel Vetter
2014-06-09 10:23 ` Pavel Machek
2014-06-09 11:03 ` Jiri Kosina
2014-06-10 11:50 ` Bisecting the heisenbugs (was Re: 3.15-rc: regression in suspend) Pavel Machek
2014-06-21 20:29 ` 3.16, i915: less colors in X? Pavel Machek
2014-06-21 20:35 ` Pavel Machek
2014-06-21 21:06 ` Chris Wilson
2014-06-22 14:26 ` Pavel Machek
2014-06-22 15:11 ` regression: 3.16, i915: less colors in X?, caused by 773875bfb6737982903c42d1ee88cf60af80089c Pavel Machek
2014-06-21 21:16 ` 3.16, i915: less colors in X? Martin Steigerwald
2014-06-25 22:35 ` Pavel Machek [this message]
2014-06-27 13:37 ` 3.15-rc: regression in suspend Jiri Kosina
2014-07-07 8:39 ` Daniel Vetter
2014-07-11 19:26 ` Pavel Machek
2014-07-11 23:33 ` Jiri Kosina
2014-08-07 12:47 ` Jiri Kosina
2014-08-07 12:54 ` Jiri Kosina
2014-08-07 14:36 ` [Intel-gfx] " Daniel Vetter
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=20140625223522.GA5923@xo-6d-61-c0.localdomain \
--to=pavel@ucw.cz \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=rjw@rjwysocki.net \
/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).