From: Peter Clifton <pcjc2@cam.ac.uk>
To: Seblu <seblu@seblu.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Fwd: 2.6.36-rc5 i915 regression
Date: Tue, 26 Oct 2010 00:47:33 +0100 [thread overview]
Message-ID: <1288050453.795.9.camel@pcjc2lap> (raw)
In-Reply-To: <AANLkTi=NB+HVCZ--WV2Cr1cgPqJA6aUHEhaqxbkdxWTY@mail.gmail.com>
On Tue, 2010-10-26 at 01:19 +0200, Seblu wrote:
> i've tryed last git kernel with edp-fixes from
> git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/drm-intel.git,
> i've the following result :
> http://videobin.org/+2a3/2kn.ogg
For future reference.. its probably not a good idea to let that
condition persist. There is a chance it might damage the LCD if it is
powered but not being driven properly.
> with intel-drm-next from
> git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git,
> it's better!
> My screen is back. Do you include those patch in 2.6.37?
>
> But:
> - suspend to RAM cause a computer freeze.
Do you have this commit from drm-next recently?:
commit 641934069d29211baf82afb93622a426172b67b6
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Sun Oct 24 12:38:05 2010 +0100
drm/i915: Move gpu_write_list to per-ring
... to prevent flush processing of an idle (or even absent) ring.
This fixes a regression during suspend from 87acb0a5.
Reported-and-tested-by: Alexey Fisher <bug-track@fisher-privat.net>
Tested-by: Peter Clifton <pcjc2@cam.ac.uk>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
It fixed my suspend.
> - after one day, applications become graphically slow.
No clue there I'm afraid.
--
Peter Clifton
Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA
Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)
next prev parent reply other threads:[~2010-10-25 23:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 11:00 2.6.36-rc5 i915 regression Johannes Hirte
2010-10-01 12:28 ` Chris Wilson
2010-10-01 12:28 ` Chris Wilson
2010-10-01 12:55 ` Seblu
2010-10-01 13:22 ` Chris Wilson
2010-10-01 20:27 ` Seblu
2010-10-02 9:07 ` Zhenyu Wang
2010-10-07 23:24 ` Seblu
2010-10-09 9:40 ` Seblu
2010-10-10 13:52 ` Seblu
[not found] ` <AANLkTinTX9hXMV+nn-qQjsGq-_fF8mwGc6p1P_-csJUR@mail.gmail.com>
[not found] ` <89k77n$p72i7f@fmsmga001.fm.intel.com>
2010-10-18 16:38 ` Fwd: " Seblu
2010-10-25 23:19 ` Seblu
2010-10-25 23:47 ` Peter Clifton [this message]
2010-10-26 0:57 ` Seblu
2010-10-26 1:42 ` Peter Clifton
2010-10-26 2:13 ` Seblu
2010-10-26 8:30 ` Chris Wilson
2010-10-26 8:49 ` Seblu
2010-10-26 9:25 ` Chris Wilson
2010-11-02 10:04 ` Seblu
2010-10-30 20:13 ` Chun-Yu Shei
2010-10-01 18:15 ` Johannes Hirte
2010-10-01 13:01 ` Seblu
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=1288050453.795.9.camel@pcjc2lap \
--to=pcjc2@cam.ac.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=seblu@seblu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.