All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: David Brownell <david-b@pacbell.net>,
	linux-usb-devel@lists.sourceforge.net,
	Alan Stern <stern@rowland.harvard.edu>,
	linux-kernel@vger.kernel.org, Tino Keitel <tino.keitel@gmx.de>
Subject: Re: [linux-usb-devel] possible USB regression with 2.6.21-rc4: iPod doesn't work
Date: Fri, 23 Mar 2007 17:27:09 +0100	[thread overview]
Message-ID: <20070323162709.GK752@stusta.de> (raw)
In-Reply-To: <20070322214653.GA6889@dose.home.local>

On Thu, Mar 22, 2007 at 10:46:53PM +0100, Tino Keitel wrote:
> On Thu, Mar 22, 2007 at 14:29:11 -0700, David Brownell wrote:
> > On Thursday 22 March 2007 12:54 pm, Tino Keitel wrote:
> > > On Thu, Mar 22, 2007 at 15:40:40 -0400, Alan Stern wrote:
> > > > 	  _Something_ is generating those overcurrent 
> > > > warnings, and it sure looks like a hardware malfunction.
> > > 
> > > But it works with 2.6.20.
> > 
> > So can you bisect to find what caused the problem?
> 
> I never did use git-bisect, but maybe I find the time next week.


Instructions for bisecting:


<--  snip  -->

# install git and cogito on your computer

# clone Linus' tree:
cg-clone \ 
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

# start bisecting:
cd linux-2.6
git bisect start
git bisect bad v2.6.21-rc4
git bisect good v2.6.20

# start round
cp /path/to/.config .
make oldconfig
make
# install kernel, check whether it's good or bad, then:
git bisect [bad|good]
# start next round


After at about 12 reboots, you'll have found the guilty commit
("...  is first bad commit").


More information on git bisecting:
  man git-bisect

<--  snip  -->


> Regards,
> Tino

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-03-23 16:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 20:47 possible USB regression with 2.6.21-rc4: iPod doesn't work Tino Keitel
2007-03-22  8:50 ` [linux-usb-devel] " Oliver Neukum
2007-03-22  8:54   ` Tino Keitel
2007-03-22 19:40     ` Alan Stern
2007-03-22 19:54       ` Tino Keitel
2007-03-22 21:29         ` David Brownell
2007-03-22 21:46           ` Tino Keitel
2007-03-23 16:27             ` Adrian Bunk [this message]
2007-03-22 21:56           ` Chuck Ebbert
2007-03-22 23:20             ` Pete Zaitcev
2007-03-22 19:17   ` [linux-usb-devel] " Tino Keitel
2007-03-22 19:42     ` Oliver Neukum
2007-03-25 16:53       ` Tino Keitel
2007-03-26 18:12         ` Alan Stern
2007-03-26 18:59           ` Tino Keitel
2007-03-26 20:28             ` Alan Stern
2007-03-26 20:47               ` Tino Keitel
2007-03-26 21:15                 ` Alan Stern
2007-03-26 21:26                   ` Tino Keitel
2007-03-26 22:21                     ` Tino Keitel
2007-03-26 22:33                       ` Tino Keitel
2007-03-27 17:01                         ` Alan Stern
2007-03-26 21:31                   ` Tino Keitel
2007-03-29 13:44                     ` Bill Davidsen

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=20070323162709.GK752@stusta.de \
    --to=bunk@stusta.de \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    --cc=tino.keitel@gmx.de \
    /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.