http://www.orbit-lab.org/kernel/compat-wireless-2.6/2008/04/

http://www.orbit-lab.org/kernel/compat-wireless-2.6/2008/04/

[Grant Williamson]

Hi,

I am trying to narrow down a wireless issue I am having with leap on 
Fedora 9. Seems that in April the issue was fixed in the 
compat-wireless-2.6 tarball.

On http://www.orbit-lab.org/kernel/compat-wireless-2.6/2008/04/ most of 
the archives for April are missing. Is there any
other mirror where I can find or checkout the archives between 20080407 
& 20080420?

I need to track it down so the issue can get fixed on el5.

Re: http://www.orbit-lab.org/kernel/compat-wireless-2.6/2008/04/

[Pavel Roskin]

On Tue, 2008-06-10 at 14:57 -0400, Grant Williamson wrote:
> Hi,
> 
> I am trying to narrow down a wireless issue I am having with leap on 
> Fedora 9. Seems that in April the issue was fixed in the 
> compat-wireless-2.6 tarball.
> 
> On http://www.orbit-lab.org/kernel/compat-wireless-2.6/2008/04/ most of 
> the archives for April are missing. Is there any
> other mirror where I can find or checkout the archives between 20080407 
> & 20080420?
> 
> I need to track it down so the issue can get fixed on el5.

The snapshots are not suitable for bisecting bugs.  Even a single day
can bring dozens of updates.

This right tool for bisection is git.  Please check out the wireless
tree:

git-clone git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git

Then compile the kernel.  See if the problem exists.  You need to use
reverse logic, since you are looking for a patch that fixed something,
not a patch that broke it.

Thus, if the problem is fixed, mark the revision as "bad" with
"git-bisect bad".  Then find a revision that is likely to have the
problem.  Use "git-tag -l" or an interactive tool, such as qgit or tig.
Check it out with "git-checkout".  Test the kernel.  Mark is with
"git-bisect bad" or "git-bisect good" using the same reversed logic.

Once you find one "good" and one "bad" revision, git-bisect will be
telling you what to test next, and a few tests later, you'll have the
exact change you are looking for.

You can also check logs for the problem or describe it here in case
somebody knows which patch fixed it.

-- 
Regards,
Pavel Roskin