VU+Solo + VTI 4.1 - Crash in Main menu

    Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

    • VU+Solo + VTI 4.1 - Crash in Main menu

      Hello
      I just installed the latest VTI 4.1, and i experiment crashes when i'm going in Main Menu...
      I notified this problem also with ViX-2.3.153 and with Blackhole 1.7.0...
      With old version of VTI (4.0 and before) and ViX-2.3.133-vusolo and before, it was no problems...

      Description of the problem : when i go to menu, the box is freezing, can't exit menu, can't connect to telnet, or to webif, and the only way to restart is to unplug power...

      Any help please ?

      Thanks

      Ced

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von fced ()

    • RE: VU+Solo + VTI 4.1 - Crash in Main menu

      Re-
      After some hour, the box crashed again, i was viewing a channel, and freeze...
      The sound stay a while after the image freeze...
      After some minutes (3-4), the vusolo have rebooted alone (without intervention from me)

      Any help please ?

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von fced ()

    • RE: VU+Solo + VTI 4.1 - Crash in Main menu

      Please, can someone tell me how to enable crashlog or debug log on VTI 4.1?

      In /Media/hdd, there is nothing (only usbtuner.log) and /var/log/message is empty, no trace of crash inside....

      A telnet command may be ?

      Any help please ?

    • If it is a kernel panic you do not see something at log.

      You can see it if you do a serial log (connect Vu+ STB wtih RS232 cable and use putty to log)

      Please turn off softcam if do some tests

    • re-
      i have uninstalled softcam and the box haven't crashed..., more than 1 hour without crashe...
      I have tried with different version of softcam 2.1.3 -> 2.3.0 (from VTI Server), and same problem...

      The VU+Solo is now using VTI 4.0, and it seem to be ok, no more freeze...

      Is there other peoples here wich have same bug ?

      Thanks
      Ced

    • Originally posted by fced
      ........
      Is there other peoples here wich have same bug ?

      Thanks
      Ced


      I use VTI 4.1 for some days with a lot of plugins, recording..., and it works fine.
      Try to download another copy of the image..perhaps the image you installed is corrupted or something like that.
      [FONT=verdana][B]Vu+ Solo and VTI 4.2[/B][/FONT] :D

    • In fact, i have notified this problem, with the 3 latest images :
      Blackhole 1.7
      ViX-2.3.204-vusolo_usb.zip
      VTI 4.1...

      May be my VU+ Solo is a clone, and may be it's an protection system, but i have buy it 23/07/2011 before clone exist... i hope it's not a clone, i got a VU+Solo because here, where i live, impossible to found an original Dreambox (500 or 800) and when i have buyed my VU+Solo it was the only one in the local market...
      Before, i have buyed a DM500, then a DM800 thinking clone don't exist, and they was clones, and i'm bored of clones, too much problems...

      Who can tell me more about How identify if my VUSolo is really an original ? i didn't want to open it, and on this page :
      www2.vuplus.com/14-vuplus-articles/100-caution-vu-clone
      I can't find the difference between original and clone...

      I have seen an plugin to detect if the box is a clone, but if it's a clone, i didn't want it be blocked, we are punished by buying an original box with a original price (250 euros here) wich is a clone, and we are punished a second time, when they block the clone functionnalities like Dream Multimedia do...
      I think DMM and VU must attack sellers, and manufacturers, but not final client (we are 2 times victims)...

      Any idea ? how did this clone detection plugin is working ? did someone know ?

      Dieser Beitrag wurde bereits 3 mal editiert, zuletzt von fced ()

    • RE: VU+Solo + VTI 4.1 - Crash in Main menu

      To Schomi - > I have installed it before installing VTI 4.0 image, (one time)

      Should we update the VU+SOLO with cfe solo bootloader each time we change image ?

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von fced ()

    • Hello,
      I have tried today again VTI 4.1, new downloaded file, and i have the same problem,
      i installed CCCam 2.2.1 from Download menu, and after a while, the image is freezing, and the box doesn't respond...
      I tried with CCcam disabled, and for now, no crash...

      When i press any key on the remote control, i can see the led on the VUSOLO flashing, but no response from the box...
      The only way to make it work again is to unplug/plug power chord...

      I have tried also the : "Return to love plugin" to see if my VU+Solo is a clone or a genuine one, and i think it's genuine, i got Authentication Successful...

      So where is the problem ? why CCCam is crashing my VU+Solo ?
      This receiver act only as client, there is only 2 clines in the cccam.cfg file...

      Any idea please ?

      Is there differences between VTI 4.0 and 4.1 in this file ? /usr/script/CCcam_2.3.0_cam.sh
      Could the script cause the problem ?


      ps : i have notified a download/installation emu problem also :
      Impossible to install 2 version of CCCam (CCcam 2.2.1 + CCcam 2.1.3 for example) - One replace the other...
      - And more important : If you install CCCam 2.1.3 for example , and then install CCcam 2.2.1, it's impossible to uninstall them, you have 0 package uninstalled... Impossible to uninstall it and reinstall...

      You need to reflash the box (reinstall the entire image)
      In old version of VTI, if my memory is correct it was possible to have 2 version of CCCam installed (run only one) - (or maybe it was in VIX images - i'm not sure)...

      Dieser Beitrag wurde bereits 3 mal editiert, zuletzt von fced ()

    • Can you take a log with a serial connection ?

      It's possible to install more CCcam versions via VTi Softwaremanager there is no replacement. But it's not possible to run 2 CCcam versions at same time

    • Here it is :)
      This log is from Blackhole 1.7.2, i re-install VTI 4.1 -> to serial log and post again, i'm back in few minutes...

      ps : i'm on macintosh, and was not sure my usb-serial adapter will work...
      Dateien

    • After 2 hours on VTI 4.1, still no bug...
      But this morning before i try Blackhole 1.7.2, i was on VTI 4.0, then i done the update to VTI 4.1, and impossible to watch tv more than 1/2 hour... -> Kernel Panic...
      I'm still logging, but nothing yet...

    • Here is the promise logs, after Kernel panic on VTI 4.1...
      Two kernel panics, after 1-2 hours
      Those logs are chinese for me, i haven't found the cause of kernel panic inside ...

      Kernel Panic on VTI 4.1

      Quellcode

      1. [IDLE] 3269.99993515 60 True
      2. nr_read 241 nr_write 10
      3. sum 251 prev_sum 251
      4. hdd IDLE!
      5. [IDLE] 3275.99993515 60 True
      6. CPU 0 Unable to handle kernel paging request at virtual address 00000008, epc == 802780ac, ra == 80279db4
      7. Oops[#1]:
      8. Cpu 0
      9. $ 0 : 00000000 00000000 00000000 00000000
      10. $ 4 : 80605d70 806057cc 00000000 00000d46
      11. $ 8 : 00000001 00000000 00000001 00000000
      12. $12 : 00000005 000003ff 80600000 805066fc
      13. $16 : 80605d70 86469a30 00000000 80605d70
      14. $20 : fffffffc 806057d0 fffffffe 806057cc
      15. $24 : 00000001 8002305c
      16. $28 : 86464000 86465b88 3b9aca00 80279db4
      17. Hi : 00000317
      18. Lo : 38148500
      19. epc : 802780ac rb_insert_color+0x54/0x1d0
      20. Tainted: P
      21. ra : 80279db4 timerqueue_add+0x88/0x134
      22. Status: 11000402 KERNEL EXL
      23. Cause : 00800008
      24. BadVA : 00000008
      25. PrId : 0101954c (Brcm4380)
      26. Modules linked in: brcmfb dvb_bcm7325(P) procmk
      27. Process CCcam2_3_0 (pid: 741, threadinfo=86464000, task=84c0f728, tls=739fc930)
      28. Stack : 80680000 800564e0 00000001 80279cd8 84c0f87c 80605d70 806057cc 86465c20
      29. 80605790 00000003 806057d0 80600000 00000001 80279db4 86465c20 80605790
      30. 00000003 806057d0 80605d70 806057c0 86465c20 80048e24 86465c20 00000000
      31. 00000001 00000068 80600000 80605790 86465c18 80049c10 84c0f728 ffffffff
      32. 84c0f728 ffffffff 804fedac 86626400 0f7f7b3c 00000d46 0f7f7b3c 00000d46
      33. ...
      34. Call Trace:
      35. [<802780ac>] rb_insert_color+0x54/0x1d0
      36. [<80279db4>] timerqueue_add+0x88/0x134
      37. [<80048e24>] __run_hrtimer+0x9c/0x110
      38. [<80049c10>] hrtimer_interrupt+0x164/0x4b0
      39. [<8000b6a4>] c0_compare_interrupt+0x3c/0x64
      40. [<80060844>] handle_irq_event_percpu+0x5c/0x280
      41. [<800634ac>] handle_percpu_irq+0x58/0x8c
      42. [<80060408>] generic_handle_irq+0x44/0x64
      43. [<80005818>] do_IRQ+0x18/0x24
      44. [<8000225c>] plat_irq_dispatch+0xbc/0x1e0
      45. [<80003f6c>] ret_from_irq+0x0/0x4
      46. [<8027e1fc>] __copy_user+0x38/0x2bc
      47. [<c07025e8>] sc_dev_ioctl+0x204/0x448 [dvb_bcm7325]
      50. Code: 30430001 14600016 00549024 <8e500008> 12110032 00000000 12000020 00000000 8e030000
      51. ---[ end trace a0b5fc5d59378cd2 ]---
      52. Kernel panic - not syncing: Fatal exception in interrupt
      53. Rebooting in 180 seconds..
      Alles anzeigen



      -----------------------------


      Kernel Panic on Blackhole 1.7.2

      Quellcode

      1. hdd IDLE!
      2. [IDLE] 1068.00007391 60 True
      3. nr_read 234 nr_write 6
      4. sum 240 prev_sum 240
      5. hdd IDLE!
      6. [IDLE] 1074.00001097 60 True
      7. nr_read 234 nr_write 6
      8. sum 240 prev_sum 240
      9. hdd IDLE!
      10. [IDLE] 1080.00003099 60 True
      11. nr_read 234 nr_write 6
      12. sum 240 prev_sum 240
      13. hdd IDLE!
      14. [IDLE] 1086.0000329 60 True
      15. nr_read 234 nr_write 6
      16. sum 240 prev_sum 240
      17. hdd IDLE!
      18. [IDLE] 1092.00007796 60 True
      19. CPU 0 Unable to handle kernel paging request at virtual address 00000008, epc == 802780ac, ra == 80279db4
      20. Oops[#1]:
      21. Cpu 0
      22. $ 0 : 00000000 00000000 00000000 00000000
      23. $ 4 : 80605d70 806057cc 00000000 000004c0
      24. $ 8 : 00000001 00000000 00000001 00000000
      25. $12 : 00000005 000003ff 80600000 805066fc
      26. $16 : 80605d70 86759d90 00000000 80605d70
      27. $20 : fffffffc 806057d0 fffffffe 806057cc
      28. $24 : 00000001 8002305c
      29. $28 : 8671e000 8671fb88 3b9aca00 80279db4
      30. Hi : 0000011b
      31. Lo : 2c5c6f00
      32. epc : 802780ac rb_insert_color+0x54/0x1d0
      33. Tainted: P
      34. ra : 80279db4 timerqueue_add+0x88/0x134
      35. Status: 11000402 KERNEL EXL
      36. Cause : 00800008
      37. BadVA : 00000008
      38. PrId : 0101954c (Brcm4380)
      39. Modules linked in: brcmfb dvb_bcm7325(P) procmk
      40. Process CCcam2_3_0 (pid: 737, threadinfo=8671e000, task=86634a18, tls=7307e930)
      41. Stack : 80680000 800564e0 00000001 80279cd8 85584c00 80605d70 806057cc 8671fc20
      42. 80605790 00000003 806057d0 80600000 00000001 80279db4 8671fc20 80605790
      43. 00000003 806057d0 80605d70 806057c0 8671fc20 80048e24 8671fc20 00000000
      44. 00000001 00000068 80600000 80605790 8671fc18 80049c10 00000020 00000000
      45. 0000000a 80680000 0000000d c073e010 0d1d31c8 000004c0 0d1d31c8 000004c0
      46. ...
      47. Call Trace:
      48. [<802780ac>] rb_insert_color+0x54/0x1d0
      49. [<80279db4>] timerqueue_add+0x88/0x134
      50. [<80048e24>] __run_hrtimer+0x9c/0x110
      51. [<80049c10>] hrtimer_interrupt+0x164/0x4b0
      52. [<8000b6a4>] c0_compare_interrupt+0x3c/0x64
      53. [<80060844>] handle_irq_event_percpu+0x5c/0x280
      54. [<800634ac>] handle_percpu_irq+0x58/0x8c
      55. [<80060408>] generic_handle_irq+0x44/0x64
      56. [<80005818>] do_IRQ+0x18/0x24
      57. [<8000225c>] plat_irq_dispatch+0xbc/0x1e0
      58. [<80003f6c>] ret_from_irq+0x0/0x4
      59. [<8027e218>] __copy_user+0x54/0x2bc
      60. [<c07025e8>] sc_dev_ioctl+0x204/0x448 [dvb_bcm7325]
      63. Code: 30430001 14600016 00549024 <8e500008> 12110032 00000000 12000020 00000000 8e030000
      64. ---[ end trace 61ecd50f6e0a6213 ]---
      65. Kernel panic - not syncing: Fatal exception in interrupt
      66. Rebooting in 180 seconds..
      Alles anzeigen
      Dateien

      Dieser Beitrag wurde bereits 3 mal editiert, zuletzt von fced ()

    • VTI 4.0 is working well for me except an problem with Timers ...
      But why did i have this problem with the 3 latest images (VTI 4.1, Backhole , VIX); and why other peoples don't have problems ?
      Did my VU+solo have a hardware problem or a defect ? - it have less than one year ...
      Or may be a plugin or a driver installed by default in 4.1 cause this problem ?

      Is there major differences between VTI 4.0 and VTI 4.1 ?

      Does this mean it's a problem between Tuner and CCCam ?

      Quellcode

      1. Modules linked in: brcmfb dvb_bcm7325(P) procmk
      2. Process CCcam2_3_0 (pid: 741, threadinfo=86464000, task=84c0f728, tls=739fc930)


      lot of questions ... :)

      Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von fced ()

    • No it's no hardware problem.
      Other useres have same problems. The problem is caused by CCcam + driver. So people who do not use CCcam do not get the kernel panic.
      But this problem also exists in VTi 4.0.