[Mesa-dev] [PATCH] intel: Give an explanation why we are exiting for debugging.

2011-09-04 Thread Eugeni Dodonov
This could happen in 3 different cases, and ERRNO can explain what happened. First case would be EIO (gpu hang), second EINVAL (something is wrong inside the batch), and we also discovered that sometimes it happens with ENOSPACE. All of those cases are different it it could be worth to at least kno

Re: [Mesa-dev] [PATCH] intel: Give an explanation why we are exiting for debugging.

2011-09-02 Thread Eugeni Dodonov
On Fri, Sep 2, 2011 at 15:53, Eric Anholt wrote: > On Fri, 2 Sep 2011 12:33:44 -0300, Eugeni Dodonov > wrote: > > From: Eugeni Dodonov > > > > This could happen in 3 different cases, and ERRNO can explain what > > happened. First case would be EIO (gpu hang), second EINVAL (something is > > wr

Re: [Mesa-dev] [PATCH] intel: Give an explanation why we are exiting for debugging.

2011-09-02 Thread Eric Anholt
On Fri, 2 Sep 2011 12:33:44 -0300, Eugeni Dodonov wrote: > From: Eugeni Dodonov > > This could happen in 3 different cases, and ERRNO can explain what > happened. First case would be EIO (gpu hang), second EINVAL (something is > wrong inside the batch), and we also discovered that sometimes it

[Mesa-dev] [PATCH] intel: Give an explanation why we are exiting for debugging.

2011-09-02 Thread Eugeni Dodonov
From: Eugeni Dodonov This could happen in 3 different cases, and ERRNO can explain what happened. First case would be EIO (gpu hang), second EINVAL (something is wrong inside the batch), and we also discovered that sometimes it happens with ENOSPACE. All of those cases are different it it could b