From: Chris Wilson <chris@chris-wilson.co.uk>
To: Pekka Enberg <penberg@kernel.org>
Cc: Dave Airlie <airlied@linux.ie>,
torvalds@linux-foundation.org,
DRI mailing list <dri-devel@lists.freedesktop.org>,
linux-kernel@vger.kernel.org
Subject: Re: [git pull] drm fixes for -rc1
Date: Tue, 29 Mar 2011 08:49:52 +0100 [thread overview]
Message-ID: <b9dded$ififhr@orsmga002.jf.intel.com> (raw)
In-Reply-To: <AANLkTi=VqkYjdiDLJvM-OfmBSGx-EkRkt=4XCDEnvZsU@mail.gmail.com>
On Tue, 29 Mar 2011 10:11:21 +0300, Pekka Enberg <penberg@kernel.org> wrote:
> On Mon, Mar 28, 2011 at 10:09 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Let me know if there's a patch/git tree to test. The flicker is
> extremely annoying and I boot the machine often because it's my main
> kernel development laptop.
I will let you know as soon as I have something ready for testing.
> > That's an old userspace bug, which so far no one has been able to
> > reproduce on the upstream ddx.
>
> Is it harmless? Why is the kernel complaining about it?
Being pragmatic, so that I can tell one EINVAL apart from another. And
it's only mostly harmless. Userspace is attempting to write to/read from
a buffer it has marked as being no longer required, so some rendering is
going amiss. And it does not rule out the possibility that at some point
it will catch the error later and result in a SIGBUS being sent to the
application (probably X).
However since it is not a kernel error nor is it fatal, that and a lot of
similar messages can be demoted to debug.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-03-29 7:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 11:34 [git pull] drm fixes for -rc1 Dave Airlie
2011-03-28 18:43 ` Pekka Enberg
2011-03-28 18:53 ` Pekka Enberg
2011-03-28 19:09 ` Chris Wilson
2011-03-29 7:11 ` Pekka Enberg
2011-03-29 7:49 ` Chris Wilson [this message]
2011-03-29 10:46 ` [PATCH] drm/i915: Disable all outputs early, before KMS takeover Chris Wilson
2011-03-29 12:23 ` [PATCH] drm/i915: Move the irq wait queue initialisation into the ring init Chris Wilson
2011-03-29 13:05 ` Pekka Enberg
2011-03-29 13:22 ` Chris Wilson
2011-03-29 13:39 ` Pekka Enberg
2011-03-29 14:22 ` Pekka Enberg
2011-03-29 14:32 ` Chris Wilson
2011-03-29 15:21 ` Pekka Enberg
2011-04-01 11:44 ` [Intel-gfx] [PATCH] drm/i915: Disable all outputs early, before KMS takeover Daniel Vetter
2011-04-01 11:51 ` Pekka Enberg
2011-04-05 10:21 ` Tomas Winkler
2011-04-05 10:30 ` Chris Wilson
2011-04-05 10:37 ` Pekka Enberg
2011-04-05 11:55 ` Tomas Winkler
2011-04-05 14:11 ` Pekka Enberg
2011-04-05 14:27 ` Chris Wilson
2011-04-05 14:31 ` Pekka Enberg
2011-04-05 14:34 ` Chris Wilson
2011-04-05 15:11 ` Pekka Enberg
2011-04-05 15:32 ` Chris Wilson
2011-04-05 15:44 ` Pekka Enberg
2011-04-05 14:42 ` [Intel-gfx] " Linus Torvalds
2011-04-05 15:01 ` Keith Packard
2011-04-05 15:12 ` Chris Wilson
2011-04-05 15:35 ` Pekka Enberg
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$ififhr@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=torvalds@linux-foundation.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