From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Marc Haber <mh+linux-kernel@zugschlus.de>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"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: Fri, 17 Jun 2016 22:31:25 +0100 [thread overview]
Message-ID: <20160617213125.GA22906@sudip-laptop> (raw)
In-Reply-To: <20160612164756.GB4572@torres.zugschlus.de>
On Sun, Jun 12, 2016 at 06:47:56PM +0200, Marc Haber wrote:
> On Sat, Jun 11, 2016 at 02:55:04PM +0200, Marc Haber wrote:
> > 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.
>
> The kernel panic on boot is caused by bugs in the parport part. I
> worked around these by disabling PARPORT in the kernel configuration.
May I ask which bug in parport are you reffering to? There was a bad
commit in ppdev which caused boot failure and that was reverted.
But in parport??
regards
sudip
next prev parent reply other threads:[~2016-06-17 21:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 19:02 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
2016-06-12 16:47 ` Marc Haber
2016-06-12 20:14 ` Alan Stern
2016-06-17 21:31 ` Sudip Mukherjee [this message]
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=20160617213125.GA22906@sudip-laptop \
--to=sudipm.mukherjee@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mh+linux-kernel@zugschlus.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
all inboxes | Powered by JetHome®