Nouveau - Aug 2013 - [Bug 68348] New: [piglit] shaders/glsl-array-bounds-02 (+even nrs) produces TRAP , TRAP_MP - TP0: Unhandled ustatus 0x00000001

https://bugs.freedesktop.org/show_bug.cgi?id=68348

          Priority: medium
            Bug ID: 68348
          Assignee: nouveau at lists.freedesktop.org
           Summary: [piglit] shaders/glsl-array-bounds-02 (+even nrs)
                    produces TRAP , TRAP_MP - TP0: Unhandled ustatus
                    0x00000001
        QA Contact: xorg-team at lists.x.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: dirkneukirchen at web.de
          Hardware: x86 (IA32)
            Status: NEW
           Version: git
         Component: Driver/nouveau
           Product: xorg

Created attachment 84353
  --> https://bugs.freedesktop.org/attachment.cgi?id=84353&action=edit
dmesg with many instances of problem occuring (while isolating the piglit
testcase)

./piglit-run.py --no-concurrency -t  '^shaders/glsl-array-bounds-02'
tests/quick.tests results/quick-shaders-array.tests

and all other even numbered cases 
glsl-array-bounds-04
glsl-array-bounds-06
glsl-array-bounds-08

print out success but get a kernel log entry like 

[ 4653.971680] nouveau E[  PGRAPH][0000:02:00.0] TRAP_MP - TP0: Unhandled
ustatus 0x00000001
[ 4653.971688] nouveau E[  PGRAPH][0000:02:00.0]  TRAP
[ 4653.971695] nouveau E[  PGRAPH][0000:02:00.0] ch 5 [0x0007814000
shader_runner[8809]] subc 3 class 0x8397 mthd 0x15e0 data 0x00000000

found with heavy use of exclude -x feature :)


Hardware:
Nvidia 8200 Onboard NVAA/NV50
nouveau  [  DEVICE][0000:02:00.0] Chipset: MCP77/MCP78 (NVAA)
nouveau  [  DEVICE][0000:02:00.0] Family : NV50

Software:
Linux Mint 15 + xorg-edgers + 3.11-rc5
Kernel: 3.11.0-rc5-vanillaice (compiled)
libdrm-nouveau: 2.4.46+git20130702.c6d73cfe-0ubuntu0sarvatt~raring
xserver-xorg-video-nouveau :
1:1.0.9+git20130730.300c5a32-0ubuntu0sarvatt~raring
mesa: 9.2.0~git20130729+9.2.9b8ad643-0ubuntu0sarvatt~raring

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20130820/a1f20efd/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=68348

--- Comment #1 from Ilia Mirkin <imirkin at alum.mit.edu> ---
The big difference between the even and odd numbered
shaders/glsl-array-bounds-* seems to be how the invalid index comes about.

In the odd-numbered ones, it comes directly from shader code, e.g.:

void main() {
  int idx = 20;
  array[idx]
}

In the even-numbered ones, it comes from a uniform that I guess is passed in:

uniform int idx;

void main() {
  array[idx]
}

(And the various tests check fragment/vertex shaders, positive/negative
offsets, and the place where the idx comes from, so 8 tests total.)

Although I'm not sure there's actually a problem here... the program is
doing
something illegal. You get segfault notifications in dmesg too...

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20130820/99ad0f39/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=68348

Tobias Klausmann <tobias.klausmann at mni.thm.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #2 from Tobias Klausmann <tobias.klausmann at mni.thm.de> ---
Is this still a bug with recent kernels and other software? Please retest with
3.19-rc4 as there were some fixes for these chips in particular.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20150117/43bfd153/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=68348

--- Comment #3 from Tobias Klausmann <tobias.klausmann at mni.thm.de> ---
Noted on IRC by pmoureau:

Tests {2-8} are working fine while {10, 12} are still failing with a similar
error on MCP79/7A (the closest we got)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20150117/182f21c3/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=68348

--- Comment #4 from Ilia Mirkin <imirkin at alum.mit.edu> ---
The piglit test got changed in the meanwhile. It's an out-of-bounds access,
I
think the error in dmesg is legit...ish. Not sure. We could turn off error
reporting, which afaik is what the blob does.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20150117/c26521c7/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=68348

Ilia Mirkin <imirkin at alum.mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |RESOLVED
         Resolution|---                         |NOTABUG

--- Comment #5 from Ilia Mirkin <imirkin at alum.mit.edu> ---
We don't disable error reporting, so you'll see stuff like that in
dmesg.
Expected.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151022/81432111/attachment.html>