From: Pavel Machek <pavel@ucw.cz>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 3.15-rc: regression in suspend
Date: Wed, 14 May 2014 22:31:15 +0200 [thread overview]
Message-ID: <20140514203115.GB5855@amd.pavel.ucw.cz> (raw)
In-Reply-To: <alpine.LNX.2.00.1405141809000.16459@pobox.suse.cz>
On Wed 2014-05-14 18:10:22, Jiri Kosina wrote:
> On Wed, 14 May 2014, Pavel Machek wrote:
>
> > > So it might in the end of the day the same thing as I have reported in
> > >
> > > https://bugs.freedesktop.org/show_bug.cgi?id=76554
> > >
> > > which is not 100% reproducible either (although with newer kernels it's
> > > *much* more reproducible for me than with older).
> > >
> > > > It worked few times on -rc5, but then I rebooted and problem
> > > > re-appeared.
> > >
> > > If you could capture dmesg of the resume where X fails to resume properly
> > > to see whether you have i915 ring initialization errors there as well?
> >
> > I did dmesg and I believe I would have noticed "*ERROR*" there.. but
> > I'll of course capture the buffer when it happens.
>
> Thanks.
Ok, so it happened again and the *ERROR* was there ... see the other mail.
> > Note that X do work somehow after resume (I can't switch virtual
> > desktops and dialog is stuck on screen, but it is not complete
> > failure). I can do ctrl-alt-f1 and get to useful prompt.
>
> I have similar symptoms. The windows are not redrawing, etc.
Yep, it seems we have same bug.
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-05-14 20:31 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 [this message]
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 ` 3.15-rc: regression in suspend Pavel Machek
2014-06-27 13:37 ` 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=20140514203115.GB5855@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--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).