From: Mark Lord <kernel@teksavvy.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: Linux 2.6.39 -- *ERROR* Attempting to mmap a purgeable buffer
Date: Fri, 20 May 2011 21:57:07 -0400 [thread overview]
Message-ID: <4DD71BF3.5030906@teksavvy.com> (raw)
In-Reply-To: <BANLkTim-u1_ixT517dWd-p4zXgaU=LLg1A@mail.gmail.com>
On 11-05-20 06:00 PM, Linus Torvalds wrote:
> On Thu, May 19, 2011 at 8:26 AM, Mark Lord <kernel@teksavvy.com> wrote:
>>
>> Just got weird stuff in the syslog this morning from rc7-git12:
>>
>> [43190.824700] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a purgeable buffer
>> [43190.827426] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a purgeable buffer
>> [43190.827506] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a purgeable buffer
>> [43190.827568] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a purgeable buffer
>> [43190.828685] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a purgeable buffer
>> [43190.830498] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a purgeable buffer
>> [43190.830603] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a purgeable buffer
>> [43190.831055] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a purgeable buffer
>> [43190.832580] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a purgeable buffer
>> [43190.832788] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a purgeable buffer
>
> Quoting from an earlier mail about this issue from the DRM people:
>
> "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."
>
> So it's basically user space trying to access something stale, but it
> should be harmless.
Peachy. I suspect the messages get generated when I run gmplayer or vlc
(not sure which, don't really care much either).
Thanks.
next prev parent reply other threads:[~2011-05-21 1:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 5:04 Linux 2.6.39 Linus Torvalds
2011-05-19 5:32 ` Stephen Rothwell
2011-05-19 15:26 ` Linux 2.6.39 -- *ERROR* Attempting to mmap a purgeable buffer Mark Lord
2011-05-20 22:00 ` Linus Torvalds
2011-05-21 1:57 ` Mark Lord [this message]
2011-05-19 15:44 ` Linux 2.6.39 Mark Lord
2011-05-19 15:47 ` Randy Dunlap
2011-05-19 16:16 ` Catalin Marinas
2011-05-19 16:23 ` Randy Dunlap
2011-05-23 10:49 ` Catalin Marinas
2011-05-21 17:56 ` Milan Oravec
2011-05-21 20:31 ` Ed Tomlinson
2011-05-23 22:08 ` Ed Tomlinson
2011-05-25 8:27 ` Ville Tervo
2011-05-25 21:19 ` Milan Oravec
2011-06-21 21:08 ` Milan Oravec
2011-05-22 1:12 ` Uwaysi Bin Kareem
2011-05-22 7:22 ` CaT
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=4DD71BF3.5030906@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=chris@chris-wilson.co.uk \
--cc=linux-kernel@vger.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 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.