From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Zou Nan hai <nanhai.zou@intel.com>,
Xiang Hai hao <haihao.xiang@intel.com>,
Eric Anholt <eric@anholt.net>, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org
Subject: Re: 2.6.35-rc6+: i915: Bisected regression
Date: Sun, 01 Aug 2010 13:42:24 +0200 [thread overview]
Message-ID: <4C555DA0.6020109@s5r6.in-berlin.de> (raw)
In-Reply-To: <201008011101.01429.thomas@m3y3r.de>
Thomas Meyer wrote:
> This commit makes suspend to ram unreliable for me:
>
> commit d1b851fc0d105caa6b6e3e7c92d2987dfb52cbe0
> Author: Zou Nan hai <nanhai.zou@intel.com>
> Date: Fri May 21 09:08:57 2010 +0800
>
> drm/i915: implement BSD ring buffer V2
>
> The BSD (bit stream decoder) ring is used for accessing the BSD engine
> which decodes video bitstream for H.264 and VC1 on G45+. It is
> asynchronous with the render ring and has access to separate parts of
> the GPU from it, though the render cache is coherent between the two.
>
> Signed-off-by: Zou Nan hai <nanhai.zou@intel.com>
> Signed-off-by: Xiang Hai hao <haihao.xiang@intel.com>
> Signed-off-by: Eric Anholt <eric@anholt.net>
>
> git revert didn't work on 2.6.35-rc6 so I just changed the HAS_BSD thing to:
>
> #define HAS_BSD(dev) (0)
>
> with this change applied suspend to ram is back to the reliability of 2.6.34.y
>
> with kind regards
> thomas
Added CCs.
Thomas, on what hardware did you observe the regression? Is it suspend
or resume that is unreliable? What are the particular symptoms --- does
not suspend, crashes during suspend, crashes during resume...?
--
Stefan Richter
-=====-==-=- =--- ----=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2010-08-01 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 9:01 Thomas Meyer
2010-08-01 11:42 ` Stefan Richter [this message]
2010-08-01 10:51 ` Thomas Meyer
2010-08-01 13:14 ` Paul Rolland
2010-08-01 15:17 ` Roberto Oppedisano
2010-08-24 17:36 ` Thomas Meyer
2010-08-25 3:02 ` Roberto Oppedisano
2010-08-25 13:41 ` Paul Rolland
2010-08-05 5:43 ` Shuang He
2010-08-06 3:26 ` David John
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=4C555DA0.6020109@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=haihao.xiang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nanhai.zou@intel.com \
--cc=thomas@m3y3r.de \
/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®