Hi
My system specs:
Satellite Box: Vu+ Duo2
Motherboard: VUPLUS_DUO2_MAIN_V1.0 2014.06.11
2 Preinstalled DVBS2 dual tuners
Current installed, flashed image: openvix-4.2.001.release-vuduo2_usb
Previously flashed images (not openvix, but I'm mentioning them for completeness):
BlackHole-2.1.5-vuduo2_usb
BlackHole-3.0.2-vuduo2_usb_release_20160516_e6f1d77
Until today, I had been running openvix-4.2.001.release-vuduo2_usb for 3 weeks without issue. Great image, like the features. However, my Vu+ Duo2 crashed today with a "CPU 0 Unable to handle kernel paging request at virtual address" error in the message log.
Please note my Vu+ Duo2 was bought new from a reputable dealer, and I've never had any problems flashing my OpenVix (or 2 previous Black Hole) image on the Vu+ Duo2, which came in Vu+ packaging.
For your info, I had the same recording crash issue every 2-3 weeks with the Black Hole images. Please note I want to stick with the OpenVix image, which I prefer to Black Hole, from this point onwards.
The crash happens during recording. I've already situated my hard drive outside of the Vu+ Duo2 to eliminate any possible overheating issue due to the hard drive.
With OpenVix, the unit's network file shares were still available after the crash, as was SSH access. WebIf was unavailable after the crash.
Obviously I've tried changing image provider and moved the hard drive outside of the Vu+ Duo2, but the recording crash problem persists. A restart of the Vu+ Duo2 is required before recordings can resume.
I'd be really, really grateful for any help/suggestions to resolve this issue. Many thanks in advance for your help.
Please find the relevant portion of the unit's message log below:
Sep 10 13:11:20 vuduo2 user.warn kernel: !!!^M[DMX]: paserband_remove_pid pid 0x51f not found
Sep 10 13:11:20 vuduo2 user.warn kernel: !!!^M[DMX]: mcba GetBuffer Error ...type : 1, pes_type : 20, ts_type : 9 pid : 0x507
Sep 10 13:11:21 vuduo2 user.alert kernel: CPU 0 Unable to handle kernel paging request at virtual address 00000028, epc == e0ce3a00, ra == e0ce3a00
Sep 10 13:11:21 vuduo2 user.warn kernel: Oops[#1]:
Sep 10 13:11:21 vuduo2 user.warn kernel: CPU: 0 PID: 2761 Comm: mgcamd_138c Tainted: P O 3.13.5 #1
Sep 10 13:11:21 vuduo2 user.warn kernel: task: cf5b8020 ti: cfed0000 task.ti: cfed0000
Sep 10 13:11:21 vuduo2 user.warn kernel: $ 0 : 00000000 10008700 0000fc81 cf2cc284
Sep 10 13:11:21 vuduo2 user.warn kernel: $ 4 : 10008701 10008701 000002e7 00000001
Sep 10 13:11:21 vuduo2 user.warn kernel: $ 8 : 00000000 84080008 800f9a10 00000001
Sep 10 13:11:21 vuduo2 user.warn kernel: $12 : 770fea50 1000d2b0 10010c70 00408dc4
Sep 10 13:11:21 vuduo2 user.warn kernel: $16 : cf2e0b00 cf2e0b00 00000000 00000000
Sep 10 13:11:21 vuduo2 user.warn kernel: $20 : 00000000 e10d73a0 e18f0000 e0d50000
Sep 10 13:11:21 vuduo2 user.warn kernel: $24 : 004082e4 8006ff60
Sep 10 13:11:21 vuduo2 user.warn kernel: $28 : cfed0000 cfed1c20 e0d50000 e0ce3a00
Sep 10 13:11:21 vuduo2 user.warn kernel: Hi : 00002bcb
Sep 10 13:11:21 vuduo2 user.warn kernel: Lo : f2e06ccc
Sep 10 13:11:21 vuduo2 user.warn kernel: epc : e0ce3a00 NEXUS_BaseObject_P_RegisterUnregister+0x17c/0x3bc [dvb_base]
Sep 10 13:11:21 vuduo2 user.warn kernel: Tainted: P O
Sep 10 13:11:21 vuduo2 user.warn kernel: ra : e0ce3a00 NEXUS_BaseObject_P_RegisterUnregister+0x17c/0x3bc [dvb_base]
Sep 10 13:11:21 vuduo2 user.warn kernel: Status: 10008703 KERNEL EXL IE
Sep 10 13:11:21 vuduo2 user.warn kernel: Cause : 00800008
Sep 10 13:11:21 vuduo2 user.warn kernel: BadVA : 00000028
Sep 10 13:11:21 vuduo2 user.warn kernel: PrId : 00025a11 (Broadcom BMIPS5000)
Sep 10 13:11:21 vuduo2 user.warn kernel: Modules linked in: ipv6 brcmfb(O) dvb_bcm7424(PO) dvb_base(PO) bcm_event(PO) procmk(O) rt5370sta(O) rt2800usb rt2800lib rt2x00usb rt2x00lib mac80211 xfs libcrc32c
Sep 10 13:11:21 vuduo2 user.warn kernel: Process mgcamd_138c (pid: 2761, threadinfo=cfed0000, task=cf5b8020, tls=77106930)
Sep 10 13:11:21 vuduo2 user.warn kernel: Stack : 00000000 00000000 00000000 00000000 cf5d6134 00000000 00000000 00000000
Sep 10 13:11:21 vuduo2 user.warn kernel: 00000000 00000200 ce427500 e19f114c 00000200 e18f0000 e0d50000 e0d37f5c
Sep 10 13:11:21 vuduo2 user.warn kernel: cf2e0a80 e0e4b104 00000000 ffffffff cf2e0b00 ffffffff 00000000 e0d50c54
Sep 10 13:11:21 vuduo2 user.warn kernel: 00000000 00000000 00000000 00000000 e1aaa768 e18f54f4 00000000 e13163a8
Sep 10 13:11:21 vuduo2 user.warn kernel: e18ef984 e19ec6dc e19ecb74 cb426080 00000000 e18f493c 0041a400 8000367c
Sep 10 13:11:21 vuduo2 user.warn kernel: ...
Sep 10 13:11:21 vuduo2 user.warn kernel: Call Trace:
Sep 10 13:11:21 vuduo2 user.warn kernel: [<e0ce3a00>] NEXUS_BaseObject_P_RegisterUnregister+0x17c/0x3bc [dvb_base]
Sep 10 13:11:21 vuduo2 user.warn kernel: [<e0d37f5c>] NEXUS_PidChannel_BaseObject_P_RegisterUnregister+0 x34/0x40 [dvb_base]
Sep 10 13:11:21 vuduo2 user.warn kernel: [<e0d50c54>] NEXUS_PidChannel_Close+0x38/0x60 [dvb_base]
Sep 10 13:11:21 vuduo2 user.warn kernel: [<e18f54f4>] bcm7335_demux_release_priv+0x508/0x10fc [dvb_bcm7424]
Sep 10 13:11:21 vuduo2 user.warn kernel: Code: afa20010 0060f809 02602821 <8e430028> 10600041 8fa20010 12800011 00000000 8e430020
Sep 10 13:11:21 vuduo2 user.warn kernel: ---[ end trace 33523f593e9ebfc5 ]---
