Nobody answers my question in solved thread [solved] Wrong system time, how to get the correct time again
so I create ne one to report this problem:
To reproduce:
1. Switch to transponder with broken time from the future (e.g. now on 9E 11804/V/27500, time is resync about 20 min)
2. Dreambox synchronizes bad time what is not problem yet
3. But then switch to channel with correct time and you get: (journalctl -f -u enigma2 | grep eDVBLocalTimeHandler)

cze 07 18:09:27 dm520 enigma2[176]: [eDVBLocalTimeHandler] Receiver time is 'Thu Jun  7 18:28:06 2018'
cze 07 18:28:06 dm520 enigma2[176]: [eDVBLocalTimeHandler] Transponder time is 'Thu Jun  7 18:07:12 2018'
cze 07 18:28:06 dm520 enigma2[176]: [eDVBLocalTimeHandler] diff is -1254
cze 07 18:28:06 dm520 enigma2[176]: [eDVBLocalTimeHandler] we have correction 135
cze 07 18:28:06 dm520 enigma2[176]: [eDVBLocalTimeHandler] diff after add correction is -1119
cze 07 18:28:06 dm520 enigma2[176]: [eDVBLocalTimeHandler] use stored correction(<5 min)
cze 07 18:28:06 dm520 enigma2[176]: [eDVBLocalTimeHandler] update RTC
cze 07 18:28:06 dm520 enigma2[176]: [eDVBLocalTimeHandler] time_difference is -1119
cze 07 18:28:06 dm520 enigma2[176]: [eDVBLocalTimeHandler] update Linux Time

Expected:
Time is fixed to correct time.
Actual:
No time fix -Time is wrong!

Even after restart of DM there is the same behaviour, only switching off power for several seconds resets time to 1.1.1970 and then time is fill in properly.
Can anyone fix it or give at least any workaround to reset to corect time, please. (NTP on/off did not change anything).

Once again, I think this issue is still reproducible in some cases when time was broken on bad transponder and set to 2h from the future
Even with ntp enabled and switch to correct time transponder I got:

maj 31 01:11:08 dm520 enigma2[1682]: [eDVBLocalTimeHandler] Receiver time is 'Thu May 31 01:11:08 2018'
maj 31 01:11:08 dm520 enigma2[1682]: [eDVBLocalTimeHandler] Transponder time is 'Wed May 30 23:08:17 2018'
maj 31 01:11:08 dm520 enigma2[1682]: [eDVBLocalTimeHandler] diff is -7371
maj 31 01:11:08 dm520 enigma2[1682]: [eDVBLocalTimeHandler] no correction found... store calced correction(7371)
maj 31 01:11:08 dm520 enigma2[1682]: [eDVBLocalTimeHandler] not changed

Is this really accepted action? Time shouldn't be fixed?
I doubt only switch off of DM should be solution.

Hi,

Maybe its a stupid question but after 1h I was not able to do it:
There is web browser on my Dreambox DM 525 HD but how to write in authorization window password with caps letters e.g 'W' or special chars '%' etc ? Look that I can only write numbers there

Regards,
marrak

Yes, I can confirm this fixes above issue! Thank you very much. I hope you can include it in next release

Still reproducible on r24

I checked my DM 525HD and indeed only 306MB RAM so it's good question
But AGC - I see you did not have original image so maybe it is a reason. On my original image there is no AGC field even. But after several months of usage similar is BER always 0, why it does not work, I don't know

I manage to reproduce it on any channel: in dreamboxedit put vpid and pcr empty value and for mpeg some random value (most likely must be different than proper for that channel). Then sent update to Dreambox and switch to this channel and after several seconds enigma2 freeze.
Please fix for this issue

Thank you very much! I'm using more than one year my DM and did not notice this settings

Where can I get ntp for Dreambox DM 525 HD? I did not see it in apt repo

@mimisiku did you try to reproduce it on your DM 525?

Thanks for respond
I'm trying to compile enigma2 to debug it my myself but any help of more expreience users or developers will be helpful.
I can confirm reprodution of the problem a moment ago on :
Hotbird 13E 11488 27500 H sid 5198
http://en.kingofsat.net/tp.php?tp=796
My firmware:
Image: Experimental 2017-07-20
Dreambox OS: 4.3.1r20-2017-11-07
All up to date.
Logs:
I move now all files to dedicated directory so above posts link may be deprecated
All log files are available here:
https://mega.nz/#F!FPonlAjZ!CMEKPkdTFtUxJfyti7HYEw

I can produce fresh logs if required.

There are more channels I have the same problem, but data of this I saved to tests.

I'm still trying to workaroud it at least
Here is dmesg output:
https://mega.nz/#!xa4GUSxY!pI8…RISmFwY9jUABK5yAosOrYSCco
It looks something very bad happens on some channels:

[63838.185000] CPU 0 Unable to handle kernel paging request at virtual address 00a45b2c, epc == e07911a4, ra == e0791154
[63838.186000] Oops[#1]:
[63838.186000] Cpu 0
[63838.186000] $ 0   : 00000000 10008b00 00a45b2c 7fffffff
[63838.186000] $ 4   : 0397029e e0a45b30 00010000 0000001f
[63838.186000] $ 8   : 000e210f af721b9f 0001ffff 807439f8
[63838.186000] $12   : 00000050 00000006 0000002c 00000022
[63838.186000] $16   : 00000000 e0a386e0 00000001 00000000
[63838.186000] $20   : 805d015c e0a386e0 e0a39d68 805d015c
[63838.186000] $24   : 00000000 80335110                  
[63838.191000] $28   : af720000 af721c10 00000000 e0791154
[63838.191000] Hi    : 00000000
[63838.191000] Lo    : 00000178
[63838.191000] epc   : e07911a4 bcm_xpt_decoder_stop+0x248/0x2b8 [bcm73625]
[63838.191000]     Tainted: P           O
[63838.191000] ra    : e0791154 bcm_xpt_decoder_stop+0x1f8/0x2b8 [bcm73625]
[63838.191000] Status: 10008703    KERNEL EXL IE 
[63838.191000] Cause : 00800004
[63838.191000] BadVA : 00a45b2c
[63838.191000] PrId  : 0002a065 (Broadcom BMIPS4380)
[63838.191000] Modules linked in: dreambox_keyboard(PO) bcm73625(PO) atbm781x(PO) lnb_ctrl(PO) dreambox_rc2(PO) stb_core(PO)
[63838.191000] Process enigma2 (pid: 194, threadinfo=af720000, task=afe1f2f8, tls=77232490)
[63838.191000] Stack : 00000001 00000000 ffffffff 00000000 00000000 00000000 00000000 e0a28280
[63838.191000]         00000000 e0a28260 00000000 00000000 00000000 00000000 af57f480 00018000
[63838.191000]         00001776 0006ddd0 00001000 00000bbb 0002bf98 00000000 0006defc 00000000
[63838.201000]         00000000 00000000 00001388 af58df00 00000008 00000001 e0a3a060 e0a39af8
[63838.201000]         e0a386e0 00000007 805d015c 00000070 e0a39dd8 e07a8af0 00000000 00000000
[63838.201000]         ...
[63838.201000] Call Trace:
[63838.201000] [<e07911a4>] bcm_xpt_decoder_stop+0x248/0x2b8 [bcm73625]
[63838.201000] [<e07a8af0>] bcm_audio_decoder_xpt_stop+0xf0/0x1d0 [bcm73625]
[63838.201000] [<e0786404>] bcm_dvb_demux_free_pid_channel+0xa14/0xabc [bcm73625]
[63838.201000] 
[63838.201000] 
[63838.201000] Code: 00031827  c0440000  00832024 <e0440000> 1080fffc  00000000  02301021  2403ffff  ac400ebc 
[63838.209000] ---[ end trace 27de713721ad43f6 ]---

Can anyone help? Or how can I report this issue to Dreambox developer?

I have no experience in enigma2 at all but this lines look strange for me:

SubServices is returning list  [('1:0:1:144E:5DC:13E:820000:0:0:0:', '(...)')]
timeout 0012!
...
sdt update done!
SubServices is returning list  [('1:0:1:144E:5DC:13E:820000:0:0:0:', ' ')]

Look like channel changes name (?)
And a moment later, I think it the time when enigma2 stops responding...

AUDIO_STOP - ok
DEMUX_STOP - audio - main thread is non-idle! display spinner!
15467085 ms latency per 1000 blits (0,064653 fps)
[EPGC] schedule other finished(1510166104)
119999 ms latency per 1000 blits (8,333403 fps)

But why? And how to prevent or restart it?

Zitat von m0rphU

In DreamOS we have systemd, so please use it

Code

systemctl restart enigma2

Thank you for replay.
Yes of course I tried systemctl too
So now output of

journalctl -f -u enigma2 > /tmp/enigma2_running.log

enigma2_running.log

>Nov 08 19:37:45 dm520 systemd[1]: Stopping enigma2...
Here I restart enigma2

At the end the same output as I wrote earlier
Any ideas?

Hi
On some channels my Dreambox DM 525 HD stops working: on the screen there is settings icon only and web interface or remote control does not work.
But if I log in via telnet or ssh there is enigma2 process defunct.
So main question is: what can I do to avoid that state?
But if it happend - I try to restart enigma2:

killall enigma2 or pkill -9 -f enigma2

and then

/usr/bin/enigma2

But it does not start and I got:

PYTHONPATH: /usr/lib/enigma2/python
before: 1
after: 1
default pipe size of 65536 bytes detected
---- opening lame channel db
reading services (version 4)
loaded 4609 services
scanning for frontends..
[    0] opening frontend

... and it wait forever then.

Is there any solution to this? Thanks in advance

Hello,
I got brand new Dreambox DM 525 HD several days ago.
I cannot record any program from remote control. If I press the REC button I get 'not available button' sign. There is no problem from web interface.
I'm using Kingstone pendrive and it is available as /dev/sda1 and formatted by Dreambox.
I had image from 8.09.2016 built-in and now I upgraded to latest (15.10) and no progress. Is it software issue or should it work?
Thanks for help!