All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Clifton <pcjc2@cam.ac.uk>
To: Seblu <seblu@seblu.net>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: Fwd: 2.6.36-rc5 i915 regression
Date: Tue, 26 Oct 2010 02:42:56 +0100	[thread overview]
Message-ID: <1288057376.13125.14.camel@pcjc2lap> (raw)
In-Reply-To: <AANLkTikeqF6Uo+sjerhappnmwuu9=Y4qr=+J6f-jdO4s@mail.gmail.com>

On Tue, 2010-10-26 at 02:57 +0200, Seblu wrote:
> I make an another video, which show suspend to ram issue with this
> lastest kernel and how it's perfectly functionnal with 2.6.35.7.
> 
> http://videobin.org/+2a5/2kp.ogg
> 
> can i do something more to help your  troubleshoot this issue?

If you have a working kernel version and a non working version (and some
time on your hands!), you could "git bisect" between the various
revisions to determine which commit introduced the breakage.

(NB: I'm not a driver developer here, just a keen user).

It took me a good long time bisecting a graphics regression when I had
it down to 80 changes. Since in that case I was sure it was a graphics
related fault - and had an idea which of the many driver source files
would be relevant, I was able to pass some extra parameters to git
bisect to narrow the search.

Others might disagree, but from your video I wouldn't be 100% sure that
I could restrict the search to the graphics driver only.

-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)

  reply	other threads:[~2010-10-26  1:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 11:00 2.6.36-rc5 i915 regression Johannes Hirte
2010-10-01 12:28 ` Chris Wilson
2010-10-01 12:28   ` Chris Wilson
2010-10-01 12:55   ` Seblu
2010-10-01 13:22     ` Chris Wilson
2010-10-01 20:27       ` Seblu
2010-10-02  9:07         ` Zhenyu Wang
2010-10-07 23:24           ` Seblu
2010-10-09  9:40             ` Seblu
2010-10-10 13:52               ` Seblu
     [not found]                 ` <AANLkTinTX9hXMV+nn-qQjsGq-_fF8mwGc6p1P_-csJUR@mail.gmail.com>
     [not found]                   ` <89k77n$p72i7f@fmsmga001.fm.intel.com>
2010-10-18 16:38                     ` Fwd: " Seblu
2010-10-25 23:19                     ` Seblu
2010-10-25 23:47                       ` Peter Clifton
2010-10-26  0:57                         ` Seblu
2010-10-26  1:42                           ` Peter Clifton [this message]
2010-10-26  2:13                             ` Seblu
2010-10-26  8:30                       ` Chris Wilson
2010-10-26  8:49                         ` Seblu
2010-10-26  9:25                           ` Chris Wilson
2010-11-02 10:04                           ` Seblu
2010-10-30 20:13                         ` Chun-Yu Shei
2010-10-01 18:15   ` Johannes Hirte
2010-10-01 13:01 ` Seblu

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=1288057376.13125.14.camel@pcjc2lap \
    --to=pcjc2@cam.ac.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=seblu@seblu.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.