Comment 32 for bug 1401788

(In reply to comment #29)
> Whilst I think this is related to the userptr blit, there is a chance that
> the corruption is due to a render operation whilst the userptr is still
> bound in the aperture. So can I ask you retest with the latest stack?

Test on latest -nightly kernel and X.It still exists.
output:
rendercheck 1.4
Render extension version 0.11
Window format: r8g8b8
Found server-supported format: a8
Found server-supported format: a8r8g8b8
Found server-supported format: x8r8g8b8
Found server-supported format: b8g8r8a8
Found server-supported format: b8g8r8x8
Found server-supported format: r8g8b8
Found server-supported format: b8g8r8
Found server-supported format: r5g5b5
Found server-supported format: b5g5r5
Found server-supported format: x1r5g5b5
Found server-supported format: x1b5g5r5
Found server-supported format: r5g6b5
Found server-supported format: b5g6r5
Found server-supported format: x8b8g8r8
Found server-supported format: x2r10g10b10
Found server-supported format: x2b10g10r10
Beginning dest coords test
dst coords test error of 255.0000 at (0, 0) --
           R G B A
got: 1.000 0.000 0.000 1.000
expected: 1.000 1.000 1.000 1.000
dst coords test error of 255.0000 at (0, 1) --
           R G B A
got: 0.000 0.000 0.000 1.000
expected: 1.000 1.000 1.000 1.000
dst coords test error of 255.0000 at (0, 2) --
           R G B A
got: 1.000 0.000 0.000 1.000
expected: 1.000 1.000 1.000 1.000
dst coords test error of 255.0000 at (0, 4) --
           R G B A
got: 0.000 0.000 0.000 1.000
expected: 1.000 1.000 1.000 1.000
dst coords test error of 255.0000 at (1, 1) --
           R G B A
got: 0.000 0.000 0.000 1.000
expected: 1.000 0.000 0.000 1.000
dst coords test error of 255.0000 at (1, 2) --
           R G B A
got: 1.000 1.000 1.000 1.000
expected: 1.000 0.000 0.000 1.000
dst coords test error of 255.0000 at (1, 3) --
           R G B A
got: 1.000 1.000 1.000 1.000
expected: 1.000 0.000 0.000 1.000
dst coords test error of 255.0000 at (1, 4) --
           R G B A
got: 0.000 0.000 0.000 1.000
expected: 1.000 1.000 1.000 1.000
dst coords test error of 255.0000 at (2, 1) --
           R G B A
got: 1.000 1.000 1.000 1.000
expected: 1.000 0.000 0.000 1.000
dst coords test error of 255.0000 at (2, 2) --
           R G B A
got: 1.000 1.000 1.000 1.000
expected: 1.000 0.000 0.000 1.000
dst coords test error of 255.0000 at (2, 3) --
           R G B A
got: 0.000 0.000 0.000 1.000
expected: 1.000 0.000 0.000 1.000
dst coords test error of 255.0000 at (2, 4) --
           R G B A
got: 0.000 0.000 0.000 1.000
expected: 1.000 1.000 1.000 1.000
dst coords test error of 255.0000 at (3, 2) --
           R G B A
got: 1.000 1.000 1.000 1.000
expected: 1.000 0.000 0.000 1.000
dst coords test error of 255.0000 at (3, 3) --
           R G B A
got: 0.000 0.000 0.000 1.000
expected: 1.000 0.000 0.000 1.000
dst coords test error of 255.0000 at (3, 4) --
           R G B A
got: 0.000 0.000 0.000 1.000
expected: 1.000 1.000 1.000 1.000
dst coords test error of 255.0000 at (4, 1) --
           R G B A
got: 1.000 0.000 0.000 1.000
expected: 1.000 1.000 1.000 1.000
dst coords test error of 255.0000 at (4, 3) --
           R G B A
got: 0.000 0.000 0.000 1.000
expected: 1.000 1.000 1.000 1.000
dst coords test error of 255.0000 at (4, 4) --
           R G B A
got: 0.000 0.000 0.000 1.000
expected: 1.000 1.000 1.000 1.000
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 550 requests (550 known processed) with 0 events remaining.
xinit: connection to X server lost
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0"
[1]+ Done xinit (wd: /opt)
(wd now: /GFX/Test/Rendercheck/bin)