26 replies to this topic

[anudanan]

Today my uno4kse made two recordings (3SAT HD and ONE HD)

 

My wife than go to the Channel Selection Menu and would like to select an other channel, I don´t know which channel she has selected. But after pressing OK to goto the new channel the spinner comes and I have seen with dmesg or in /var/log/messages a driver crash

 

I´ve have attached th message file from /var/log

 

Are you able to fix that problem? I remember I´ve seen that some weeks ago but I´have not any log from that crash

 

 messages.txt   179.56KB   9 downloads 

[betacentauri]

We cannot fix it. We don’t have the source code. Only VU+ can fix it. Can you reproduce it?

[anudanan]

Today I can´t reproduce it.  It comes without any special things we do.

 

My uno4kse has two legacy sat cable for tje FBC tuners and are connected to a legacy multiswitch and normaly it works fine with the restriction that I can use only 2 of the 4 quadrants of Astra at the same time. Today the restriction is no problem for me and my wife. For solving that restriction I use the PLI fallbacktuners which I use also in the past with my et8000 receivers.

 

Maybe that the drivercrash has to do with using legacy sat connection instead of unicable but I don´t know.

 

Do you think that using fallbacktuner can motivate the drivercrash or is the mechanism to use fallback tuner outside the driver code?

 

I will read and search in the VTI forum and openatv forum if anyone has the some problem with VTI. I think all images use the same driver and kernel version today for the uno4kse and therefor the bug must be include in alle different images

Edited by anudanan, 4 February 2018 - 18:48.

[Erik Slagter]

Feb  4 17:24:26 Wohnzimmer user.warn kernel: [216095.159530] !!!^M[DMX]: paserband_remove_pid pid 0x0 not found
Feb  4 17:24:26 Wohnzimmer user.warn kernel: [216095.159530] 
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.789087] !!!^M[DMX]: paserband_remove_pid pid 0x13f6 not found
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.789087] 
Feb  4 17:24:36 Wohnzimmer user.alert kernel: [216104.799043] Unable to handle kernel NULL pointer dereference at virtual address 0000002c
Feb  4 17:24:36 Wohnzimmer user.alert kernel: [216104.807389] pgd = d4203cc0
Feb  4 17:24:36 Wohnzimmer user.alert kernel: [216104.810598] [0000002c] *pgd=11a30003, *pmd=11a4b003, *pte=00000000
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216104.817119] Internal error: Oops: 207 [#1] SMP ARM
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.822009] Modules linked in: bluetooth ipv6 brcmfb(O) dvb_bcm7252sse(PO) dvb_base(PO) bcm_event(PO) procmk(O)
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.832321] CPU: 0 PID: 1500 Comm: enigma2 Tainted: P           O    4.1.20-1.9 #2
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.839985] Hardware name: Broadcom STB (Flattened Device Tree)
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.845999] task: d4042580 ti: d2794000 task.ti: d2794000
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.851620] PC is at NEXUS_BaseObject_P_RegisterUnregister+0x1d8/0x344 [dvb_base]
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.859374] LR is at NEXUS_BaseObject_P_RegisterUnregister+0x1d8/0x344 [dvb_base]
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.866952] pc : [<bf00f158>]    lr : [<bf00f158>]    psr: 60030013
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.866952] sp : d2795e48  ip : 00000000  fp : bf69d3ec
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.878613] r10: bf693df0  r9 : 00000000  r8 : 00000000
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.883929] r7 : bf3aba30  r6 : d42f7b40  r5 : 00000000  r4 : d42f7b40
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.890549] r3 : 00004b07  r2 : d3755c4c  r1 : 60030013  r0 : d3755c44
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.897171] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.904400] Control: 30c5387d  Table: 14203cc0  DAC: fffffffd
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216104.910238] Process enigma2 (pid: 1500, stack limit = 0xd2794210)
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216104.916425] Stack: (0xd2795e48 to 0xd2796000)
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216104.920875] 5e40:                   bf3a9b58 00000000 d20bfd00 bf69d3ec bf68ccf4 d6e1d8a4
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216104.929148] 5e60: bf693df0 bf06909c d42f7b40 bf2a6438 bf3a9b58 bf07ec38 00000003 00000000
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216104.937421] 5e80: d6e1e8a4 bf58c60c 00000000 00000000 00000000 00000000 d40425c8 d2795fb0
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216104.945693] 5ea0: d2218e40 00000a0f 011efec0 d4042580 d23066f0 d2218e7c 00000055 c001ef98
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216104.953965] 5ec0: d2795f64 c0051688 d5a4e400 01000000 d57f7003 00000008 00000800 00000000
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216104.962239] 5ee0: 00000000 bf68cee4 d6e1d8a4 bf68cecc d6e1e8a4 d6bd91bc 00000008 d29ef708
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216104.970512] 5f00: 00000000 c045d838 d6bd9140 d6bd9140 bf68c688 d41bfa10 d6bd91bc c045b3c8
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216104.978784] 5f20: d6bd9140 d6bd9140 bf68c688 c045b578 d6bd9140 bf68c640 bf68c688 d41bfa10
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216104.987057] 5f40: d6bd91bc c045ba40 d29ef700 d36cb488 00000000 d41bfa10 d47f5110 c00e11d0
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216104.995329] 5f60: 00000000 00000000 d404296c 00000000 c089b098 d4042580 c00100c4 d2794000
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216105.003602] 5f80: 00000000 c003e6b8 d2794000 c00100c4 d2795fb0 00000006 c00100c4 c0012e48
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216105.011875] 5fa0: 010df2e8 bec8df44 015c3a30 c000ff8c 00000000 00000002 b5d694c0 b5d69084
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216105.020148] 5fc0: 010df2e8 bec8df44 015c3a30 00000006 a9c75ad0 0023dd28 b67d7de0 00000000
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216105.028421] 5fe0: 00000000 bec8df18 00000000 b626af98 80030010 00000077 00000000 00000000
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216105.037063] [<bf00f158>] (NEXUS_BaseObject_P_RegisterUnregister [dvb_base]) from [<bf06909c>] (NEXUS_PidChannel_BaseObject_P_RegisterUnregister+0x28/0x34 [dvb_base])
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216105.052275] [<bf06909c>] (NEXUS_PidChannel_BaseObject_P_RegisterUnregister [dvb_base]) from [<bf07ec38>] (NEXUS_PidChannel_Close+0x38/0x54 [dvb_base])
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216105.066017] [<bf07ec38>] (NEXUS_PidChannel_Close [dvb_base]) from [<bf58c60c>] (bcm7335_demux_stop_feed_trans+0x450/0x1090 [dvb_bcm7252sse])
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216105.078748] [<bf58c60c>] (bcm7335_demux_stop_feed_trans [dvb_bcm7252sse]) from [<c045d838>] (dmx_section_feed_stop_filtering+0x34/0x8c)
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216105.091025] [<c045d838>] (dmx_section_feed_stop_filtering) from [<c045b3c8>] (dvb_dmxdev_feed_stop+0xa4/0xac)
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216105.101039] [<c045b3c8>] (dvb_dmxdev_feed_stop) from [<c045b578>] (dvb_dmxdev_filter_stop+0x90/0xd0)
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216105.110269] [<c045b578>] (dvb_dmxdev_filter_stop) from [<c045ba40>] (dvb_demux_release+0x2c/0x18c)
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216105.119328] [<c045ba40>] (dvb_demux_release) from [<c00e11d0>] (__fput+0x80/0x1c8)
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216105.126997] [<c00e11d0>] (__fput) from [<c003e6b8>] (task_work_run+0xac/0xe4)
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216105.134231] [<c003e6b8>] (task_work_run) from [<c0012e48>] (do_work_pending+0x7c/0xa4)
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216105.142247] [<c0012e48>] (do_work_pending) from [<c000ff8c>] (work_pending+0xc/0x20)
Feb  4 17:24:36 Wohnzimmer user.emerg kernel: [216105.150086] Code: e1a00001 e1a02005 e1a01009 e12fff3c (e598302c) 
Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216105.156431] ---[ end trace be256f68a68c3fff ]---
Feb  4 17:26:16 Wohnzimmer authpriv.info dropbear[15358]: Child connection from 192.168.1.47:36460
Feb  4 17:26:16 Wohnzimmer authpriv.notice dropbear[15358]: PAM password auth succeeded for 'root' from 192.168.1.47:36460

[anudanan]

My message file shows the following lines before the driver crashes with a null pointer access

 

Feb  4 17:24:26 Wohnzimmer user.warn kernel: [216095.136360] [VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0

Feb  4 17:24:26 Wohnzimmer user.warn kernel: [216095.142443] [VID]: VIDEO_GET_SIZE aspect: 1 0

Feb  4 17:24:26 Wohnzimmer user.warn kernel: [216095.159530] !!!^M[DMX]: paserband_remove_pid pid 0x0 not found

Feb  4 17:24:26 Wohnzimmer user.warn kernel: [216095.159530] 

Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.789087] !!!^M[DMX]: paserband_remove_pid pid 0x13f6 not found

Feb  4 17:24:36 Wohnzimmer user.warn kernel: [216104.789087] 

Feb  4 17:24:36 Wohnzimmer user.alert kernel: [216104.799043] Unable to handle kernel NULL pointer dereference at virtual address 0000002c

Feb  4 17:24:36 Wohnzimmer user.alert kernel: [216104.807389] pgd = d4203cc0

 

Is that really a driver bug or is it possible that the enigma source calls the driver with wrong parameters?

 

What does the message mean "paserband_remove_pid"

 

normally after VIDEO_GET_SIZE there comes kernel messages to stop Audio and Video, then continue audio  an then goto tune

 

Feb  4 17:24:23 Wohnzimmer user.warn kernel: [216091.384292] [VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0

Feb  4 17:24:23 Wohnzimmer user.warn kernel: [216091.391944] [VID]: VIDEO_GET_SIZE aspect: 1 0

Feb  4 17:24:26 Wohnzimmer user.warn kernel: [216094.771035] [VID]: VIDEO_STOP 1  1

Feb  4 17:24:26 Wohnzimmer user.warn kernel: [216094.774758] [AUD]: AUDIO_STOP 0 

Feb  4 17:24:26 Wohnzimmer user.warn kernel: [216094.801864] [AUD]: AUDIO_CONTINUE 0 0 aph=0x0

Feb  4 17:24:26 Wohnzimmer user.warn kernel: [216094.806432] [AUD]: AUDIO_CONTINUE aph=0 0 0

Feb  4 17:24:26 Wohnzimmer user.warn kernel: [216094.901045] FE tune

 

 

On this box I´ve the latest 6.1rc before the 6.1 release came out. Is there a hope that 6.1 release does not have that problem? 

Until today I have no time to make an update because the box makes many recordings for my wife and I have not found a maintenance slot for the box.

[WanWizard]

DMX demux was a bug in the drivers of older VU+ models, back in 2016. It has been reported here on a Solo 4K in march 2017 too.

So my feeling is VU+ has a serious issue in their driver code, which still isn't fixed.

 

6.1-rc and 6.1-release are virtually identical. And given the fact that this seems to be a long-standing bug, I don't expect it to be fixed soon.

[anudanan]

Do you have informationens what are the circumstances to come into the bug. I´ve not seen any reason why it came up.  Is there a know workaround available. For example switching from a legacy SAT installation to a unicable installation?

 

Very strange that VU don´t fix those problems. 

[WanWizard]

No, I don't. I'm not a VU+ user myself, but I've seen many reports of this bug, on lots of different VU+ boxes, over the years.

 

Assuming that they use the same source as the basis for new drivers, it is clear that have a design issue that every new driver has inherited.

[anudanan]

It is not so easy today to find a modern stable box

 

Many years ago I used 3 et9200 and they were very stable with openpli. I think the driver were stable

Some years later I bought 2 et8000 for better performance. The driver also were stable but the two boxes have problems (Link down/up problems) with the ethernet interface. A workaround with USB ethernet adapters don´t work very stable, Many times I see problem in the usb ethernetdriver that the driver has lost events.

Than I bought last year two uno4kse to replace the et8000. Now I´m not happy with the driver quality of VU and it sounds not good what you say about the fixing reaction of VU in the past. They sell and sell boxes but they spend not the time to make the driver stable. Strange

 

I like FBC tuners and I think today the only openpli supportet boxes are the VU.

I´ve seen in your GIT that you´ve integrated the bsp for Gigablue. I think the gigablue quad 4k support also FBC tuners and I think about a next change to gigablue quad 4k when you support it and if the driver of gigablue is more stable than drivers of VU

 

What do you think about a time frame to support gigablue and what do you think about the driver quality of gigablue

 

Strange that today it is so difficult to find a stable and modern box.

[WanWizard]

I can only guess, but my 2ct's:

 

A large part of the market is (or has been) driven by illegal use, which saw a surge in the production of simple, cheap, low-end hardware. At the same time, providers are stepping up security, so the market for real enthousiasts is getting smaller due to the introduction of CI and CI+ requirements, and cards linked to hardware. And it is this market that buys the high-end boxes. I think it is also one of the causes of the failure of Elicom GmbH and the Xtrend brand.

 

I personally think the HD2400 and the ET10000 are still very good boxes, if you don't have FBC and UHD requirements. If you have, there are only a few manufacturers that can supply that, VU+ currently being the biggest. We are working very close with VU+ to get the issues resolved, but it is clearly not an area they are willing to spend a lot of money on. On the plus side, they have their own developers, many brands reply on third parties, which makes regular maintenance very complicated and time consuming.

 

We've been working with Gigablue since last years ANGA, but it is a difficult relation with very slow progress, due to bugs in the drivers, that are so severe that we will not release an image until they are addressed. Some have been fixed in the last few weeks, but the most important one, CI support, is still a big problem. So I can't give you a timeframe, we have to wait until Gigablue's developer(s) address the outstanding issues... 

[Erik Slagter]

BTW this bug is known and has been reported to VU+. There is no workaround possible and is not triggered by some enigma bug.

[anudanan]

Í´ve seen that just in the moment on 

http://code.vuplus.c...0255643f6e8a7d9

 

Update drivers(4k models)
 - Fix HDR/HLG problem
 - Fix grab problem
 - Fix demux problem
 - Improve overall performance
Update kernel config
 - Adjust driver memory allocations

 

I hope that solve the driver crashs

[anudanan]

Today there is a next driverupdate for vu 4K models available

 

update drivers(4k models)
 - Fix demux problem

[anudanan]

Today I´ve seen this commit 

https://github.com/O...2d81e9b9557f75c

 

as a driver update for vuplus in  the developer branch.

 

Is the goal from openpli to make a 6.2rc/rel with these new driver in future ? So the only way to use the new drivers is to update from 6.1 to 6.2 in future?

Edited by anudanan, 21 February 2018 - 21:45.

[WanWizard]

Yes.

[anudanan]

Do you have an idea when you start the 6.2rc phase?
Today I‘ve seen a next driver crash on one of my two uno4kse boxes

[WanWizard]

Is already in the planning.

[twol]

Seeing post #9, thought I would add my comments, as a basic user rather than the more exacting requirements of OpenPli.
I have had most of the Xtrend boxes at some time and in my view the ET8500 was a great product with excellent design characteristics - a pity that Xtrend disappeared.
Mainly, because I wanted to try FBC tuners (and didn‘t want Vu+), I bought the GigaBlue 4K at first availablity, and to be honest have never had an issue, regardless of other user issues, but then I don‘t need CI, HbbTV, Kodi etc etc.
With the Images I use (and build) OpenViX, OpenATV ..and OpenPli, I always have a very stable box that provides me with the platform for my 28.2E/19.2E setup using unicables switches for both the FBC tuners and other legacy requirements.... and with integrated multiboot facilities (which I have on all the 3 Giga4K images) it really provides a great platform... and acts as the fallback tuner box for the other receivers where necessary

Edited by twol, 26 February 2018 - 20:48.

[anudanan]

The driver crash today comes up after starting the CutListEditor . Normaly the CutListEditor starts the movie but here the driver crashes.

I hope the fixes in the new driver solve the problem.

 

I have it not so often but every crash is annoying

[Erik Slagter]

Also don't put your family fortune on the driver update. It may help, it may not. In the meantime try to find out what it triggers and try to avoid that action. Another workaround can be to reboot the receiver once a day, you can do it on schedule, so you don't have to think of it yourself.