On Fri, Jul 31, 2015 at 04:11:21PM +0200, Krzysztof Kolasa wrote:
> On 22.07.2015 10:27, Daniel Vetter wrote:
> > On Tue, Jul 21, 2015 at 08:07:47PM +0200, Krzysztof Kolasa wrote:
> >> On 21.07.2015 16:03, Daniel Vetter wrote:
> >>> On Tue, Jul 21, 2015 at 02:48:21PM +0200, Krzysztof Kolasa wrote:
On 22.07.2015 10:27, Daniel Vetter wrote:
> On Tue, Jul 21, 2015 at 08:07:47PM +0200, Krzysztof Kolasa wrote:
>> On 21.07.2015 16:03, Daniel Vetter wrote:
>>> On Tue, Jul 21, 2015 at 02:48:21PM +0200, Krzysztof Kolasa wrote:
On 21.07.2015 11:43, Chris Wilson wrote:
> On Tue, Jul 21, 2015 a
On 22.07.2015 10:27, Daniel Vetter wrote:
> On Tue, Jul 21, 2015 at 08:07:47PM +0200, Krzysztof Kolasa wrote:
>> On 21.07.2015 16:03, Daniel Vetter wrote:
>>> On Tue, Jul 21, 2015 at 02:48:21PM +0200, Krzysztof Kolasa wrote:
On 21.07.2015 11:43, Chris Wilson wrote:
> On Tue, Jul 21, 2015 a
On Tue, Jul 21, 2015 at 08:07:47PM +0200, Krzysztof Kolasa wrote:
> On 21.07.2015 16:03, Daniel Vetter wrote:
> > On Tue, Jul 21, 2015 at 02:48:21PM +0200, Krzysztof Kolasa wrote:
> >> On 21.07.2015 11:43, Chris Wilson wrote:
> >>> On Tue, Jul 21, 2015 at 11:07:20AM +0200, Daniel Vetter wrote:
> >>
On 21.07.2015 16:03, Daniel Vetter wrote:
> On Tue, Jul 21, 2015 at 02:48:21PM +0200, Krzysztof Kolasa wrote:
>> On 21.07.2015 11:43, Chris Wilson wrote:
>>> On Tue, Jul 21, 2015 at 11:07:20AM +0200, Daniel Vetter wrote:
On Tue, Jul 21, 2015 at 10:58:50AM +0200, Krzysztof Kolasa wrote:
> O
On Tue, Jul 21, 2015 at 02:48:21PM +0200, Krzysztof Kolasa wrote:
> On 21.07.2015 11:43, Chris Wilson wrote:
> > On Tue, Jul 21, 2015 at 11:07:20AM +0200, Daniel Vetter wrote:
> >> On Tue, Jul 21, 2015 at 10:58:50AM +0200, Krzysztof Kolasa wrote:
> >>> On 21.07.2015 10:41, Daniel Vetter wrote:
> >>
On 21.07.2015 11:43, Chris Wilson wrote:
> On Tue, Jul 21, 2015 at 11:07:20AM +0200, Daniel Vetter wrote:
>> On Tue, Jul 21, 2015 at 10:58:50AM +0200, Krzysztof Kolasa wrote:
>>> On 21.07.2015 10:41, Daniel Vetter wrote:
I meant whether you can reset the bad commit and it's immediate parent
>>
On Tue, Jul 21, 2015 at 11:07:20AM +0200, Daniel Vetter wrote:
> On Tue, Jul 21, 2015 at 10:58:50AM +0200, Krzysztof Kolasa wrote:
> > On 21.07.2015 10:41, Daniel Vetter wrote:
> > > I meant whether you can reset the bad commit and it's immediate parent
> > > extensively to make sure the bisect is
On Tue, Jul 21, 2015 at 10:58:50AM +0200, Krzysztof Kolasa wrote:
> On 21.07.2015 10:41, Daniel Vetter wrote:
> > I meant whether you can reset the bad commit and it's immediate parent
> > extensively to make sure the bisect is really correct. gpu's occasionally
> > take a while to hang themselves,
On 21.07.2015 10:41, Daniel Vetter wrote:
> I meant whether you can reset the bad commit and it's immediate parent
> extensively to make sure the bisect is really correct. gpu's occasionally
> take a while to hang themselves, so could be that the bisect was
> mislead somewhere.
Again I will bisec
On Sun, Jul 19, 2015 at 08:07:19PM +0200, Krzysztof Kolasa wrote:
> Photo laptop screen:
>
> https://drive.google.com/open?id=0B1LAMAFWTdeweTJycjFoZkNSVmM
>
> bisected first bad commit: [0875546c5318c85c13d07014af5350e9000bc9e9]
> drm/i915: Fix up the vma aliasing ppgtt binding
Are you sure abo
Photo laptop screen:
https://drive.google.com/open?id=0B1LAMAFWTdeweTJycjFoZkNSVmM
bisected first bad commit: [0875546c5318c85c13d07014af5350e9000bc9e9] drm/i915:
Fix up the vma aliasing ppgtt binding
crash dump /sys/class/drm/card0/error :
GPU HANG: ecode 3:0:0x0063ffe6, in Xorg [1221], reaso
12 matches
Mail list logo