Jump to content


Photo

Problem with Release 7.2 and Vu+ USB cabletuner.


  • Please log in to reply
51 replies to this topic

#1 yortiz1979

  • Member
  • 18 posts

0
Neutral

Posted 28 December 2019 - 14:46

Hi there is a problem with the VU+ DVB-C usb tuner.

 

I'm using VU+ Zero 4K.

 

when i switch from channels from satellite bouquet  and then switch to Channels from Cable bouquet added by ABM the box crashes.

 

the same happens if you have been zapping channels from satellite and then try to make a search.

 

if you go first to cable and zap from there everything works fine!! the problem comes ones you where zapping on cable and then zapp on satelite and if you switch back to cable after few channels on satelite this carshes.

 

this only happens with while switching from DVB-S to DVB-C if your switch from iptv to cable all work fine.

 

im using OSCAM-emu from the plugin source.

 

i hope this bugs gets fixes or someone point me on the right direction.

 

Im using. Im using latest openpli version 7.2 2019-12-23



Re: Problem with Release 7.2 and Vu+ USB cabletuner. #2 WanWizard

  • PLi® Core member
  • 70,552 posts

+1,813
Excellent

Posted 28 December 2019 - 15:17

If the box crashes, there is a crash log on the box, please post it here, so we know what the problem is.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Problem with Release 7.2 and Vu+ USB cabletuner. #3 mimisiku

  • Senior Member
  • 5,518 posts

+115
Excellent

Posted 28 December 2019 - 15:23

I have never seen this behaviour. I own both the DVB-C/T2 and DVB-S2X variant. I have done a CableScan on mine and used the RemoteStreamConvert option to 'copy' my Satellite bouquets into the DVB-C/T2 box. Furthermore I use OScam to receive the necessary CW's from my RasPi CardServer. Zapping works fine.. No freezes, hickups whatsoever.. I use VTi 14.0.5 as firmware but OpenPli performs exactly the same!
Met één been in het graf..... Helaas

Re: Problem with Release 7.2 and Vu+ USB cabletuner. #4 yortiz1979

  • Member
  • 18 posts

0
Neutral

Posted 28 December 2019 - 16:59

here is the log:

 

 

[eDVBSatelliteEquipmentControl] ret 15000, score old 0
[eDVBSatelliteEquipmentControl] score new 15000
[eDVBSatelliteEquipmentControl] final score 15005
[ActionMap] Keymap 'ChannelSelectBaseActions' -> Action = 'showFavourites'.
[ActionMap] Keymap 'OkCancelActions' -> Action = 'ok'.
[ActionMap] Keymap 'OkCancelActions' -> Action = 'ok'.
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift /media/hdd// statfs failed: No such file or directory
playing 1:0:19:278F:65:F020:FFFF0000:0:0:0:
[eDVBCAService] free slot 0 demux 0 for service 1:0:19:7534:426:1:C00000:0:0:0:
[eDVBCAService] free service 1:0:19:7534:426:1:C00000:0:0:0:
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift /media/hdd// statfs failed: No such file or directory
[eTSMPEGDecoder] decoder state: play, vpid=ffffffff, apid=ffffffff
[eDVBPCR0] DEMUX_STOP ok
[eDVBPCR0] destroy
[eDVBVideo0] DEMUX_STOP  ok
[eDVBVideo0] VIDEO_STOP ok
[eDVBVideo0] destroy
[eDVBAudio0] AUDIO_STOP ok
[eDVBAudio0] DEMUX_STOP ok
[eDVBAudio0] AUDIO_CONTINUE ok
[eDVBAudio0] destroy
cleaning up
TuxTxt cache cleared
[eDVBResourceManager] start release channel timer
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift /media/hdd// statfs failed: No such file or directory
not pauseable.
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift /media/hdd// statfs failed: No such file or directory
not pauseable.
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift /media/hdd// statfs failed: No such file or directory
not pauseable.
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift /media/hdd// statfs failed: No such file or directory
new service started! trying to download cuts!
download failed, no cuesheet interface
RemovePopup, id = ZapError
[eDVBLocalTimerHandler] remove channel 0x2809140
[eEPGCache] remove channel 0x2809140
[eDVBResourceManager] allocate channel.. 0065:f020
[eDVBFrontend1] opening frontend
[gRC] main thread is non-idle! display spinner!


Re: Problem with Release 7.2 and Vu+ USB cabletuner. #5 WanWizard

  • PLi® Core member
  • 70,552 posts

+1,813
Excellent

Posted 28 December 2019 - 17:01

There is no indication of a crash in this log.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Problem with Release 7.2 and Vu+ USB cabletuner. #6 yortiz1979

  • Member
  • 18 posts

0
Neutral

Posted 28 December 2019 - 17:17

There is no indication of a crash in this log

 

here is the process again before it get the spinner and the you need to reboot the console since it does not respond any more!

 

if someone can address me to the right solution this is very enoying!!

 

[gRC] main thread is non-idle! display spinner!
 

 

i have read that if there is a driver problem you wont see the error on the logs, is that true?

 

here the log again since i access the bouquet folder generated by ABM

 

[ActionMap] Keymap 'ChannelSelectBaseActions' -> Action = 'showFavourites'.
[ActionMap] Keymap 'OkCancelActions' -> Action = 'ok'.
[ActionMap] Keymap 'OkCancelActions' -> Action = 'ok'.
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift /media/hdd// statfs failed: No such file or directory
playing 1:0:19:278F:65:F020:FFFF0000:0:0:0:
[eDVBCAService] free slot 0 demux 0 for service 1:0:19:7534:426:1:C00000:0:0:0:
[eDVBCAService] free service 1:0:19:7534:426:1:C00000:0:0:0:
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift /media/hdd// statfs failed: No such file or directory
[eTSMPEGDecoder] decoder state: play, vpid=ffffffff, apid=ffffffff
[eDVBPCR0] DEMUX_STOP ok
[eDVBPCR0] destroy
[eDVBVideo0] DEMUX_STOP  ok
[eDVBVideo0] VIDEO_STOP ok
[eDVBVideo0] destroy
[eDVBAudio0] AUDIO_STOP ok
[eDVBAudio0] DEMUX_STOP ok
[eDVBAudio0] AUDIO_CONTINUE ok
[eDVBAudio0] destroy
cleaning up
TuxTxt cache cleared
[eDVBResourceManager] start release channel timer
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift /media/hdd// statfs failed: No such file or directory
not pauseable.
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift /media/hdd// statfs failed: No such file or directory
not pauseable.
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift /media/hdd// statfs failed: No such file or directory
not pauseable.
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift /media/hdd// statfs failed: No such file or directory
new service started! trying to download cuts!
download failed, no cuesheet interface
RemovePopup, id = ZapError
[eDVBLocalTimerHandler] remove channel 0x2782fe0
[eEPGCache] remove channel 0x2782fe0
[eDVBResourceManager] allocate channel.. 0065:f020
[eDVBFrontend1] opening frontend
[gRC] main thread is non-idle! display spinner!


Re: Problem with Release 7.2 and Vu+ USB cabletuner. #7 WanWizard

  • PLi® Core member
  • 70,552 posts

+1,813
Excellent

Posted 28 December 2019 - 18:14

Displaying a spinner is not a crash. It only means some code is busy longer than it should, blocking the mainloop. Which can be anything.

 

And this is a bit of dmesg output, if it is from a crash log, the first bit, displaying the crash cause, is missing.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Problem with Release 7.2 and Vu+ USB cabletuner. #8 Dimitrij

  • PLi® Core member
  • 10,331 posts

+350
Excellent

Posted 28 December 2019 - 18:21

 

VU+ DVB-C usb tuner

Please answer

 cat /proc/bus/nim_sockets 

 


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: Problem with Release 7.2 and Vu+ USB cabletuner. #9 yortiz1979

  • Member
  • 18 posts

0
Neutral

Posted 28 December 2019 - 18:54

 

 

VU+ DVB-C usb tuner

Please answer

 cat /proc/bus/nim_sockets 

this is what i get

 

NIM Socket 0:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(SI2166)
        Frontend_Device: 0
        I2C_Device: 2
 
NIM Socket 1:
        Type: DVB-C
        Name: Vuplus DVB-T/C USB NIM(TURBO):VTUNER
        Frontend_Device: 1root@vuzero4k:~#
 


Re: Problem with Release 7.2 and Vu+ USB cabletuner. #10 yortiz1979

  • Member
  • 18 posts

0
Neutral

Posted 28 December 2019 - 19:04

Displaying a spinner is not a crash. It only means some code is busy longer than it should, blocking the mainloop. Which can be anything.

 

And this is a bit of dmesg output, if it is from a crash log, the first bit, displaying the crash cause, is missing.

here the logs using dmseg after the system, let me know if this could be of any help. if you need more infor please let me know

 

 
[ 4240.428889] [AUD]: AUDIO_PAUSE 3
[ 4240.432232] [AUD]: AUDIO_PLAY 3 decoder start : 0
[ 4240.444623] [VID]: VIDEO_SELECT_SOURCE 0  0
[ 4240.448956] [VID]: VIDEO_SET_STREAMTYPE 1
[ 4240.453317] [VID]: VIDEO_FREEZE 3  0
[ 4240.457037] [VID]: VIDEO_PLAY 3  5 2
[ 4240.468403] [VID]: VIDEO_SLOWMOTION 0    1
[ 4240.473807] [VID]: VIDEO_FAST_FORWARD 0    1 0
[ 4240.481186] [VID]: VIDEO_CONTINUE 3  1
[ 4240.487616] [AUD]: AUDIO_CONTINUE 3 1 aph=0xccd72800
[ 4240.493964] [AUD]: Mute : 0
[ 4240.501725] [VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
[ 4240.507595] [VID]: VIDEO_GET_SIZE aspect: 1 0
[ 4248.052649] [VID]: VIDEO_STOP 1  1
[ 4248.056559] [AUD]: AUDIO_STOP 0
[ 4248.083333] [AUD]: AUDIO_CONTINUE 3 0 aph=0x0
[ 4248.087711] [AUD]: AUDIO_CONTINUE aph=0 0 0
[ 4248.911102] FE tune
[ 4249.387512] [AUD]: AUDIO_SELECT_SOURCE 0
[ 4249.393331] [AUD]: AUDIO_SET_BYPASS_MODE 0
[ 4249.397564] [AUD]: AC3 downmix 1  state : 1
[ 4249.402402] [AUD]: HDMI Max Audio PCM Channels=6
[ 4249.407346] [AUD]: AUDIO_PAUSE 3
[ 4249.410846] [AUD]: AUDIO_PLAY 3 decoder start : 0
[ 4249.423703] [VID]: VIDEO_SELECT_SOURCE 0  0
[ 4249.428133] [VID]: VIDEO_SET_STREAMTYPE 1
[ 4249.432687] [VID]: VIDEO_FREEZE 3  0
[ 4249.436479] [VID]: VIDEO_PLAY 3  5 2
[ 4249.448132] [VID]: VIDEO_SLOWMOTION 0    1
[ 4249.453908] [VID]: VIDEO_FAST_FORWARD 0    1 0
[ 4249.461075] [VID]: VIDEO_CONTINUE 3  1
[ 4249.467806] [AUD]: AUDIO_CONTINUE 3 1 aph=0xccd72880
[ 4249.474086] [AUD]: Mute : 0
[ 4249.482525] [VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
[ 4249.488418] [VID]: VIDEO_GET_SIZE aspect: 1 0
[DMX]: paserband_remove_pid pid 0x14ac not found
[ 4249.594931]
[ 4266.398546] [VID]: VIDEO_STOP 1  1
[ 4266.402038] [AUD]: AUDIO_STOP 0
[ 4266.429222] [AUD]: AUDIO_CONTINUE 3 0 aph=0x0
[ 4266.433593] [AUD]: AUDIO_CONTINUE aph=0 0 0
[ 4440.051066] INFO: task oscam-emu:1296 blocked for more than 120 seconds.
[ 4440.057833]       Tainted: P           O    4.1.20-1.9 #1
[ 4440.063622] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 4440.071520] oscam-emu       D c05d22c0     0  1296   1260 0x00000000
[ 4440.078644] [<c05d22c0>] (__schedule) from [<c05d2688>] (schedule+0x40/0x98)
[ 4440.085954] [<c05d2688>] (schedule) from [<c05d29fc>] (schedule_preempt_disabled+0xc/0x10)
[ 4440.094532] [<c05d29fc>] (schedule_preempt_disabled) from [<c05d3d94>] (__mutex_lock_slowpath+0x9c/0x150)
[ 4440.104510] [<c05d3d94>] (__mutex_lock_slowpath) from [<c05d3e94>] (mutex_lock+0x4c/0x50)
[ 4440.112748] [<c05d3e94>] (mutex_lock) from [<c045a388>] (dvb_device_open+0x14/0xd8)
[ 4440.120887] [<c045a388>] (dvb_device_open) from [<c00e3cac>] (chrdev_open+0xc4/0x180)
[ 4440.128783] [<c00e3cac>] (chrdev_open) from [<c00de3d0>] (do_dentry_open.constprop.3+0x1f0/0x2f8)
[ 4440.138053] [<c00de3d0>] (do_dentry_open.constprop.3) from [<c00ecae8>] (do_last.constprop.16+0x434/0xc5c)
[ 4440.148051] [<c00ecae8>] (do_last.constprop.16) from [<c00ed38c>] (path_openat+0x7c/0x5d0)
[ 4440.156636] [<c00ed38c>] (path_openat) from [<c00ee420>] (do_filp_open+0x2c/0x88)
[ 4440.164274] [<c00ee420>] (do_filp_open) from [<c00df49c>] (do_sys_open+0x10c/0x1d0)
[ 4440.172236] [<c00df49c>] (do_sys_open) from [<c000ff40>] (ret_fast_syscall+0x0/0x3c)
[ 4440.180165] INFO: task enigma2:10178 blocked for more than 120 seconds.
[ 4440.187059]       Tainted: P           O    4.1.20-1.9 #1
[ 4440.192496] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 4440.200646] enigma2         D c05d22c0     0 10178  10174 0x00000000
[ 4440.207474] [<c05d22c0>] (__schedule) from [<c05d2688>] (schedule+0x40/0x98)
[ 4440.214578] [<c05d2688>] (schedule) from [<c05d4dd0>] (schedule_timeout+0x148/0x188)
[ 4440.222661] [<c05d4dd0>] (schedule_timeout) from [<c05d30ec>] (wait_for_common+0xa8/0x174)
[ 4440.230983] [<c05d30ec>] (wait_for_common) from [<c00402a0>] (kthread_stop+0x60/0x9c)
[ 4440.239206] [<c00402a0>] (kthread_stop) from [<c0463434>] (dvb_frontend_stop+0x60/0xc8)
[ 4440.247264] [<c0463434>] (dvb_frontend_stop) from [<c0463724>] (dvb_frontend_open+0x288/0x3b4)
[ 4440.256217] [<c0463724>] (dvb_frontend_open) from [<c045a40c>] (dvb_device_open+0x98/0xd8)
[ 4440.264605] [<c045a40c>] (dvb_device_open) from [<c00e3cac>] (chrdev_open+0xc4/0x180)
[ 4440.272734] [<c00e3cac>] (chrdev_open) from [<c00de3d0>] (do_dentry_open.constprop.3+0x1f0/0x2f8)
[ 4440.281664] [<c00de3d0>] (do_dentry_open.constprop.3) from [<c00ecae8>] (do_last.constprop.16+0x434/0xc5c)
[ 4440.291725] [<c00ecae8>] (do_last.constprop.16) from [<c00ed38c>] (path_openat+0x7c/0x5d0)
[ 4440.300046] [<c00ed38c>] (path_openat) from [<c00ee420>] (do_filp_open+0x2c/0x88)
[ 4440.308271] [<c00ee420>] (do_filp_open) from [<c00df49c>] (do_sys_open+0x10c/0x1d0)
[ 4440.316001] [<c00df49c>] (do_sys_open) from [<c000ff40>] (ret_fast_syscall+0x0/0x3c)
[ 4440.324244] INFO: task kdvb-ad-1-fe-0:10284 blocked for more than 120 seconds.
[ 4440.331521]       Tainted: P           O    4.1.20-1.9 #1
[ 4440.337320] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 4440.345213] kdvb-ad-1-fe-0  D c05d22c0     0 10284      2 0x00000000
[ 4440.352210] [<c05d22c0>] (__schedule) from [<c05d2688>] (schedule+0x40/0x98)
[ 4440.359346] [<c05d2688>] (schedule) from [<c05d2e64>] (bit_wait+0x34/0x58)
[ 4440.366521] [<c05d2e64>] (bit_wait) from [<c05d2b1c>] (__wait_on_bit+0x7c/0xb0)
[ 4440.374022] [<c05d2b1c>] (__wait_on_bit) from [<c05d2bc4>] (out_of_line_wait_on_bit+0x74/0x7c)
[ 4440.382939] [<c05d2bc4>] (out_of_line_wait_on_bit) from [<bf000e64>] (dvb_usb_fe_sleep+0x108/0x1b4 [dvb_usb_v2])
[ 4440.393271] [<bf000e64>] (dvb_usb_fe_sleep [dvb_usb_v2]) from [<c0462f98>] (dvb_frontend_thread+0x260/0x69c)
[ 4440.403396] [<c0462f98>] (dvb_frontend_thread) from [<c003ff14>] (kthread+0xdc/0xf4)
[ 4440.411273] [<c003ff14>] (kthread) from [<c000ffe8>] (ret_from_fork+0x14/0x2c)
[ 4560.418076] INFO: task oscam-emu:1296 blocked for more than 120 seconds.
[ 4560.425080]       Tainted: P           O    4.1.20-1.9 #1
[ 4560.430534] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 4560.438763] oscam-emu       D c05d22c0     0  1296   1260 0x00000000
[ 4560.445552] [<c05d22c0>] (__schedule) from [<c05d2688>] (schedule+0x40/0x98)
[ 4560.452658] [<c05d2688>] (schedule) from [<c05d29fc>] (schedule_preempt_disabled+0xc/0x10)
[ 4560.461314] [<c05d29fc>] (schedule_preempt_disabled) from [<c05d3d94>] (__mutex_lock_slowpath+0x9c/0x150)
[ 4560.471339] [<c05d3d94>] (__mutex_lock_slowpath) from [<c05d3e94>] (mutex_lock+0x4c/0x50)
[ 4560.479585] [<c05d3e94>] (mutex_lock) from [<c045a388>] (dvb_device_open+0x14/0xd8)
[ 4560.487664] [<c045a388>] (dvb_device_open) from [<c00e3cac>] (chrdev_open+0xc4/0x180)
[ 4560.495550] [<c00e3cac>] (chrdev_open) from [<c00de3d0>] (do_dentry_open.constprop.3+0x1f0/0x2f8)
[ 4560.505068] [<c00de3d0>] (do_dentry_open.constprop.3) from [<c00ecae8>] (do_last.constprop.16+0x434/0xc5c)
[ 4560.514917] [<c00ecae8>] (do_last.constprop.16) from [<c00ed38c>] (path_openat+0x7c/0x5d0)
[ 4560.523788] [<c00ed38c>] (path_openat) from [<c00ee420>] (do_filp_open+0x2c/0x88)
[ 4560.531331] [<c00ee420>] (do_filp_open) from [<c00df49c>] (do_sys_open+0x10c/0x1d0)
[ 4560.539490] [<c00df49c>] (do_sys_open) from [<c000ff40>] (ret_fast_syscall+0x0/0x3c)
[ 4560.547631] INFO: task enigma2:10178 blocked for more than 120 seconds.
[ 4560.554609]       Tainted: P           O    4.1.20-1.9 #1
[ 4560.560073] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 4560.568185] enigma2         D c05d22c0     0 10178  10174 0x00000000
[ 4560.574925] [<c05d22c0>] (__schedule) from [<c05d2688>] (schedule+0x40/0x98)
[ 4560.582341] [<c05d2688>] (schedule) from [<c05d4dd0>] (schedule_timeout+0x148/0x188)
[ 4560.590138] [<c05d4dd0>] (schedule_timeout) from [<c05d30ec>] (wait_for_common+0xa8/0x174)
[ 4560.598738] [<c05d30ec>] (wait_for_common) from [<c00402a0>] (kthread_stop+0x60/0x9c)
[ 4560.606703] [<c00402a0>] (kthread_stop) from [<c0463434>] (dvb_frontend_stop+0x60/0xc8)
[ 4560.615030] [<c0463434>] (dvb_frontend_stop) from [<c0463724>] (dvb_frontend_open+0x288/0x3b4)
[ 4560.623777] [<c0463724>] (dvb_frontend_open) from [<c045a40c>] (dvb_device_open+0x98/0xd8)
[ 4560.632384] [<c045a40c>] (dvb_device_open) from [<c00e3cac>] (chrdev_open+0xc4/0x180)
[ 4560.640348] [<c00e3cac>] (chrdev_open) from [<c00de3d0>] (do_dentry_open.constprop.3+0x1f0/0x2f8)
[ 4560.649531] [<c00de3d0>] (do_dentry_open.constprop.3) from [<c00ecae8>] (do_last.constprop.16+0x434/0xc5c)
[ 4560.659305] [<c00ecae8>] (do_last.constprop.16) from [<c00ed38c>] (path_openat+0x7c/0x5d0)
[ 4560.668227] [<c00ed38c>] (path_openat) from [<c00ee420>] (do_filp_open+0x2c/0x88)
[ 4560.675845] [<c00ee420>] (do_filp_open) from [<c00df49c>] (do_sys_open+0x10c/0x1d0)
[ 4560.684228] [<c00df49c>] (do_sys_open) from [<c000ff40>] (ret_fast_syscall+0x0/0x3c)
[ 4560.692033] INFO: task kdvb-ad-1-fe-0:10284 blocked for more than 120 seconds.
[ 4560.699766]       Tainted: P           O    4.1.20-1.9 #1
[ 4560.705217] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 4560.713362] kdvb-ad-1-fe-0  D c05d22c0     0 10284      2 0x00000000
[ 4560.720112] [<c05d22c0>] (__schedule) from [<c05d2688>] (schedule+0x40/0x98)
[ 4560.727454] [<c05d2688>] (schedule) from [<c05d2e64>] (bit_wait+0x34/0x58)
[ 4560.734483] [<c05d2e64>] (bit_wait) from [<c05d2b1c>] (__wait_on_bit+0x7c/0xb0)
[ 4560.742107] [<c05d2b1c>] (__wait_on_bit) from [<c05d2bc4>] (out_of_line_wait_on_bit+0x74/0x7c)
[ 4560.750862] [<c05d2bc4>] (out_of_line_wait_on_bit) from [<bf000e64>] (dvb_usb_fe_sleep+0x108/0x1b4 [dvb_usb_v2])
[ 4560.761339] [<bf000e64>] (dvb_usb_fe_sleep [dvb_usb_v2]) from [<c0462f98>] (dvb_frontend_thread+0x260/0x69c)
[ 4560.771584] [<c0462f98>] (dvb_frontend_thread) from [<c003ff14>] (kthread+0xdc/0xf4)
[ 4560.779723] [<c003ff14>] (kthread) from [<c000ffe8>] (ret_from_fork+0x14/0x2c)


Re: Problem with Release 7.2 and Vu+ USB cabletuner. #11 WanWizard

  • PLi® Core member
  • 70,552 posts

+1,813
Excellent

Posted 28 December 2019 - 19:11

That doesn't look particularly healthy, but I don't really see the relation between this and a zap...


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Problem with Release 7.2 and Vu+ USB cabletuner. #12 yortiz1979

  • Member
  • 18 posts

0
Neutral

Posted 28 December 2019 - 19:25

That doesn't look particularly healthy, but I don't really see the relation between this and a zap...

what can you recommend me to do?



Re: Problem with Release 7.2 and Vu+ USB cabletuner. #13 WanWizard

  • PLi® Core member
  • 70,552 posts

+1,813
Excellent

Posted 28 December 2019 - 19:34

I don't know, this is above my limited skill set...


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Problem with Release 7.2 and Vu+ USB cabletuner. #14 Dimitrij

  • PLi® Core member
  • 10,331 posts

+350
Excellent

Posted 28 December 2019 - 20:45

First you need to check on another image(VTI,openATV).


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: Problem with Release 7.2 and Vu+ USB cabletuner. #15 Dimitrij

  • PLi® Core member
  • 10,331 posts

+350
Excellent

Posted 28 December 2019 - 21:08

To understand this is the problem of drivers or image.


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: Problem with Release 7.2 and Vu+ USB cabletuner. #16 yortiz1979

  • Member
  • 18 posts

0
Neutral

Posted 29 December 2019 - 01:16

To understand this is the problem of drivers or image.

i will give  try on openvix or openatv



Re: Problem with Release 7.2 and Vu+ USB cabletuner. #17 Abu Baniaz

  • PLi® Contributor
  • 2,501 posts

+64
Good

Posted 29 December 2019 - 02:07

Please attach crash logs instead of pasting contents. The posts have maximum size. Most people who read logs prefer to use a text editor to find terms too.



Re: Problem with Release 7.2 and Vu+ USB cabletuner. #18 Abu Baniaz

  • PLi® Contributor
  • 2,501 posts

+64
Good

Posted 29 December 2019 - 02:15

He might have the same issue with Vix as their code is very similar to PLI. Might be better trying ATV

https://www.world-of-satellite.com/showthread.php?48426-VU-USB-Turbo-Tuner-Problem
https://www.world-of-satellite.com/showthread.php?57740-VU-Turbo-Tuner-Freeze

Edited by Abu Baniaz, 29 December 2019 - 02:15.


Re: Problem with Release 7.2 and Vu+ USB cabletuner. #19 yortiz1979

  • Member
  • 18 posts

0
Neutral

Posted 29 December 2019 - 02:53

To understand this is the problem of drivers or image.

i can confirm is not a driver option,it works wthout any problem on openvix latest option, so is a problem with openpli!!



Re: Problem with Release 7.2 and Vu+ USB cabletuner. #20 yortiz1979

  • Member
  • 18 posts

0
Neutral

Posted 29 December 2019 - 04:01

Please attach crash logs instead of pasting contents. The posts have maximum size. Most people who read logs prefer to use a text editor to find terms too.

hi abu since is not a crash but a spiner there is no crash file. i can still init 6 from ssh when the box hangs. i read both link you shared but nothing. i have test two fresh openpli option 6.2 and 7.2 and both crash. i tested on openvix and it works fine wihout any problem. i can sithc as much as i can from iptv to cable and no issue,the minute i hit a channle from saelite, no matter if i come back to iptv, if i hit after that a cable channel the box freeze and i get the spinner. i alos tried changing the skin on openpli, nothing. this is very enoying :( please help!!!




17 user(s) are reading this topic

0 members, 17 guests, 0 anonymous users