[VU+ Duo2] Freeze/Crashes Daily at 7PM

[vpsdo]

Hi

At 7PM Daily, my box gets stuck, just the progress icon spinning and I have to power off and on the box to make it work and it does this every day at 7PM, Please. I have upgrade from Hades to Latest Version and restored my settings.

Here logs from - /var/volatile/log/messages

Sep  4 19:00:40 vuduo2 daemon.notice ntpdate[599]: step time server 176.126.242.239 offset 1441389611.981312 sec
Sep  4 19:00:44 vuduo2 daemon.notice ntpdate[686]: adjust time server 178.79.160.57 offset 0.001824 sec
Sep  4 19:00:46 vuduo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0 
Sep  4 19:00:46 vuduo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 1  0
Sep  4 19:00:46 vuduo2 user.warn kernel: [VID]: VIDEO_PLAY 1  2 0
Sep  4 19:00:46 vuduo2 user.warn kernel: [VID]: VIDEO_CONTINUE 1  1 
Sep  4 19:00:46 vuduo2 user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 1  1 0
Sep  4 19:00:47 vuduo2 user.warn kernel: [VID]: VIDEO_STOP 0  1
Sep  4 19:00:47 vuduo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0  0
Sep  4 19:00:49 vuduo2 user.err kernel: UBI error: ubi_open_volume: cannot open device 0, volume 0, error -16
Sep  4 19:01:03 vuduo2 user.warn kernel: [AUD]: AUDIO_SET_MUTE 0 
Sep  4 19:01:03 vuduo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER -817029648 
Sep  4 19:01:03 vuduo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : amixl 0, amixr 0
Sep  4 19:01:03 vuduo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : next left volume 0, right volume 0
Sep  4 19:01:03 vuduo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
Sep  4 19:01:03 vuduo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER -817029648 
Sep  4 19:01:03 vuduo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : amixl 0, amixr 0
Sep  4 19:01:03 vuduo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
Sep  4 19:01:03 vuduo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
Sep  4 19:01:04 vuduo2 daemon.crit automount[626]: key "logs" not found in map source(s).
Sep  4 19:01:04 vuduo2 user.crit kernel: EXT4-fs error (device sda1): ext4_mb_generate_buddy:756: group 1, 854 clusters in bitmap, 856 in gd; block bitmap corrupt.
Sep  4 19:01:04 vuduo2 user.crit kernel: EXT4-fs error (device sda1): ext4_mb_generate_buddy:756: group 3, 530 clusters in bitmap, 531 in gd; block bitmap corrupt.
Sep  4 19:01:04 vuduo2 user.crit kernel: EXT4-fs error (device sda1): ext4_mb_generate_buddy:756: group 4, 1425 clusters in bitmap, 1426 in gd; block bitmap corrupt.
Sep  4 19:01:04 vuduo2 user.crit kernel: EXT4-fs error (device sda1): ext4_mb_generate_buddy:756: group 5, 27578 clusters in bitmap, 27580 in gd; block bitmap corrupt.
Sep  4 19:01:04 vuduo2 user.crit kernel: EXT4-fs error (device sda1): ext4_mb_generate_buddy:756: group 6, 1067 clusters in bitmap, 1068 in gd; block bitmap corrupt.
Sep  4 19:01:04 vuduo2 user.crit kernel: EXT4-fs error (device sda1): ext4_mb_generate_buddy:756: group 7, 734 clusters in bitmap, 735 in gd; block bitmap corrupt.
Sep  4 19:01:04 vuduo2 user.crit kernel: EXT4-fs error (device sda1): ext4_mb_generate_buddy:756: group 8, 9464 clusters in bitmap, 9465 in gd; block bitmap corrupt.
Sep  4 19:01:04 vuduo2 user.crit kernel: EXT4-fs error (device sda1): ext4_mb_generate_buddy:756: group 9, 4930 clusters in bitmap, 4931 in gd; block bitmap corrupt.
Sep  4 19:01:04 vuduo2 user.crit kernel: EXT4-fs error (device sda1): ext4_mb_generate_buddy:756: group 10, 1250 clusters in bitmap, 1251 in gd; block bitmap corrupt.
Sep  4 19:01:04 vuduo2 user.crit kernel: EXT4-fs error (device sda1): ext4_mb_generate_buddy:756: group 11, 3448 clusters in bitmap, 3450 in gd; block bitmap corrupt.
Sep  4 19:01:04 vuduo2 user.warn kernel: JBD2: Spotted dirty metadata buffer (dev = sda1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
Sep  4 19:01:04 vuduo2 user.warn kernel: JBD2: Spotted dirty metadata buffer (dev = sda1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
Sep  4 19:01:04 vuduo2 user.warn kernel: FE tune
Sep  4 19:01:05 vuduo2 user.warn kernel: [AUD]: AUDIO_SELECT_SOURCE 0 
Sep  4 19:01:05 vuduo2 user.warn kernel: [AUD]: AUDIO_SET_BYPASS_MODE 0 
Sep  4 19:01:05 vuduo2 user.warn kernel: [AUD]: AC3 downmix 0  state : 0
Sep  4 19:01:05 vuduo2 user.warn kernel: [AUD]: AUDIO_PAUSE 6827232 
Sep  4 19:01:05 vuduo2 user.warn kernel: [AUD]: AUDIO_PLAY 6827232 decoder start : 0
Sep  4 19:01:05 vuduo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0  0
Sep  4 19:01:05 vuduo2 user.warn kernel: [VID]: VIDEO_GET_SIZE src w: 1920 h:1080 display w:1920 h:1080
Sep  4 19:01:05 vuduo2 user.warn kernel: [VID]: VIDEO_GET_SIZE aspect: 1 1
Sep  4 19:01:05 vuduo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 1 
Sep  4 19:01:05 vuduo2 user.warn kernel: [VID]: VIDEO_FREEZE 6827232  0
Sep  4 19:01:05 vuduo2 user.warn kernel: [VID]: VIDEO_PLAY 6827232  5 2
Sep  4 19:01:05 vuduo2 user.warn kernel: [VID]: VIDEO_SLOWMOTION 0    1
Sep  4 19:01:05 vuduo2 user.warn kernel: [VID]: VIDEO_FAST_FORWARD 0    1
Sep  4 19:01:05 vuduo2 user.warn kernel: [VID]: VIDEO_CONTINUE 6827232  1 
Sep  4 19:01:05 vuduo2 user.warn kernel: [AUD]: AUDIO_CONTINUE 6827232 1 aph=0xcdf46a80
Sep  4 19:01:05 vuduo2 user.warn kernel: [AUD]: Mute : 0
Sep  4 19:01:05 vuduo2 user.warn kernel: [AUD]: AUDIO_CHANNEL_SELECT 0 
Sep  4 19:01:10 vuduo2 cron.err crond[675]: time disparity of 24023160 minutes detected
Sep  4 19:01:15 vuduo2 user.warn kernel: [VID]: VIDEO_STOP 1  1
Sep  4 19:01:15 vuduo2 user.warn kernel: [AUD]: AUDIO_STOP 6827232 
Sep  4 19:01:15 vuduo2 user.warn kernel: [AUD]: AUDIO_CONTINUE 6827232 0 aph=0x0
Sep  4 19:01:15 vuduo2 user.warn kernel: [AUD]: AUDIO_CONTINUE aph=0 0 0
Sep  4 19:01:15 vuduo2 user.warn kernel: FE tune
Sep  4 19:01:15 vuduo2 user.warn kernel: [AUD]: AUDIO_SELECT_SOURCE 0 
Sep  4 19:01:15 vuduo2 user.warn kernel: [AUD]: AUDIO_SET_BYPASS_MODE 1 
Sep  4 19:01:15 vuduo2 user.warn kernel: [AUD]: downmix 0 state : 0
Sep  4 19:01:15 vuduo2 user.warn kernel: [AUD]: AUDIO_PAUSE 6827232 
Sep  4 19:01:15 vuduo2 user.warn kernel: [AUD]: AUDIO_PLAY 6827232 decoder start : 0
Sep  4 19:01:15 vuduo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0  0
Sep  4 19:01:15 vuduo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0 
Sep  4 19:01:15 vuduo2 user.warn kernel: [VID]: VIDEO_FREEZE 6827232  0
Sep  4 19:01:15 vuduo2 user.warn kernel: [VID]: VIDEO_PLAY 6827232  2 2
Sep  4 19:01:15 vuduo2 user.warn kernel: [VID]: VIDEO_SLOWMOTION 0    1
Sep  4 19:01:15 vuduo2 user.warn kernel: [VID]: VIDEO_FAST_FORWARD 0    1
Sep  4 19:01:15 vuduo2 user.warn kernel: [VID]: VIDEO_CONTINUE 6827232  1 
Sep  4 19:01:15 vuduo2 user.warn kernel: [AUD]: AUDIO_CONTINUE 6827232 1 aph=0xcdfd5c00
Sep  4 19:01:15 vuduo2 user.warn kernel: [AUD]: Mute : 0
Sep  4 19:01:15 vuduo2 user.warn kernel: [VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
Sep  4 19:01:15 vuduo2 user.warn kernel: [VID]: VIDEO_GET_SIZE aspect: 1 0
Sep  4 19:05:18 vuduo2 user.notice kernel: EXT4-fs (sda1): error count: 980
Sep  4 19:05:18 vuduo2 user.notice kernel: EXT4-fs (sda1): initial error at 1426767692: mb_free_blocks:1433: block 12019584
Sep  4 19:05:18 vuduo2 user.notice kernel: EXT4-fs (sda1): last error at 1441389664: ext4_mb_generate_buddy:756
Sep  4 19:28:04 vuduo2 user.warn kernel: [VID]: VIDEO_STOP 1  1

 

[Huevos]

What is in the debug log.

 

[vpsdo]

What is in the debug log.

where is the location of the debug log?

EDIT:

if its this location, /home/root/logs/

It has not produced a debug log.

 

[DaMacFunkin]

You need to enable debug logs then reboot, after your next 7pm crash find the log and upload it.

 

[bbbuk]

It would have been better if you hadn't have upgraded from Hades to 3.2 and did a system restore.

If debug logs don't produce anything useful can I suggest you backup to usb/hdd, "timers.xml", "autotimer.xml" and "settings" files (all in "/etc/enigma2") and do a fresh usb flash manually do the following:-

Telnet in and put box to sleep using "init 4"
FTP your old "timers.xml" and "autotimer.xml" from your backup location to "/etc/enigma2" on your freshly flashed box.
From Telnet, restart box using "init 6"

This will restore your timers and autotimers.

Optionally, you can restore personalised settings with the "settings" file.

Do you have a multi-sat setup or install loads of plugins?

 

[vpsdo]

Debug Log Attached

View attachment Enigma2-05-09-2015_19-08-40.log

is 7PM a clue, I have not set anything at 7PM.
is 7PM a time for certain task set by vix coders?

 

[vpsdo]

and also Open Webif becomes unaccessable when it happens.

EDIT: i just remembered, this started happening around the same time I have disabled the Color LCD Display, Im gonna enable it and wait and see.

 

[vpsdo]

Enabling Back the Color LCD Display has fixed the problem.

Is there a solution where I can disable the LCD Display and not freeze daily at 7PM?

 

[vpsdo]

the problem came back, enabling LCD display did not fix the problem, it has skipped sunday for some reason.
Please help.

 

[vpsdo]

you might be right.

I done a text search for "1900" (for 7pm) on "timers.xml" file and found old recording timer of a certain TV program, I checked with a relative member and found out this programs shows daily at 7PM except sundays. so I have deleted the timer.xml & autotimer.xml and restored one from my Vu+ Duo in my bedroom. will have to wait for next 7PM, but im pretty confident this will fix it.

It would have been better if you hadn't have upgraded from Hades to 3.2 and did a system restore.

If debug logs don't produce anything useful can I suggest you backup to usb/hdd, "timers.xml", "autotimer.xml" and "settings" files (all in "/etc/enigma2") and do a fresh usb flash manually do the following:-

Telnet in and put box to sleep using "init 4"
FTP your old "timers.xml" and "autotimer.xml" from your backup location to "/etc/enigma2" on your freshly flashed box.
From Telnet, restart box using "init 6"

This will restore your timers and autotimers.

Optionally, you can restore personalised settings with the "settings" file.

Do you have a multi-sat setup or install loads of plugins?

 

[bbbuk]

It's weird that it's 7pm

I don't have a duo2 but when you start recording does the lcd screen on front normally display lcd icon or something for the channel it's recording or another indicator that requires your lcd screen?

I wonder if a recording around that time is related to, albeit indirectly, this problem?