dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Norbert Preining <preining@logic.at>
To: Dave Airlie <airlied@gmail.com>
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 09:44:31 +0900	[thread overview]
Message-ID: <20121104004431.GG6196@gamma.logic.tuwien.ac.at> (raw)
In-Reply-To: <CAPM=9tw_0vDcRG25i2ypJEKT+JNqWzkXw2+jg=qj6H5M1hoJXg@mail.gmail.com>

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?

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
SCREEB (n.)
To make the noise of a nylon anorak rubbing against a pair of corduroy
trousers.
			--- Douglas Adams, The Meaning of Liff

  parent reply	other threads:[~2012-11-04  0:44 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 [this message]
2012-11-04  6:08                     ` Dave Airlie
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=20121104004431.GG6196@gamma.logic.tuwien.ac.at \
    --to=preining@logic.at \
    --cc=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 \
    /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).