From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89957] vm protection faults in piglit lest: texsubimage cube_map_array pbo
Date: Wed, 08 Apr 2015 17:23:22 +0000 [thread overview]
Message-ID: <bug-89957-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1225 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=89957
Bug ID: 89957
Summary: vm protection faults in piglit lest: texsubimage
cube_map_array pbo
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: tstellar@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
To reproduce: /home/tstellar/piglit/bin/texsubimage cube_map_array pbo -auto
-fbo
I've spent some time debugging this and it appears the result from the
v_cubeid_f32
instruction is causing the shader to access memory outside the bounds of the
texture.
If I replace v_cubeid_f32 $dst, $src0, $src1, $src2 instructions with v_mov_f32
$dst, 0.0 or v_mov_f32 $dst, 1.0
I no longer see vm protection faults.
However, if I replace the v_cubeid_f32 instructions with v_mov_f32 $dst, 2.0
then the vm protection faults return. So, it seems the bad case is whenever
the face id is computed as >= 2.0f.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2527 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-04-08 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 17:23 bugzilla-daemon [this message]
2015-04-08 17:30 ` [Bug 89957] vm protection faults in piglit lest: texsubimage cube_map_array pbo bugzilla-daemon
2015-04-13 23:20 ` bugzilla-daemon
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=bug-89957-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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.