dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83319] [r600g] GPU lockup in gsraytrace (Mesa-demo-8.2.0) - RV730
Date: Wed, 25 Nov 2015 01:46:30 +0000	[thread overview]
Message-ID: <bug-83319-502-eTJFNPOJGN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83319-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1003 bytes --]

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

--- Comment #11 from Dieter Nützel <Dieter@nuetzel-hh.de> ---
(In reply to Dieter Nützel from comment #3)
> (In reply to comment #2)
> > Yeah, texturing in geometry shaders hangs. The problem might be that the GS
> > RING constant buffer is bound to slot 16, which isn't a valid constant
> > buffer slot (the last one is 15).
> 
> Hello Marek!
> 
> We're back from vacation, so...;-)
> 
> Read about it (R600_MAX_CONST_BUFFERS) in Glenn Kennard
> <glenn.kennard@gmail.com> patch:
> [Mesa-dev] [PATCH] r600g: Implement GL_ARB_sample_shading
> 
> Is it that what you mean?
> Either way, following the shader dumps.
> 
> BTW I have a broken screen shot for geom-outlining-150.png, too if you need.

Broken rendering for 'geom-outlining-150' and
ogl-samples: 'gl-320-primitive-shading'

is FIXED with Mesa-11.0.6 (git, too) on RV730 AGP at least.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2035 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

  parent reply	other threads:[~2015-11-25  1:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-31 22:59 [Bug 83319] New: [r600g] GPU lockup in gsraytrace (Mesa-demo-8.2.0) - RV730 bugzilla-daemon
2014-08-31 23:00 ` [Bug 83319] " bugzilla-daemon
2014-09-01 11:17 ` bugzilla-daemon
2014-09-01 11:37 ` bugzilla-daemon
2014-09-01 11:40 ` bugzilla-daemon
2014-09-01 11:40 ` bugzilla-daemon
2014-09-01 12:48 ` bugzilla-daemon
2014-10-23 18:34 ` bugzilla-daemon
2015-07-30  2:50 ` bugzilla-daemon
2015-09-02 18:23 ` bugzilla-daemon
2015-09-03 13:36 ` bugzilla-daemon
2015-11-25  1:46 ` bugzilla-daemon [this message]
2015-11-25  1:50 ` bugzilla-daemon
2015-11-25  6:34 ` bugzilla-daemon
2015-11-27  3:34 ` bugzilla-daemon
2016-01-14 10:10 ` bugzilla-daemon
2016-01-14 16:37 ` bugzilla-daemon
2016-01-14 21:58 ` bugzilla-daemon
2019-09-18 19:17 ` 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-83319-502-eTJFNPOJGN@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox