FYI, the latest Mesa skips further command submissions (CS) only if you set
{GLX_CONTEXT_RESET_NOTIFICATION_STRATEGY_ARB,
GLX_LOSE_CONTEXT_ON_RESET_ARB} and the CS ioctl fails.
Previous Mesa versions always stopped further command submissions after a
failure and ignored the GLX (and EGL) flags.
M
On 2019-02-03 2:15 a.m., Stuart Young wrote:
> Jean has logged 3 versions of the same bug in Debian, as he wasn't sure
> which package was causing the issues.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921114
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921145
> https://bugs.d
Jean has logged 3 versions of the same bug in Debian, as he wasn't sure
which package was causing the issues.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921114
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921145
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921004
None of the b
On Sat, Feb 2, 2019 at 4:13 AM Jean-Dominique Frattini
wrote:
>
> Hello,
>
> I am on Debian Linux testing. And after an update (firmware-amd-graphics,
> xserver-xorg-video-amdgup and Mesa), my program often raises this error
> message:
>
> amdgpu: The CS has been cancelled because the context is
Hello,
I am on Debian Linux testing. And after an update (firmware-amd-graphics,
xserver-xorg-video-amdgup and Mesa), my program often raises this error
message:
amdgpu: The CS has been cancelled because the context is lost.
When this message shows up (hundreds of lines are displaying in the con
