Hi Dave,
So here's my atomic series, finally all debugged&reviewed. Sean Paul has
done a full detailed pass over it all, and a lot of other people have
commented and provided feedback on some parts. Rob Clark also converted
msm over the w/e and seems happy. The only small thing is that Rob wants
t
Hi Glenn,
First of all, evergreen_cs_track_check only has to be called for the
packets that execute a draw call. It's useless to call it for
INDEX_BASE, INDEX_BUFFER_SIZE, and SET_BASE.
There has never been index buffer bounds checking in the CS checker
and this patch doesn't change that, so no a
https://bugzilla.kernel.org/show_bug.cgi?id=85421
--- Comment #11 from Hin-Tak Leung ---
This time I don't have firefox running. Just a few terminals and qemu/kvm. The
gcc testsuite inside the vm is demanding enough I didn't want to run anything
else.
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=85421
--- Comment #10 from Hin-Tak Leung ---
Created attachment 157061
--> https://bugzilla.kernel.org/attachment.cgi?id=157061&action=edit
whole dmesg from vt with 3.16.6 when it crashed.
This time it crashed while I was running just a few terminals
Hi,
A have a desktop and a laptop with Haswell and on both I'm experiencing
this issue: after a time of continuous usage (days usually) I run into
this warning:
Nov 9 01:24:38 xyz kernel: [ cut here ]
Nov 9 01:24:38 xyz kernel: WARNING: CPU: 2 PID: 10769 at
drivers/gpu/
On Sun, 09 Nov 2014 00:15:49 +0100, Jerome Glisse
wrote:
> On Sat, Nov 08, 2014 at 11:51:30PM +0100, Glenn Kennard wrote:
>> Signed-off-by: Glenn Kennard
>
> NAK insecure. This is missing any kind of boundary checking for the
> indirect buffer and thus can be abuse.
The indirect command buffe
e:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141109/808a9554/attachment-0001.html>
