[Bug 91780] Rendering issues with geometry shader - bugzilla-daemon

From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91780] Rendering issues with geometry shader
Date: Thu, 03 Sep 2015 09:59:24 +0000	[thread overview]
Message-ID: <bug-91780-502-xywaaZ71Tz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91780-502@http.bugs.freedesktop.org/>

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

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

--- Comment #6 from Jonas Wielicki <jonas@wielicki.name> ---
(In reply to Dieter Nützel from comment #2)
> And maybe test Mesa-demo 'gsraytrace'?

I am having a hard time to get gsraytrace to run. I am not sure whether this is
related to this bug or to PRIME issues, as in general, using the Radeon GPU is
a bit unstable here. The instability manifests in not receiving any rendering
output in the window and sometimes error messages ("radeon: The kernel rejected
CS, see dmesg for more information.").

I made two tests:

FIRST TEST

When trying to run the gsraytrace demo on the radeon, I did not receive visual
output in the window; no rendering took place, the window contents were never
written and were showing what was at that place on the screen before the window
opened. The terminal suggested a frame rate of 1 FPS. No crash happened.

I then tried to distinguish between PRIME failure and demo failure by opening a
glxgears instance on the radeon gpu, which made the whole X11 freeze for a few
seconds and afterwards both glxgears and the gsraytrace demo spammed the above
error message.

SECOND TEST

This time, I started glxgears first to make sure that everything was set up
properly, PRIME-wise. glxgears was running fine at a reasonable frame rate.

Then I started the gsraytrace demo, which made the X11 freeze. (I then went to
fetch some tea) Both programs were spamming the above error message when the
GUI had unfreezed.

At no point I ever saw visual output from the gsraytrace demo. As I said, I am
not sure what of this is purely due to PRIME and what is caused by the bug this
entry refers to. I just wanted to add my data here as it was requested for and
I don’t think I will get better results on my own.

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

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