[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPM=9txgXLHQPCP4egU57P0=pACmKZnAzwgj6fNxR5-4nwOF6A@mail.gmail.com>
Date: Sun, 4 Nov 2012 16:08:47 +1000
From: Dave Airlie <airlied@...il.com>
To: Norbert Preining <preining@...ic.at>
Cc: Chris Wilson <chris@...is-wilson.co.uk>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Daniel Vetter <daniel.vetter@...ll.ch>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>
Subject: Re: drm i915 hangs on heavy io load
On Sun, Nov 4, 2012 at 10:44 AM, Norbert Preining <preining@...ic.at> wrote:
> Hi all,
>
> On Di, 30 Okt 2012, Dave Airlie wrote:
>> I would suggest starting a bisect on drivers/gpu/drm/i915 from 3.6
>> final to 3.7-rc1 or maybe -rc2.
>
> Sorry for my ignorance ... I did on master branch
> $ git checkout v3.7-rc1
> ...
> $ git bisect start drivers/gpu/drm/i915
> $ git bisect bad
> $ git bisect good v3.6
> Bisecting: 121 revisions left to test after this (roughly 7 steps)
> [25c5b2665fe4cc5a93edd29b62e7c05c15dddd26] drm/i915: implement new set_mode code flow
> $
> after that I am back somewhere around
> 3.6.0-rc2
> ???
>
> Am I doing something wrong? I thought I am bisecting between 3.6 and 3.7.-rc2?
> How can I go back to 3.6.0-rc2?
Yeah thats fine, bisecting works by going to where commits were
originally committed, so drm-intel-next was 3.6.0-rc2 at some point
was only merged into Linus later.
Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists