From: Chris Wilson <chris@chris-wilson.co.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 10:25:49 +0100 [thread overview]
Message-ID: <b9dded$gt4dll@orsmga002.jf.intel.com> (raw)
In-Reply-To: <AANLkTi=p=4-MYQRrzWOJPGMa++78RryTcSjxSLjDUWuh@mail.gmail.com>
On Tue, 26 Oct 2010 10:49:01 +0200, Seblu <seblu@seblu.net> wrote:
> On Tue, Oct 26, 2010 at 10:30 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > Depending on where the tip was, at least one suspend regression was
> > recently fixed. It would be useful to recheck with 64193406.
> Yes i have this patch in, and the issue is still here.
Oh 6410. Yeah, that regression was pre-g4x. Do you have a good idea of the
precise range in which the regression was introduced, or is just another
eDP misery?
> Do you have seen this vmideo, which show the suspend to ram issue with
> ailine and drm-next and how it's functional with 2.6.35.7?
>
> http://videobin.org/+2a5/2kp.ogg
>
> >
> >> - after one day, applications become graphically slow.
> >
> > You're not alone. Eric has reported that writes to a GTT mapping become
> > glacially slow after some time, without any distortion in the CPU profile.
> > Can we collate what hardware we are seeing this effect on?
> lspci,lshw,cpuinfo, you did somthing more?
Just the chipset [Arrandale, in this case] for the time being, so I know
which machines to leave running to see if I can observe the effect here.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-10-26 9:25 UTC|newest]
Thread overview: 20+ 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: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
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 [this message]
2010-11-02 10:04 ` Seblu
2010-10-30 20:13 ` Chun-Yu Shei
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='b9dded$gt4dll@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox