ohci_hcd leak ed

[Jonathan Neuschäfer]

On Fri, Aug 19, 2011 at 11:16:18PM +0300, DiP wrote:
> On Fri, 19 Aug 2011 21:42:09 +0200
> Jonathan Neuschäfer <j.neuschaefer at gmx.net> wrote:
> 
> > On Fri, Aug 19, 2011 at 12:53:46AM +0300, DiP wrote:
> > > I found where it is.
> > > 
> > > It seems to appear on my desktop box when I connect cams to the same bus.
> > > Two connectors next to each other.
> > > 
> > > But on the notebook it does matter. Any bus, any port.
> > > 
> > > Problem still alive with a kernel 
> > > 3.0.2-pf-di #1 SMP PREEMPT Fri Aug 19
> > > 00:21:22 EEST 2011 x86_64 Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz
> > > GenuineIntel GNU/Linux
> > 
> > Sounds like a problem worth reporting on the relevant mailing lists. If
> > you have the time and patience, bisecting the (possible) bug may be useful
> > (see http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html).
> > 
> 
> Sorry, can not get what to deal with that bisect. I wonder if you could explain
> me what to do, or point me to the more explanatory articles/wiki etc?

Git bisect is actually quite easy to use. First you have to find a "good"
version (i.e. git commit). A version is good if the bug isn't there.
Then you start the bisection:
$ git bisect start bad-version good-version

Git bisect will check out a version for you to test. Now test this
version and tell git bisect whether you experience the bug or not.
$ git bisect good  # if the bug is there
$ git bisect bad   # if it's not there

Repeat this precess until git bisect good/bad prints a message of the form:

    02f8c6aee8df3cdc935e9bdd4f2d020306035dbe is the first bad commit.
    commit 02f8c6aee8df3cdc935e9bdd4f2d020306035dbe
    Author: Linus Torvalds <torvalds at linux-foundation.org>
    Date:   Thu Jul 21 19:17:23 2011 -0700

        Linux 3.0

    :100644 100644 60d91f7... 6a5bdad... M  Makefile


Hope this helps,
	Jonathan Neuschäfer