Comment=
# 6
on bug 91780<=
/a>
from Jonas Wielicki
(In reply to Dieter N=C3=BCtzel 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 thi=
s 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 renderi=
ng
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 vis=
ual
output in the window; no rendering took place, the window contents were nev=
er
written and were showing what was at that place on the screen before the wi=
ndow
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 openi=
ng 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 ab=
ove
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=E2=80=99t think I will get better results on my own.