On 21 October 2016 at 12:26, Dan Kegel wrote:
> On Thu, Oct 20, 2016 at 6:49 PM, Dave Airlie wrote:
>> If piglit crashes or explodes it's the driver's fault.
>
> Are you quite sure? There could be bugs in piglit, no?
It would most likely crash on all drivers then. It's unlikely that piglit
tes
On Thu, Oct 20, 2016 at 6:49 PM, Dave Airlie wrote:
> If piglit crashes or explodes it's the driver's fault.
Are you quite sure? There could be bugs in piglit, no?
> But really you don't debug piglit tests without access to the source
> code of the driver, and for that you need to be nvidia.
On 21 October 2016 at 05:56, Dan Kegel wrote:
> I guess the underlying question is "how much work would it
> be to get piglit to the point where errors it reports when
> run against nvidia's proprietary drivers are actual problems in those
> drivers".
> I suspect it'd be a good summer project.
I
I guess the underlying question is "how much work would it
be to get piglit to the point where errors it reports when
run against nvidia's proprietary drivers are actual problems in those drivers".
I suspect it'd be a good summer project.
On Thu, Oct 20, 2016 at 12:39 PM, Ilia Mirkin wrote:
> On
On Thu, Oct 20, 2016 at 3:27 PM, Dan Kegel wrote:
> Hi folks,
> a few piglit tests seem to leave a little noise in dmesg when run on
> nvidia proprietary drivers.
> Is this expected?
>
> 1)
>
> dmesg output:
> texsubimage[27980]: segfault at 20e0d20 ip 7fc0492ce5d5 sp
> 7ffc97347800 error
Hi folks,
a few piglit tests seem to leave a little noise in dmesg when run on
nvidia proprietary drivers.
Is this expected?
1)
dmesg output:
texsubimage[27980]: segfault at 20e0d20 ip 7fc0492ce5d5 sp
7ffc97347800 error 4 in
libnvidia-glcore.so.370.28[7fc0481ad000+13bd000]
reproducers:
p
