From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: intel-gfx@lists.freedesktop.org, Chris Wilson <chris@chris-wilson.co.uk>
Cc: dri-devel@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Linux PM list" <linux-pm@vger.kernel.org>,
"Stéphane Marchesin" <marcheu@chromium.org>
Subject: Re: [Regression in 3.10] Garbage displayed after resume on Acer Aspire S5
Date: Sun, 07 Jul 2013 01:36:15 +0200 [thread overview]
Message-ID: <14306109.Kf2NcaamIl@vostro.rjw.lan> (raw)
In-Reply-To: <1511667.B4N0cEgdH9@vostro.rjw.lan>
On Saturday, July 06, 2013 03:59:49 PM Rafael J. Wysocki wrote:
> Hi,
>
> I've just started to play with a new Acer Aspire S5 test box and noticed that
> garbage is displayed after resume from suspend to RAM with the 3.10 kernel
> (under KDE 4.10.3 on openSUSE 12.3). The display corruption goes away after
> killing X and restarting it.
>
> The CPU is a Core i5-3317U (Ivy Bridge), i915 graphics.
>
> That doesn't happen with 3.9 (same config otherwise). It also doesn't happen
> with my older Sandy Bridge-based box (with 3.10), so I suspect Ivy Bridge
> specifics.
>
> Is this known? Do you want me to bisect?
Most likely, this has been introduced by this commit:
commit 19b2dbde5732170a03bd82cc8bd442cf88d856f7
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Wed Jun 12 10:15:12 2013 +0100
drm/i915: Restore fences after resume and GPU resets
At least I'm not able to reproduce it with that commit reverted. With that
commit in I was able to reproduce it quite readily on machines with Ivy Bridge
and Sandy Bridge processors.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-07-06 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-06 13:59 Rafael J. Wysocki
2013-07-06 14:16 ` Daniel Vetter
2013-07-06 20:26 ` Rafael J. Wysocki
2013-07-06 21:47 ` Rafael J. Wysocki
2013-07-06 23:36 ` Rafael J. Wysocki [this message]
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=14306109.Kf2NcaamIl@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marcheu@chromium.org \
/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
all inboxes | Powered by JetHome®