From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752056AbcFKMzJ (ORCPT ); Sat, 11 Jun 2016 08:55:09 -0400 Received: from torres.zugschlus.de ([85.214.131.164]:54134 "EHLO torres.zugschlus.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751395AbcFKMzH (ORCPT ); Sat, 11 Jun 2016 08:55:07 -0400 Date: Sat, 11 Jun 2016 14:55:04 +0200 From: Marc Haber To: Greg KH Cc: "linux-kernel@vger.kernel.org" , linux-usb@vger.kernel.org Subject: Re: USB broken on Banana Pi in Linux 4.6 Message-ID: <20160611125504.GA4572@torres.zugschlus.de> References: <20160530190250.GA26198@torres.zugschlus.de> <20160530204712.GA9225@kroah.com> <20160603065358.GA12054@torres.zugschlus.de> <20160603153511.GA28326@kroah.com> <20160607170600.GA22014@torres.zugschlus.de> <20160607173017.GA25514@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20160607173017.GA25514@kroah.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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