From: Ed Tomlinson <edt@aei.ca>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: Oliver Neukum <oneukum@suse.de>,
linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [BUG] usb problems in .38-rc3+
Date: Tue, 8 Feb 2011 23:31:26 -0500 [thread overview]
Message-ID: <201102082331.27644.edt@aei.ca> (raw)
In-Reply-To: <AANLkTinpKwe2vWH3=Ur+N76a6KyfuFp0V-EznXXS7m+p@mail.gmail.com>
On Tuesday 08 February 2011 01:46:16 Gadiyar, Anand wrote:
> On Tue, Feb 8, 2011 at 7:45 AM, Ed Tomlinson <edt@aei.ca> wrote:
> > I tried bisecting without much luck. It started with about 4000 commits to check. It was still bad
> > when it reached the first 1000 commits post .37. Then all boots started crashing. I think its possible
> > to restrict a bisect to a directory - if so, what dir should I try?
> >
>
> Maybe drivers/ or drivers/usb would be enough for a first attempt?
> I usually start there.
>
> You could just do:
>
> git bisect start -- [path]
>
> to restrict bisection to commits that touch [path].
This is as far as I can get:
# bad: [100b33c8bd8a3235fd0b7948338d6cbb3db3c63d] Linux 2.6.38-rc4
# good: [3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5] Linux 2.6.37
# good: [387c31c7e5c9805b0aef8833d1731a5fe7bdea14] Linux 2.6.37-rc8
# good: [90a8a73c06cc32b609a880d48449d7083327e11a] Linux 2.6.37-rc7
# good: [c8ddb2713c624f432fa5fe3c7ecffcdda46ea0d4] Linux 2.6.37-rc1
git bisect start 'v2.6.38-rc4' 'v2.6.37' 'v2.6.37-rc8' 'v2.6.37-rc7' 'v2.6.37-rc1' '--' 'drivers/usb' 'drivers/bluetooth'
# good: [5cdc5bd8b2b1190cb54548c03194b154b4892e2a] Merge branch 'musb-hw' of git://gitorious.org/usb/usb into musb
git bisect good 5cdc5bd8b2b1190cb54548c03194b154b4892e2a
# bad: [f2c565e223af39ed38be5c84b1a37b591b22db83] xHCI: replace dev_dbg() with xhci_dbg()
git bisect bad f2c565e223af39ed38be5c84b1a37b591b22db83
# good: [2af10844eb6ed104f9505bf3a7ba3ceb02264f31] USB: Merge 2.6.37-rc5 into usb-next
git bisect good 2af10844eb6ed104f9505bf3a7ba3ceb02264f31
# bad: [3e5b08cbbf78bedd316904ab0cf3b27119433ee5] Merge branch 'usb-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6
git bisect bad 3e5b08cbbf78bedd316904ab0cf3b27119433ee5
# good: [1051b9f0f9eab8091fe3bf98320741adf36b4cfa] Merge branch 'for-rmk' of git://git.pengutronix.de/git/imx/linux-2.6 into devel-stable
git bisect good 1051b9f0f9eab8091fe3bf98320741adf36b4cfa
After this the kernel does not build.
Any clues?
Ed
next prev parent reply other threads:[~2011-02-09 4:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 19:17 [BUG] usb problems in .38-rc3+ Ed Tomlinson
2011-02-05 20:16 ` Alan Stern
2011-02-05 22:50 ` Przemo Firszt
2011-02-06 4:27 ` Ed Tomlinson
2011-02-07 9:09 ` Oliver Neukum
2011-02-08 0:20 ` Ed Tomlinson
2011-02-08 2:15 ` Ed Tomlinson
2011-02-08 6:46 ` Gadiyar, Anand
2011-02-09 4:31 ` Ed Tomlinson [this message]
2011-02-09 6:17 ` Anand Gadiyar
2011-02-09 23:48 ` Ed Tomlinson
2011-02-12 14:38 ` Ed Tomlinson
2011-02-16 14:00 ` Gustavo F. Padovan
2011-02-16 18:38 ` Ed Tomlinson
2011-02-16 18:47 ` Gustavo F. Padovan
[not found] ` <201102201209.20799.edt@aei.ca>
2011-02-20 20:49 ` Ed Tomlinson
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=201102082331.27644.edt@aei.ca \
--to=edt@aei.ca \
--cc=gadiyar@ti.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).