From: Dave Airlie <airlied@gmail.com>
To: Norbert Preining <preining@logic.at>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: drm i915 hangs on heavy io load
Date: Sun, 4 Nov 2012 16:08:47 +1000 [thread overview]
Message-ID: <CAPM=9txgXLHQPCP4egU57P0=pACmKZnAzwgj6fNxR5-4nwOF6A@mail.gmail.com> (raw)
In-Reply-To: <20121104004431.GG6196@gamma.logic.tuwien.ac.at>
On Sun, Nov 4, 2012 at 10:44 AM, Norbert Preining <preining@logic.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.
next prev parent reply other threads:[~2012-11-04 6:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121023053830.GA30776@gamma.logic.tuwien.ac.at>
2012-10-23 6:56 ` drm i915 hangs on heavy io load Dave Airlie
2012-10-23 6:56 ` Dave Airlie
2012-10-23 9:17 ` Chris Wilson
[not found] ` <CAPM=9txr4TzuG-BbL0bXeEK6AzkOK9pH0kh-nP=Njv53sgFZew@mail.gmail.com>
2012-10-23 7:24 ` Norbert Preining
2012-10-24 0:36 ` Norbert Preining
2012-10-24 8:11 ` Chris Wilson
2012-10-28 2:47 ` Norbert Preining
2012-10-28 11:10 ` Chris Wilson
2012-10-28 12:32 ` Norbert Preining
2012-10-29 7:17 ` Tino Keitel
2012-10-30 0:49 ` Norbert Preining
2012-10-30 0:55 ` Dave Airlie
2012-10-30 1:01 ` Norbert Preining
2012-10-30 1:37 ` Ben Widawsky
2012-10-30 3:13 ` Norbert Preining
2012-11-04 0:44 ` Norbert Preining
2012-11-04 6:08 ` Dave Airlie [this message]
2012-11-05 0:33 ` Norbert Preining
2012-11-05 20:29 ` [bisected] " Lekensteyn
2012-10-30 0:39 ` Norbert Preining
2012-10-30 10:02 ` Chris Wilson
2012-10-23 5:38 Norbert Preining
-- strict thread matches above, loose matches on Subject: below --
2012-10-23 5:38 Norbert Preining
2012-10-23 5:38 Norbert Preining
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPM=9txgXLHQPCP4egU57P0=pACmKZnAzwgj6fNxR5-4nwOF6A@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).