[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080520082521.GA19889@xi.wantstofly.org>
Date: Tue, 20 May 2008 10:25:21 +0200
From: Lennert Buytenhek <buytenh@...tstofly.org>
To: David Brownell <david-b@...bell.net>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Alan Stern <stern@...land.harvard.edu>,
Greg Kroah-Hartman <gregkh@...e.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
akpm@...ux-foundation.org, nico@....org
Subject: Re: [Bug #10713] ehci splatter in 2.6.26-rc2
On Mon, May 19, 2008 at 11:13:11PM -0700, David Brownell wrote:
> > A bisect turns up this:
> >
> > 7329e211b987a493cbcfca0e98c60eb108ab42df is first bad commit
> > commit 7329e211b987a493cbcfca0e98c60eb108ab42df
> > Author: Alan Stern <stern@...land.harvard.edu>
> > Date: Thu Apr 3 18:02:56 2008 -0400
> >
> > USB: root hubs don't lie about their number of TTs
> >
> > Currently EHCI root hubs enumerate with a bDeviceProtocol code
> > indicating that they possess a Transaction Translator. However the
> > vast majority of controllers do not...
> >
> > And indeed, reverting this commit from 2.6.26-rc3 makes my system
> > stop oopsing when I plug in the USB-PS/2 adapter (a low speed device),
> > and makes it work again as it did in 2.6.25.
> >
> > Any other info I can provide or tests I can run?
>
> I'm guessing that this has a version of the ARC/TDI/whoever-now-owns-it
> IP, on a PCI bus? But without the integrated TT option?
>
> If this is on a PCI bus, then try removing the ehci-pci.c line added
> by that patch, see if that helps.
No, this is not on a PCI bus -- this is the on-chip EHCI controller
of the Marvell Orion ARM SoC (ehci-orion.c.)
I have honestly no idea whether the IP is in-house or third-party.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists