From: Chris Wilson <chris@chris-wilson.co.uk>
To: Dave Airlie <airlied@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
dri-devel@lists.freedesktop.org, Dave Airlie <airlied@linux.ie>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Keith Packard <keithp@keithp.com>, Eric Anholt <eric@anholt.net>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: DRM Error on Acer Aspire One
Date: Tue, 11 May 2010 23:40:41 +0100 [thread overview]
Message-ID: <89khjo$fd48jf@orsmga002.jf.intel.com> (raw)
In-Reply-To: <AANLkTikM916RlCBudL9_Pw--cpiu5mg_xcLFG9N1l9tL@mail.gmail.com>
On Wed, 12 May 2010 08:22:49 +1000, Dave Airlie <airlied@gmail.com> wrote:
> I'd rather we just backout the hangcheck stuff touching copies at all
> at this point, and try again doing it properly with a slow work or
> something for later.
>From my point of view, the information provided by the hangcheck has been
invaluable for delving into and fixing some obnoxious driver bugs. I
suspect its honeymoon period is now over - those bugs that it could
detect easily have been fixed (I hope). In order to capture the relevant
information for later chipset generations, we will need to parse the
command stream and include auxiliary buffers. So whilst I would prefer to
see this in a release so that I can easily diagnose bug reports, I accept
that there is more work to be done and will HTFU.
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-05-11 22:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 15:00 DRM Error on Acer Aspire One Jaswinder Singh Rajput
2010-05-11 16:10 ` Chris Wilson
2010-05-11 14:48 ` Andrew Morton
2010-05-11 18:18 ` Jaswinder Singh Rajput
2010-05-11 18:19 ` Chris Wilson
2010-05-11 15:35 ` Andrew Morton
2010-05-11 18:52 ` Chris Wilson
2010-05-11 19:10 ` Andrew Morton
2010-05-11 19:57 ` Chris Wilson
2010-05-11 22:22 ` Dave Airlie
2010-05-11 22:32 ` Andrew Morton
2010-05-11 22:51 ` Dave Airlie
2010-05-11 22:56 ` Andrew Morton
2010-05-11 23:17 ` Dave Airlie
2010-05-11 23:24 ` Andrew Morton
2010-05-11 22:40 ` Chris Wilson [this message]
2010-05-11 17:39 ` Jaswinder Singh Rajput
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='89khjo$fd48jf@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=jaswinderlinux@gmail.com \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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