From: David <david@unsolicited.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
linux-media@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dbrownell@users.sourceforge.net, leonidv11@gmail.com,
Greg KH <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: USB/DVB - Old Technotrend TT-connect S-2400 regression tracked down
Date: Sat, 23 May 2009 19:20:14 +0100 [thread overview]
Message-ID: <4A183E5E.1070502@unsolicited.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0905231109140.18397-100000@netrider.rowland.org>
Alan Stern wrote:
> On Sat, 23 May 2009, Pekka Enberg wrote:
>
>
>> On Sat, May 23, 2009 at 12:32 AM, David <david@unsolicited.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@unsolicited.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?
>
Here's all I have. The device is a USB connected Technotrend TT-Connect
S-2400. Support for this was added in kernel 2.6.26. When I came to
upgrade my media PC beyond .26 the dmesg showed the following:-
Media PC (32-bit - Nvidia chipset. kernel 2.6.27)
19:13:18 s kernel: usb 1-3: new high speed USB device using ehci_hcd and
address 6
19:13:18 s kernel: usb 1-3: configuration #1 chosen from 1 choice
19:13:18 s kernel: dvb-usb: found a 'Technotrend TT-connect S-2400' in
cold state, will try to load a firmware
19:13:18 s kernel: firmware: requesting dvb-usb-tt-s2400-01.fw
19:13:18 s kernel: dvb-usb: downloading firmware from file
'dvb-usb-tt-s2400-01.fw'
19:13:18 s kernel: usb 1-3: USB disconnect, address 6
19:13:18 s kernel: dvb-usb: generic DVB-USB module successfully
deinitialized and disconnected.
19:13:20 s kernel: usb 1-3: new high speed USB device using ehci_hcd and
address 7
19:13:20 s kernel: usb 1-3: configuration #1 chosen from 1 choice
19:13:20 s kernel: dvb-usb: found a 'Technotrend TT-connect S-2400' in
warm state.
19:13:20 s kernel: dvb-usb: will pass the complete MPEG2 transport
stream to the software demuxer.
19:13:20 s kernel: DVB: registering new adapter (Technotrend TT-connect
S-2400)
19:13:20 s kernel: DVB: registering frontend 0 (Philips TDA10086 DVB-S)...
19:13:23 s kernel: dvb-usb: recv bulk message failed: -110
19:13:23 s kernel: ttusb2: there might have been an error during control
message transfer. (rlen = 0, was 0)
19:13:23 s kernel: dvb-usb: Technotrend TT-connect S-2400 successfully
initialized and connected.
The device times out. Reverting b963801164618e25fbdc0cd452ce49c3628b46c8
causes it to work again
19:09:53 s kernel: usb 1-3: new high speed USB device using ehci_hcd and
address 5
19:09:53 s kernel: usb 1-3: configuration #1 chosen from 1 choice
19:09:58 s kernel: dvb-usb: found a 'Technotrend TT-connect S-2400' in
cold state, will try to load a firmware
19:09:58 s kernel: firmware: requesting dvb-usb-tt-s2400-01.fw
19:09:59 s kernel: dvb-usb: downloading firmware from file
'dvb-usb-tt-s2400-01.fw'
19:09:59 s kernel: usb 1-3: USB disconnect, address 5
19:09:59 s kernel: dvb-usb: generic DVB-USB module successfully
deinitialized and disconnected.
19:09:59 s kernel: usbcore: registered new interface driver dvb_usb_ttusb2
19:10:00 s kernel: usb 1-3: new high speed USB device using ehci_hcd and
address 6
19:10:00 s kernel: usb 1-3: configuration #1 chosen from 1 choice
19:10:01 s kernel: dvb-usb: found a 'Technotrend TT-connect S-2400' in
warm state.
19:10:01 s kernel: dvb-usb: will pass the complete MPEG2 transport
stream to the software demuxer.
19:10:01 s kernel: DVB: registering new adapter (Technotrend TT-connect
S-2400)
19:10:01 s kernel: DVB: registering frontend 3 (Philips TDA10086 DVB-S)...
19:10:01 s kernel: dvb-usb: Technotrend TT-connect S-2400 successfully
initialized and connected.
My PC (64 bit - ATI chipset, using 2.6.30-rc5)
[12044.364021] usb 4-10: new high speed USB device using ehci_hcd and
address 5
[12044.497561] usb 4-10: configuration #1 chosen from 1 choice
[12044.881621] dvb-usb: found a 'Technotrend TT-connect S-2400' in cold
state, will try to load a firmware
[12044.881626] usb 4-10: firmware: requesting dvb-usb-tt-s2400-01.fw
[12044.918854] dvb-usb: downloading firmware from file
'dvb-usb-tt-s2400-01.fw'
[12044.980719] usbcore: registered new interface driver dvb_usb_ttusb2
[12044.981478] usb 4-10: USB disconnect, address 5
[12044.985169] dvb-usb: generic DVB-USB module successfully
deinitialized and disconnected.
[12046.744023] usb 4-10: new high speed USB device using ehci_hcd and
address 6
[12046.876980] usb 4-10: configuration #1 chosen from 1 choice
[12046.877673] dvb-usb: found a 'Technotrend TT-connect S-2400' in warm
state.
[12046.878601] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[12046.878959] DVB: registering new adapter (Technotrend TT-connect S-2400)
[12046.886861] DVB: registering adapter 0 frontend 0 (Philips TDA10086
DVB-S)...
[12046.891434] LNBx2x attached on addr=8<3>dvb-usb: recv bulk message
failed: -110
[12048.888080] ttusb2: there might have been an error during control
message transfer. (rlen = 0, was 0)
[12048.888320] dvb-usb: Technotrend TT-connect S-2400 successfully
initialized and connected.
Reverting b963801164618e25fbdc0cd452ce49c3628b46c8 (manually, as there
are conflicting changes) causes it to work again. The wierd random
frontend number looks strange though.
[ 2406.492027] usb 2-10: new high speed USB device using ehci_hcd and
address 7
[ 2406.625622] usb 2-10: configuration #1 chosen from 1 choice
[ 2406.626328] dvb-usb: found a 'Technotrend TT-connect S-2400' in cold
state, will try to load a firmware
[ 2406.626335] usb 2-10: firmware: requesting dvb-usb-tt-s2400-01.fw
[ 2406.628650] dvb-usb: downloading firmware from file
'dvb-usb-tt-s2400-01.fw'
[ 2406.690868] usb 2-10: USB disconnect, address 7
[ 2406.693282] dvb-usb: generic DVB-USB module successfully
deinitialized and disconnected.
[ 2408.453024] usb 2-10: new high speed USB device using ehci_hcd and
address 8
[ 2408.585983] usb 2-10: configuration #1 chosen from 1 choice
[ 2408.586652] dvb-usb: found a 'Technotrend TT-connect S-2400' in warm
state.
[ 2408.587727] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[ 2408.588080] DVB: registering new adapter (Technotrend TT-connect S-2400)
[ 2408.591575] DVB: registering adapter 0 frontend 42056112 (Philips
TDA10086 DVB-S)...
[ 2408.595941] LNBx2x attached on addr=8<6>dvb-usb: Technotrend
TT-connect S-2400 successfully initialized and connected.
I'm happy to do any further diagnostics if it will help.
David
next prev parent reply other threads:[~2009-05-23 18:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 21:32 USB/DVB - Old Technotrend TT-connect S-2400 regression tracked down David
2009-05-22 21:45 ` David
2009-05-23 8:25 ` Pekka Enberg
2009-05-23 8:25 ` Pekka Enberg
2009-05-23 15:15 ` Alan Stern
2009-05-23 18:20 ` David [this message]
2009-05-23 19:22 ` David
2009-05-23 21:02 ` Alan Stern
2009-05-24 0:15 ` David
2009-05-24 0:54 ` hermann pitton
2009-05-24 8:35 ` David
2009-05-24 14:33 ` Alan Stern
2009-05-24 15:28 ` David
2009-05-25 2:10 ` Alan Stern
2009-05-25 2:39 ` Pete Zaitcev
2009-05-25 9:00 ` David
2009-05-25 12:25 ` David
2009-05-26 0:48 ` Pete Zaitcev
2009-05-26 14:08 ` Alan Stern
2009-05-26 18:42 ` David
2009-05-26 19:01 ` Pete Zaitcev
2009-05-24 15:16 ` Alan Stern
2009-05-25 15:23 ` Alan Stern
2009-05-25 17:32 ` David
2009-05-25 18:44 ` David
2009-05-25 21:12 ` Alan Stern
2009-05-26 20:57 ` Alan Stern
2009-05-27 18:42 ` David
2009-05-27 20:20 ` Alan Stern
2009-05-27 21:28 ` David
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=4A183E5E.1070502@unsolicited.net \
--to=david@unsolicited.net \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=gregkh@suse.de \
--cc=leonidv11@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.