I've just tried to upgrade my media server to the latest stable kernel
and have found problems with my USB DVB devices. With the new kernel
I'm seeing
DVB: registering new adapter (Technotrend TT-connect S-2400)
DVB: registering frontend 3 (Philips TDA10086 DVB-S)...
dvb-usb: recv bulk message failed: -110
ttusb2: there might have been an error during control message transfer.
(rlen = 0, was 0)
dvb-usb: Technotrend TT-connect S-2400 successfully initialized and
connected.
All of the registered DVB devices are now inoperable. dmesgs from both
kernels attached. There are subtle differences in the device numbering
as the devices were in warm state on the second kernel boot (however the
problem is still present whether the devices are warm or cold).
Any help will be appreciated
Cheers
David
(cc [email protected])
On Fri, 14 Nov 2008 20:20:40 +0000 David <[email protected]> wrote:
> I've just tried to upgrade my media server to the latest stable kernel
> and have found problems with my USB DVB devices. With the new kernel
> I'm seeing
>
> DVB: registering new adapter (Technotrend TT-connect S-2400)
> DVB: registering frontend 3 (Philips TDA10086 DVB-S)...
> dvb-usb: recv bulk message failed: -110
> ttusb2: there might have been an error during control message transfer.
> (rlen = 0, was 0)
> dvb-usb: Technotrend TT-connect S-2400 successfully initialized and
> connected.
>
> All of the registered DVB devices are now inoperable. dmesgs from both
> kernels attached. There are subtle differences in the device numbering
> as the devices were in warm state on the second kernel boot (however the
> problem is still present whether the devices are warm or cold).
>
> Any help will be appreciated
>
Andrew Morton wrote:
> (cc [email protected])
>
> On Fri, 14 Nov 2008 20:20:40 +0000 David <[email protected]> wrote:
>
>
>> I've just tried to upgrade my media server to the latest stable kernel
>> and have found problems with my USB DVB devices. With the new kernel
>> I'm seeing
>>
>> DVB: registering new adapter (Technotrend TT-connect S-2400)
>> DVB: registering frontend 3 (Philips TDA10086 DVB-S)...
>> dvb-usb: recv bulk message failed: -110
>> ttusb2: there might have been an error during control message transfer.
>> (rlen = 0, was 0)
>> dvb-usb: Technotrend TT-connect S-2400 successfully initialized and
>> connected.
>>
>>
As another data point, I've just reproduced this on an x86-64 machine
with just a single S-2400 using 2.6.28-rc5. The reply message seems to
timeout.
[ 99.425530] usb 1-8: new high speed USB device using ehci_hcd and
address 5
[ 99.556976] usb 1-8: configuration #1 chosen from 1 choice
[ 99.764105] dvb-usb: found a 'Technotrend TT-connect S-2400' in cold
state, will try to load a firmware
[ 99.764112] usb 1-8: firmware: requesting dvb-usb-tt-s2400-01.fw
[ 99.810325] dvb-usb: downloading firmware from file
'dvb-usb-tt-s2400-01.fw'
[ 99.872835] usbcore: registered new interface driver dvb_usb_ttusb2
[ 99.880036] usb 1-8: USB disconnect, address 5
[ 99.884293] dvb-usb: generic DVB-USB module successfully
deinitialized and disconnected.
[ 101.637183] usb 1-8: new high speed USB device using ehci_hcd and
address 6
[ 101.770402] usb 1-8: configuration #1 chosen from 1 choice
[ 101.770870] dvb-usb: found a 'Technotrend TT-connect S-2400' in warm
state.
[ 101.771390] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[ 101.771522] DVB: registering new adapter (Technotrend TT-connect S-2400)
[ 101.784993] DVB: registering adapter 0 frontend 0 (Philips TDA10086
DVB-S)...
[ 103.788068] dvb-usb: recv bulk message failed: -110
[ 103.788074] ttusb2: there might have been an error during control
message transfer. (rlen = 0, was 0)
[ 103.788312] dvb-usb: Technotrend TT-connect S-2400 successfully
initialized and connected.
Cheers
David