NextPVR Forums

Full Version: Device Afatech stop working after few mins
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Hi all,

I just discovered NextPVR and I'm impressed but unfortunately I can't make it work properly with my DVB-T device.

I have an Ubuntu Box 18.04.4 and the following usb dongle :

Bus 002 Device 002: ID 048d:9006 Integrated Technology Express, Inc. IT9135 BDA Afatech DVB-T HDTV Dongle

Install went smoothly and I cand find all channels I need, however everything  stop working after a couple of mins which make it unusable.

I can see live channels from dvb-t  but after switching 4-5 channels the device get stuck with either :

- Starting Device wait
- Receiving data

Same thing happens with web browser or Kodi plugin, no matter the channel.
If I restart the computer everything works fine for another five minutes :-)

I tried also the docker version but I have exactly the same behavior.

Not sure if it's some compatibility issue with my usb dongle or something else.
Before Nextpvr I had no problem with mythtv or dvblink.

Is there anything I can do to make it work?
Logs are not very useful.

Thanks
Andrea
(2020-04-25, 10:46 AM)agarbato Wrote: [ -> ]Is there anything I can do to make it work?
Logs are not very useful.

The logs is the best way to diagnose problems ...

What happens if you record a 30 minute show?
Yes is is not clear if the issue is time or channel switching which is why we need logs.

Martin
Thanks for your answers.

This is what happens when everything stop working.

This is a working flow..

020-04-25 15:34:48.611 [DEBUG][20] about to start stream...
2020-04-25 15:34:48.611 [DEBUG][20] StartStream(7247:Canale5 HD)
2020-04-25 15:34:48.611 [DEBUG][20] checking if previous capture source can be reused
2020-04-25 15:34:48.611 [DEBUG][20] checking if previous capture source can be reused
2020-04-25 15:34:48.611 [DEBUG][20] About to change frequencies...will stop existing handles
2020-04-25 15:34:48.611 [DEBUG][20] http://localhost:39303/stream/start?slip...-3571-7.ts
2020-04-25 15:34:49.208 [DEBUG][21] InitiateTranscode@exit
2020-04-25 15:34:49.208 [DEBUG][21] {"stat":"ok"}

After switching channels a couple of times that's what I get on the logs.
Starting Devices on every channel.
The only things that works is a reboot or restart the service (sometimes).

2020-04-25 15:34:49.209 [DEBUG][21] [FFMPEG]: ffmpeg version 3.4.6-0ubuntu0.18.04.1 Copyright © 2000-2019 the FFmpeg developers
2020-04-25 15:34:49.209 [DEBUG][21] [FFMPEG]: built with gcc 7 (Ubuntu 7.3.0-16ubuntu3)
2020-04-25 15:34:49.209 [DEBUG][21] [FFMPEG]: configuration: --prefix=/usr --extra-version=0ubuntu0.18.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared
2020-04-25 15:34:49.210 [DEBUG][21] [FFMPEG]: libavutil 55. 78.100 / 55. 78.100
2020-04-25 15:34:49.210 [DEBUG][21] [FFMPEG]: libavcodec 57.107.100 / 57.107.100
2020-04-25 15:34:49.210 [DEBUG][21] [FFMPEG]: libavformat 57. 83.100 / 57. 83.100
2020-04-25 15:34:49.210 [DEBUG][21] [FFMPEG]: libavdevice 57. 10.100 / 57. 10.100
2020-04-25 15:34:49.210 [DEBUG][21] [FFMPEG]: libavfilter 6.107.100 / 6.107.100
2020-04-25 15:34:49.210 [DEBUG][21] [FFMPEG]: libavresample 3. 7. 0 / 3. 7. 0
2020-04-25 15:34:49.210 [DEBUG][21] [FFMPEG]: libswscale 4. 8.100 / 4. 8.100
2020-04-25 15:34:49.210 [DEBUG][21] [FFMPEG]: libswresample 2. 9.100 / 2. 9.100
2020-04-25 15:34:49.210 [DEBUG][21] [FFMPEG]: libpostproc 54. 7.100 / 54. 7.100
2020-04-25 15:34:50.397 [DEBUG][18] Got request [::ffff:192.168.11.102]: /services/service (channel.transcode.status)
2020-04-25 15:34:50.397 [DEBUG][18] method=channel.transcode.status
2020-04-25 15:34:50.397 [DEBUG][18] parameters:
2020-04-25 15:34:50.397 [DEBUG][18] method: channel.transcode.status
2020-04-25 15:34:50.397 [DEBUG][18] format: json
2020-04-25 15:34:50.397 [DEBUG][18] client_ip: ::ffff:192.168.11.102
2020-04-25 15:34:50.397 [DEBUG][18] user_agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.92 Safari/537.36
2020-04-25 15:34:50.397 [DEBUG][18] host_callback: nuc:8866
2020-04-25 15:34:50.397 [DEBUG][18] sid: default
2020-04-25 15:34:50.397 [DEBUG][18] GetStatus() got transcoder
2020-04-25 15:34:50.397 [DEBUG][18] GetStatus()@2
2020-04-25 15:34:50.397 [DEBUG][18] GetStatus()@3
2020-04-25 15:34:50.397 [DEBUG][18] GetStatus()@exit
2020-04-25 15:34:50.397 [DEBUG][18] {"status": "Starting Device. Please Wait...","final": false,"speed": 0,"duration": 0,"percentage": 0}
2020-04-25 15:34:50.897 [DEBUG][18] Got request [::ffff:192.168.11.102]: /services/service (channel.transcode.status)

I guess this also found on dmesg is somehow related..

[sab apr 25 14:46:22 2020] random: 7 urandom warning(s) missed due to ratelimiting
[sab apr 25 15:32:29 2020] INFO: task kdvb-ad-0-fe-0:3398 blocked for more than 120 seconds.
[sab apr 25 15:32:29 2020] Not tainted 4.15.0-96-generic #97-Ubuntu
[sab apr 25 15:32:29 2020] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[sab apr 25 15:32:29 2020] kdvb-ad-0-fe-0 D 0 3398 2 0x80000000
[sab apr 25 15:32:29 2020] Call Trace:
[sab apr 25 15:32:29 2020] __schedule+0x24e/0x880
[sab apr 25 15:32:29 2020] ? i2c_transfer+0x76/0xf0
[sab apr 25 15:32:29 2020] ? atomic_t_wait+0x60/0x60
[sab apr 25 15:32:29 2020] schedule+0x2c/0x80
[sab apr 25 15:32:29 2020] bit_wait+0x11/0x60
[sab apr 25 15:32:29 2020] __wait_on_bit+0x4c/0x90
[sab apr 25 15:32:29 2020] out_of_line_wait_on_bit+0x90/0xb0
[sab apr 25 15:32:29 2020] ? bit_waitqueue+0x40/0x40
[sab apr 25 15:32:29 2020] dvb_usb_fe_sleep+0x158/0x1a0 [dvb_usb_v2]
[sab apr 25 15:32:29 2020] ? it913x_sleep+0x1b8/0x1d0 [it913x]
[sab apr 25 15:32:29 2020] dvb_frontend_thread+0x294/0x6f0 [dvb_core]
[sab apr 25 15:32:29 2020] ? wait_woken+0x80/0x80
[sab apr 25 15:32:29 2020] kthread+0x121/0x140
[sab apr 25 15:32:29 2020] ? dvb_frontend_swzigzag+0x3d0/0x3d0 [dvb_core]
[sab apr 25 15:32:29 2020] ? kthread_create_worker_on_cpu+0x70/0x70
[sab apr 25 15:32:29 2020] ret_from_fork+0x35/0x40
[sab apr 25 15:38:31 2020] INFO: task kdvb-ad-0-fe-0:3620 blocked for more than 120 seconds.
[sab apr 25 15:38:31 2020] Not tainted 4.15.0-96-generic #97-Ubuntu
[sab apr 25 15:38:31 2020] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

If you need any other info I'm happy to share it :-)

Thanks again
Log snippets are no good we need the zipped logs. Those usb errors don't look good though it seems that it is not working before that snippet.

Martin
Logs attached.

Just to let you know I updated to ubuntu 20.04.

Same behavior,  works for a few mins then stuck on Starting Device or Receiving Data.

Thanks
(2020-04-25, 03:03 PM)agarbato Wrote: [ -> ]Logs attached.

Just to let you know I updated to ubuntu 20.04.

Same behavior,  works for a few mins then stuck on Starting Device or Receiving Data.

Thanks

No logs are attached. You have to click twice.
Logs are here sorry :-)
(2020-04-25, 03:05 PM)BrettB Wrote: [ -> ]
(2020-04-25, 03:03 PM)agarbato Wrote: [ -> ]Logs attached.

Just to let you know I updated to ubuntu 20.04.

Same behavior,  works for a few mins then stuck on Starting Device or Receiving Data.

Thanks

No logs are attached. You have to click twice.
So it was tuning fine but it failed on one channel

16:55:40:782 [INFO] Tuning: 514000000 Hz
16:55:40:782 [ERROR] dvb_fe_set_parms failed
16:55:40:782 [INFO] Creating writer for: LIVE&/home/andrea/recordings/live-Rai Premium-1010-14.ts (live mode)

Does that match a time that dmesg gives you a USB error?

Martin
Pages: 1 2