linux-kernel - Re: USB/DVB - Old Technotrend TT-connect S-2400 regression tracked down

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.0905231109140.18397-100000@netrider.rowland.org>
Date:	Sat, 23 May 2009 11:15:16 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Pekka Enberg <penberg@...helsinki.fi>
cc:	David <david@...olicited.net>, <linux-media@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	<dbrownell@...rs.sourceforge.net>, <leonidv11@...il.com>,
	Greg KH <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: USB/DVB - Old Technotrend TT-connect S-2400 regression tracked
  down

On Sat, 23 May 2009, Pekka Enberg wrote:

> On Sat, May 23, 2009 at 12:32 AM, David <david@...olicited.net> wrote:
> > I reported this DVB-S card breaking between 2.6.26 and 2.6.27. I've
> > finally had time to do some digging, and the regression is caused by:
> >
> >    b963801164618e25fbdc0cd452ce49c3628b46c8 USB: ehci-hcd unlink speedups
> >
> > ..that was introduced in 2.6.27. Reverting this change in 2.6.29-rc5
> > makes the card work happily again.
> 
> [ Note: David meant 2.6.30-rc5 here. ]
> 
> Thanks for doing the bisect!
> 
> On Sat, May 23, 2009 at 12:32 AM, David <david@...olicited.net> wrote:
> > I don't know enough about USB protocols to speculate on whether there
> > may be a better fix, but hopefully someone cleverer than me can get to
> > the bottom of the problem?

It's hard to see how that patch could cause any problems, provided the
hardware is working correctly.  (There was a case where the hardware
was _not_ working as expected.)  Is any more information available
about this failure?

Alan Stern

--
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/