Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756468Ab1ETWB5 (ORCPT ); Fri, 20 May 2011 18:01:57 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:57415 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752702Ab1ETWBv (ORCPT ); Fri, 20 May 2011 18:01:51 -0400 MIME-Version: 1.0 In-Reply-To: <4DD5369B.1010601@teksavvy.com> References: <4DD5369B.1010601@teksavvy.com> From: Linus Torvalds Date: Fri, 20 May 2011 15:00:59 -0700 Message-ID: Subject: Re: Linux 2.6.39 -- *ERROR* Attempting to mmap a purgeable buffer To: Mark Lord Cc: Linux Kernel Mailing List , Chris Wilson Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1857 Lines: 35 On Thu, May 19, 2011 at 8:26 AM, Mark Lord 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. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/