From: Marc Haber <mh+linux-kernel@zugschlus.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: USB broken on Banana Pi in Linux 4.6
Date: Sat, 11 Jun 2016 14:55:04 +0200 [thread overview]
Message-ID: <20160611125504.GA4572@torres.zugschlus.de> (raw)
In-Reply-To: <20160607173017.GA25514@kroah.com>
On Tue, Jun 07, 2016 at 10:30:17AM -0700, Greg KH wrote:
> Nothing obvious, can you use 'git bisect' to go from 4.5.0 to 4.6.0 to
> find the offending commit?
I can. The first round of bisecting let me end up with
c8b710b3e4348119924051551b836c94835331b1 as the first bad commit,
which is wrong, since c8b710b3e4348119924051551b836c94835331b1^ is bad
as well. I am not sure whether things went well since I had to use git
bisect skip twice because the resulting kernel wouldn't boot on the pi.
A second round of bisecting left me in limbo, since I do not
understand this:
[45/544]mh@fan[zgchroot kernel64][debian_chroot sid_kernel64]:~/linux/debug/linux$ git bisect reset
HEAD is now at 2dcd0af... Linux 4.6
[46/545]mh@fan[zgchroot kernel64][debian_chroot sid_kernel64]:~/linux/debug/linux$ git bisect start
[47/546]mh@fan[zgchroot kernel64][debian_chroot sid_kernel64]:~/linux/debug/linux$ git bisect bad
[48/547]mh@fan[zgchroot kernel64][debian_chroot sid_kernel64]:~/linux/debug/linux$ git bisect bad c8b710b3e4348119924051551b836c94835331b1^
[49/548]mh@fan[zgchroot kernel64][debian_chroot sid_kernel64]:~/linux/debug/linux$ git bisect good v4.5
Some good revs are not ancestor of the bad rev.
git bisect cannot work properly in this case.
Maybe you mistook good and bad revs?
[50/549]mh@fan[zgchroot kernel64][debian_chroot sid_kernel64]:~/linux/debug/linux$
Do I need to start over completely?
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
next prev parent reply other threads:[~2016-06-11 12:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 19:02 USB broken on Banana Pi in Linux 4.6 Marc Haber
2016-05-30 20:47 ` Greg KH
2016-06-03 6:53 ` Marc Haber
2016-06-03 15:35 ` Greg KH
2016-06-07 17:06 ` Marc Haber
2016-06-07 17:30 ` Greg KH
2016-06-11 12:55 ` Marc Haber [this message]
2016-06-12 16:47 ` Marc Haber
2016-06-12 20:14 ` Alan Stern
2016-06-17 21:31 ` Sudip Mukherjee
2016-06-14 8:45 ` USB broken on Banana Pi in Linux 4.6 [solved] Marc Haber
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=20160611125504.GA4572@torres.zugschlus.de \
--to=mh+linux-kernel@zugschlus.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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.