Kernel Bug Tracker – Bug 33092
[regression] 2.6.39-rc1 - Beagleboard usbnet broken
Last modified: 2011-05-14 21:59:37 UTC
Subject : [regression] 2.6.39-rc1 - Beagleboard usbnet broken
Submitter : Mark Jackson <firstname.lastname@example.org>
Date : 2011-04-04 9:22
Message-ID : 4D998DC9.email@example.com
References : http://marc.info/?l=linux-kernel&m=130191386508831&w=2
This entry is being used for tracking a regression from 2.6.38. Please don't
close it until the problem is fixed in the mainline.
Author: Jamie Iles <firstname.lastname@example.org>
Date: Fri Jan 21 14:11:52 2011 +0000
dmaengine/dw_dmac: don't scan descriptors if no xfers in progress
Signed-off-by: Jamie Iles <email@example.com>
Signed-off-by: Dan Williams <firstname.lastname@example.org>
First-Bad-Commit : 087809fce28f50098d9c3ef1a6865c722f23afd2
A comment I found last night (I can't find it now) linked this bug to this thread about the regulator driver being broken:
In my testing (-rc4+), it looks like the regulator problem is indeed preventing the USB Ethernet port and the hub that it's attached to from being powered up.
Keshava Munegowda indicated that he would be working on this during the week of April 17, 2011.
On Friday, May 06, 2011, Mark Jackson wrote:
> On 30/04/11 20:46, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > The following bug entry is on the current list of known regressions
> > from 2.6.38. Please verify if it still should be listed and let the tracking team
> > know (either way).
> I have just tried the latest linus git and it is still broken.
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=33092
> > Subject : [regression] 2.6.39-rc1 - Beagleboard usbnet broken
> > Submitter : Mark Jackson <email@example.com>
> > Date : 2011-04-04 9:22 (27 days old)
Ok, I'm not really getting the whole discussion, but it seems the issue is fixed.. at least somewhere.
There seem to be 2 fixes for this issue:
And the patch by Munegowda as mentioned here:
Mark, can you confirm that the patch https://lkml.org/lkml/2011/4/14/45 fixes the issue for you?
I can confirm that the patch at https://lkml.org/lkml/2011/4/14/45 *does* fix
Fixed by commit 557f447f21621de9c5447c8702c33b53279822ce .