Bug 31419 - dmesg: [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap a purgeable buffer
dmesg: [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap a purgeable b...
Status: RESOLVED NOTOURBUG
Product: xorg
Classification: Unclassified
Component: Driver/intel
unspecified
Other All
: medium normal
Assigned To: Carl Worth
Xorg Project Team
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-05 14:15 UTC by Cristian Aravena
Modified: 2011-04-17 00:47 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg 2.6.37-rc2 (55.63 KB, text/plain)
2010-11-20 11:34 UTC, Cristian Aravena
no flags Details
dmesg 2.6.37-rc3 (72.41 KB, text/plain)
2010-11-24 11:13 UTC, Cristian Aravena
no flags Details
dmesg 2.6.37-rc5 (54.65 KB, text/plain)
2010-12-08 06:30 UTC, Cristian Aravena
no flags Details
#lspci -vvnn (28.46 KB, text/plain)
2010-12-08 06:33 UTC, Cristian Aravena
no flags Details
Xorg.0.log (35.60 KB, text/plain)
2011-02-05 11:42 UTC, Cristian Aravena
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Cristian Aravena 2010-11-05 14:15:04 UTC
Open bug in bugzilla.kernel.org :
https://bugzilla.kernel.org/show_bug.cgi?id=21982

dmesg 2.6.37-rc1:
"[  391.317411] [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap a
purgeable buffer
[  391.317527] [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap a
purgeable buffer
[  391.317597] [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap a
purgeable buffer"
Comment 1 Cristian Aravena 2010-11-20 11:34:14 UTC
Created attachment 40440 [details]
dmesg 2.6.37-rc2
Comment 2 Cristian Aravena 2010-11-24 11:13:47 UTC
Created attachment 40555 [details]
dmesg 2.6.37-rc3

dmesg:

[ 2626.424735] [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap a purgeable buffer
Comment 3 Cristian Aravena 2010-12-08 06:30:07 UTC
Created attachment 40919 [details]
dmesg 2.6.37-rc5

[ 5260.821832] [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap a purgeable buffer
Comment 4 Chris Wilson 2010-12-08 06:32:32 UTC
It's still a userspace application that's at fault...
Comment 5 Cristian Aravena 2010-12-08 06:33:10 UTC
Created attachment 40920 [details]
#lspci -vvnn

00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
Comment 6 Cristian Aravena 2010-12-08 14:18:04 UTC
(In reply to comment #4)
> It's still a userspace application that's at fault...

How do I know which application?
Comment 7 Cristian KLEIN 2011-01-25 01:37:47 UTC
Hello,

I have the same issue. In addition Xorg.0.log contains the following messages:

(WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
(EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: Invalid argument.
Comment 8 Cristian Aravena 2011-02-05 11:42:38 UTC
Created attachment 42969 [details]
Xorg.0.log

[ 72393.727] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
[ 72393.742] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
[ 72393.742] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
[ 73250.715] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
[ 73250.716] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
[ 73250.716] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
[ 75648.703] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
[ 75648.703] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
[ 76377.979] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
[ 78205.292] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
[ 79666.971] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
[ 79808.825] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
[ 81787.174] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Invalid argument
Comment 9 Chris Wilson 2011-04-17 00:47:16 UTC
You won't find the offending code in the upstream driver...