[VU+ Duo] Turn ON issue

[Sicilian]

When you do the clean install and if it crashes, can you please post an exact step by step of how to replicate the crash.

 

[Rob van der Does]

When you do the clean install and if it crashes, can you please post an exact step by step of how to replicate the crash.

I promise you: there is no reproducing method at all. It just happens, regardless hard-and software setup, regardless of operation, sometimes a couple of times per day, sometimes 'only' twice a week.
See the numerous reports on several forums, including our own.

And the crash is a real system crash (no E2 crash), also an indication for a driver problem. After all the reports and testing that has been done there's only one obvious conclusion: VU+ will have to deal with it. Many reports have been sent to them.

 

[brdbch]

There may be other (probably numerous) problems where the system crashes.

The one i'am looking into has always the same pattern:
1/2 hour after going into sleep mode, the clock resets to 1970.
A while later E2 gets into a exception loop due to an long int to int overflow (creating a huge log file).
The only way to get out in power off/on (or connect via telnet and kill E2).
This does not occur with a fresh install (no plugins, no softcams, no configuration changes).

Always occurs on the fresh install if log and EPG turned on, HDMI CEC off (still no additional plugins, no softcams).
This probably would lead to a real system crash if the log file is stored on flash, since it would use up all space.

 

[Sicilian]

There may be other (probably numerous) problems where the system crashes.

The one i'am looking into has always the same pattern:
1/2 hour after going into sleep mode, the clock resets to 1970.
A while later E2 gets into a exception loop due to an long int to int overflow (creating a huge log file).
The only way to get out in power off/on (or connect via telnet and kill E2).
This does not occur with a fresh install (no plugins, no softcams, no configuration changes).

Always occurs on the fresh install if log and EPG turned on, HDMI CEC off (still no additional plugins, no softcams).
This probably would lead to a real system crash if the log file is stored on flash, since it would use up all space.

You must post an exact step by step. i.e.
1. Flash image.
2. Start up wizard settings
3. Any system settings changed.

We need to be able to re-produce your exact step.

 

[brdbch]

I Reflashed 2.3.153, upgraded to 204, no additional plugins installed, no softcam installed, debug only log activated, default EPG configuration, running FreetoAir.
In this configuration no crash.

I activated EPG Automatic refresh, other EPG to default values, power off/on: still no crash

I activated EPG Automatic Save, power off/on: in this configuration i got the crash.

Turned back off Automatic Save, power off/on: still got the crash
Turned back off Automatic refresh, power off/on: still got the crash

Turning off EPG may leave some things behind???

 

[Sicilian]

You dont need Automatic Save or refresh. This only used on receiver that have no internet access and sharing epg from another networked receiver. Crossepg will update and refresh your EPG with the settings you set.

As stated we need an exact step by step of how your getting the crash to replicated. Also please post latest crash logs.

 

[brdbch]

Reflashed 2.3.153
configured Tuner A simple Astra
Tuner B loopthru A
scan services
set DHCP off, fix IP
Debug log to /media/hdd
HDMI CEC off
upgraded to 204
set EPG Automatic refresh on
set EPG Automatic Save on
power off/on
check EPG settings
Put in standby mode
Wait.

You can check by looking at the date (goes back to 1970) and the size of the log file with telnet.

 

[Sicilian]

Reflashed 2.3.153
configured Tuner A simple Astra
Tuner B loopthru A
scan services
set DHCP off, fix IP
Debug log to /media/hdd
HDMI CEC off
upgraded to 204
set EPG Automatic refresh on
set EPG Automatic Save on
power off/on
check EPG settings
Put in standby mode
Wait.

You can check by looking at the date (goes back to 1970) and the size of the log file with telnet.

Please confirm that time is set to transponder and not NPT.

 

[brdbch]

For these tests i did not change the default settings (i think its transponder time).
Anyway previous tests (in previous log files) showed same symptoms wether ntp was turned on or not.

 

[brdbch]

There is a quite dirty workaround.
By using a shell script to force by ntpdate the Linux clock back to normal every minute, there is no crash of E2.

#!/bin/sh
#
#
echo "starting"
while :
do
sleep 60
ntpdate pool.ntp.org
echo "looping"
done

This confirms that the root of the problem is this linux clock being reset to 1970.
This reset occurs exactly every 30 minutes when in standby mode.

 

[brdbch]

I send you a trace of the ntpdate shell output, showing the periodic reset of linux time.

 

[paul362]

Could you list filesystem on the drives, plugins and skins installed please.

Bit late sorry been away !!

Ok EXT4 on bith USB And HDD

plugins as standard image NO extra's

Standard skin that comes with 2.3 no others installed.:smash:

 

[andyblac]

strange that you do not have NTP turn on yet it is polling, please try this version (unzip).

place in '/usr/lib/enigma2/python/Components/NetworkTime.pyo'

restart gui.



let me how you get on.

andy.

 

[brdbch]

Tried it, no change.

 

[andyblac]

Tried it, no change.

then you must be dong or installing something, i can't reproduce the bug at all. with NTP enabled or disabled.


please turn each setting one by one, try find out which one is casing the issue.

ie


flash image, put to standby wait the 30 mins see if it causes bug, if not, turn on ONE setting put back to standby, and to see if bug occurs. if not turn another settings. repeat until you find the setting that causes the bug.

 

[brdbch]

That's what i did (see my posts dated 17/02).
Is it normal that after a power on , the log file names look like "Enigma2-01-01-1970_01-00-34.log", while correct time has been set in the /var/log/message.0 file ?
From the traces , it looks like the RTC is not set to current time.
Could this be caused by some hardware revision in the vu+ duo boxes (mine is new).

 

[Sicilian]

Are you 100% sure that you have a genuine receiver?

 

[brdbch]

I hope so!
I bought it from a company which claims to be the official french importer.

 

[andyblac]

set EPG Automatic refresh on
set EPG Automatic Save on

you can't have BOTH options on, on the SAME box, SAVE is for a SERVER BOX, the REFRESH is for CLIENT BOX, DO NOT use both together.

how may boxes do you have ?

this might be causing your loop.


andy.

 

[sivhead]

I had this problem and disabled XML TV not to update at a certain time, Think the default was 04:00 in the morning. With the setting on my box would not come out of deep standby. when this is turned off all is ok.