Bug #1578
USB-Tuner: dvb-usb: bulk message failed: -110 (5/0)
0%
Description
Hello,
I'm not quite sure, whether this can be a bug in tvheadend, but as I don't know what to do anymore, I would you like to have a look at this issue.
I use tvheadend with three usb dvb-s2 tuners (TT-connect S2-4600). This setup works quite well, though I get thoses errors every three till five days (!). It's somehow like it gets triggered when tunening to a new channel. It looks like this:
dvb-usb: bulk message failed: -110 (5/0)
dw2102: i2c transfer failed.
and sometimes
dw2102: i2c transfer failed.
dvb-usb: bulk message failed: -110 (4/0)
in dmesg. I googled a lot, initially this happend nearly every day. I changed the usb cables and played a bit with the ports, its an x64 system with intel chipset and 4GB RAM. I even upgraded my debian to 3.7.3 kernel and removed all unnecessary drivers and modules. On the server only samba, apache, tvheadend and oscam are running. Even though it seems to happen more often if the cpu load is high, it also happend while nearly idleing. Tvheadend becomes totally unresponsive and has to be killed. Unloading and reloading dvb-modules doesn't help, so I need a cold reboot to get the tuner running again, which is quite annoying. And because it's always another tuner of those three who fails, I don't think they have a hardware problem. Temperature is no issue and they are external powered.
I use this driver as it is recommed by the manufacturer: https://bitbucket.org/liplianin/s2-liplianin-v37
The driver is also build at minimal config, only needed modules. There are two firmwares available, both seem to behave the same.
Tvheadend gets new build from git every week (+/-), last update is two hours ago. At least I found a way to provoke this failure more reliable: heavy skipping in a recording played via pvr.hts (xbmc). It only took 30 secs. and tvheadend was gone with one of the tuners.
Is it possible, that there is a timing issue? That the tuner waits under some circumstances to long for a command and stops working? Can you please have another look at the code in charge?
I'm quite happy with this config and still think this is the best thing I ever spend so much time with, but with this issue I can't get a "production" environment.
Thanks in advance...
History
Updated by Patrick Vorlicek almost 12 years ago
Updated by dvb related dmesg at boot
[ 4.899183] WARNING: You are using an experimental version of the media stack.
[ 4.899183] As the driver is backported to an older kernel, it doesn't offer
[ 4.899183] enough quality for its usage in production.
[ 4.899183] Use it with care.
[ 4.899183] Latest git patches (needed if you report a bug to [email protected]):
[ 4.899183] aeebb1b3146a70bf02d0115a2be690d856d12e8c [media] pvrusb2: For querystd, start with list of hardware-supported standards
[ 4.899183] c0bb609fdc0b842799d5108aec7fae13b0fd32cd [media] pvrusb2: Get rid of obsolete code for video standard enumeration
[ 4.899183] 598e978aadd39e24749e0da5a6cff568570b1d00 [media] pvrusb2: Trivial tweak to get rid of some redundant dereferences
[ 4.903733] WARNING: You are using an experimental version of the media stack.
[ 4.903733] As the driver is backported to an older kernel, it doesn't offer
[ 4.903733] enough quality for its usage in production.
[ 4.903733] Use it with care.
[ 4.903733] Latest git patches (needed if you report a bug to [email protected]):
[ 4.903733] aeebb1b3146a70bf02d0115a2be690d856d12e8c [media] pvrusb2: For querystd, start with list of hardware-supported standards
[ 4.903733] c0bb609fdc0b842799d5108aec7fae13b0fd32cd [media] pvrusb2: Get rid of obsolete code for video standard enumeration
[ 4.903733] 598e978aadd39e24749e0da5a6cff568570b1d00 [media] pvrusb2: Trivial tweak to get rid of some redundant dereferences
[ 4.911630] dw2102: su3000_identify_state
[ 4.911630]
[ 4.911638] dvb-usb: found a 'TT Connect S2 4600' in warm state.
[ 4.911648] dw2102: su3000_power_ctrl: 1, initialized 0
[ 4.911648]
[ 4.911857] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 4.912053] DVB: registering new adapter (TT Connect S2 4600)
[ 4.913045] bc 00 00 00 00 00
[ 4.913906] bc ea 00 00 00 00
[ 4.914655] bc ea 2b 00 00 00
[ 4.915729] bc ea 2b 46 00 00
[ 4.916532] bc ea 2b 46 00 00
[ 4.917295] bc ea 2b 46 00 8d
[ 4.917309] dvb-usb: MAC address: bc:ea:2b:46:00:8d
[ 5.221693] DVB: Unable to find symbol ds3000_attach()
[ 5.229005] Chip ID = [DS3103]!
[ 5.229012] DS3103 chip version: 0.208 attached.
[ 5.244257] dw2102: Attached DS3103/TS2022!
[ 5.244257]
[ 5.244270] DVB: registering adapter 0 frontend 0 (Montage Technology DS3103/TS2022)...
[ 5.244641] dw2102: su3000_power_ctrl: 0, initialized 1
[ 5.244641]
[ 5.244651] dvb-usb: TT Connect S2 4600 successfully initialized and connected.
[ 5.244722] dw2102: su3000_identify_state
[ 5.244722]
[ 5.244729] dvb-usb: found a 'TT Connect S2 4600' in warm state.
[ 5.244753] dw2102: su3000_power_ctrl: 1, initialized 0
[ 5.244753]
[ 5.244904] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.245105] DVB: registering new adapter (TT Connect S2 4600)
[ 5.245800] bc 00 00 00 00 00
[ 5.246520] bc ea 00 00 00 00
[ 5.247233] bc ea 2b 00 00 00
[ 5.247918] bc ea 2b 46 00 00
[ 5.248604] bc ea 2b 46 00 00
[ 5.249288] bc ea 2b 46 00 96
[ 5.249297] dvb-usb: MAC address: bc:ea:2b:46:00:96
[ 5.553120] DVB: Unable to find symbol ds3000_attach()
[ 5.555405] Chip ID = [DS3103]!
[ 5.555412] DS3103 chip version: 0.208 attached.
[ 5.563942] dw2102: Attached DS3103/TS2022!
[ 5.563942]
[ 5.563951] DVB: registering adapter 1 frontend 0 (Montage Technology DS3103/TS2022)...
[ 5.564342] dw2102: su3000_power_ctrl: 0, initialized 1
[ 5.564342]
[ 5.564350] dvb-usb: TT Connect S2 4600 successfully initialized and connected.
[ 5.564410] dw2102: su3000_identify_state
[ 5.564410]
[ 5.564417] dvb-usb: found a 'TT Connect S2 4600' in warm state.
[ 5.564433] dw2102: su3000_power_ctrl: 1, initialized 0
[ 5.564433]
[ 5.564568] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.564727] DVB: registering new adapter (TT Connect S2 4600)
[ 5.565408] bc 00 00 00 00 00
[ 5.566112] bc ea 00 00 00 00
[ 5.566819] bc ea 2b 00 00 00
[ 5.567496] bc ea 2b 46 00 00
[ 5.568174] bc ea 2b 46 04 00
[ 5.568850] bc ea 2b 46 04 86
[ 5.568859] dvb-usb: MAC address: bc:ea:2b:46:04:86
[ 5.873151] DVB: Unable to find symbol ds3000_attach()
[ 5.875446] Chip ID = [DS3103]!
[ 5.875453] DS3103 chip version: 0.208 attached.
[ 5.883947] dw2102: Attached DS3103/TS2022!
[ 5.883947]
[ 5.883956] DVB: registering adapter 2 frontend 0 (Montage Technology DS3103/TS2022)...
[ 5.884334] dw2102: su3000_power_ctrl: 0, initialized 1
[ 5.884334]
[ 5.884340] dvb-usb: TT Connect S2 4600 successfully initialized and connected.
[ 5.884394] usbcore: registered new interface driver dw2102
[ 34.466014] dw2102: su3000_power_ctrl: 1, initialized 1
[ 34.466014]
[ 34.476374] ds3103_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3103.fw)...
[ 34.479631] ds3103_firmware_ondemand: Waiting for firmware upload(2)...
[ 35.791322] dw2102: su3000_power_ctrl: 1, initialized 1
[ 35.791322]
[ 36.006804] ts2022_set_params: offset 357khz
[ 36.006810] ts2022_set_params: 1704500khz 1704857khz
[ 37.790864] dvb-usb: recv bulk message failed: -110
[ 37.790923] dw2102: i2c transfer failed.
[ 37.800178] ds3103_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3103.fw)...
[ 37.800255] ds3103_firmware_ondemand: Waiting for firmware upload(2)...
[ 39.078477] dw2102: su3000_power_ctrl: 1, initialized 1
[ 39.078477]
[ 39.262801] ts2022_set_params: offset -286khz
[ 39.262807] ts2022_set_params: 1587500khz 1587214khz
[ 41.074853] dvb-usb: recv bulk message failed: -110
[ 41.074910] dw2102: i2c transfer failed.
[ 41.084169] ds3103_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3103.fw)...
[ 41.084259] ds3103_firmware_ondemand: Waiting for firmware upload(2)...
Updated by Adam Sutton almost 12 years ago
Updated by - Status changed from New to Need feedback
This looks like a firmware issue to me. If the firmware is complaining this much that is almost certainly the cause. There are known (and already tracked) problems with how tvheadend handles misbehaving adapters (i.e. USB ones that have been unplugged or failed), most likely this is related to that.
If you can provide some TVH debug logs that might help, though not sure. Really need the ability to replicate it and I don't have any USB tuners to test on.
Adam
Updated by Patrick Vorlicek almost 12 years ago
Anything you want. What should I do? How do I configure debuging?
Updated by Patrick Vorlicek almost 12 years ago
So, it seems definetly a problem with how tvheadend handles the tuner. I tested with MythTV and had no issues so far - but I really want to use tvheadend. I noticed, that since timeshift was added - although I doesn't have it activated - it happends more often. What do I have to do, that you can nail down the source of this issue?
Updated by Adam Sutton almost 12 years ago
We need a debug log before we can do anything. Run with -d to output debug to console or -s to syslog.
Also out of interest, see what happens if you enable close fds when idle and idle scan, see if it recovers at all when you switch channel. Maybe also try disabling pmt monitoring.
You say.it works in myth, do you see any glitches?
Adam
Updated by Adam Sutton over 11 years ago
- Status changed from Need feedback to Rejected
No update in 2 months, another I2C related error has been submitted (related?). CLosing this one.
Adam