mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Daniel Goller <morfic@gmail.com>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@linux.intel.com>
Subject: Re: staging/et131x Driver Transmits but does not Receive Packets
Date: Mon, 11 Jan 2010 00:17:45 +0000	[thread overview]
Message-ID: <20100111001745.21d28340@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <13bb8ce11001101156g3cd88a6bn7c6ce657850ab534@mail.gmail.com>

> I will gladly provide any further info you require to look into this.
> 
> Thank you in advance for your time,

There are a huge series of small patches applied to the driver so the
first step to finding which one broke your card is to find which release
or rc it breaks upon and then to narrow down to which patch.

The easiest way if you don't mind a lot of building is to use the git
tree and git bisect.

The basic idea is to pull a kernel git tree (so that it has all the
patches and meta data) then do

git-bisect reset		# Starting a new bisect
git-bisect start
git-bisect good v2.6.31-rc1	# Or whatever you know worked (later
				# the better)

git-bisect bad v2.6.32-rc3	# Earliest you know is broken (or miss
				# version for 'current')


It'll then generate a tree half way between the two

Then build a kernel and test it. If it works

git-bisect good

If not 

git-bisect bad

and it'll pick another spot half way between the two until it pins down
the offender.

If you get one that won't build/fails for some other reason you can 
git-bisect skip

to bump on one

It'll quite rapidly pin down the offending change if you've got a
repeatable bug.


  reply	other threads:[~2010-01-11  0:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-10 19:56 Daniel Goller
2010-01-11  0:17 ` Alan Cox [this message]
2010-01-11  1:30   ` Daniel Goller
2010-01-11  4:40     ` Daniel Goller
2010-01-11 10:26       ` Alan Cox
2010-01-11 16:58         ` Daniel Goller
2010-01-11 10:19     ` Alan Cox

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=20100111001745.21d28340@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=alan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morfic@gmail.com \
    /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

all inboxes | Powered by JetHome®