PDA

View Full Version : [VU+ Solo2] Box hangs after reboot - no gui



lfc84
30-06-14, 18:23
The Solo2 was running fine unitl I created a powertimer. I created a powertimer to reboot the box daily at 05:00, and then do nothing following the reboot.

I created another power timer to reboot the box once at 17:34 today and do nothing following reboot. At 17:34 a timer counting down from 180 seconds popped up. I hit ok and the box rebooted.

It has now hung on reboot and when I hit a key on the remote I get the "vix" spinning ont he top left corner.

Here's some output which may help ?


root@vusolo2:/etc/enigma2# tail -n 60 /var/log/messages
Jun 30 18:11:07 vusolo2 user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 1 1 0
Jun 30 18:11:08 vusolo2 user.warn kernel: [VID]: VIDEO_STOP 0 1
Jun 30 18:11:08 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0
Jun 30 18:11:08 vusolo2 user.err kernel: [LCD]: unknown cmd 0x1015
Jun 30 18:11:12 vusolo2 user.warn kernel: [AUD]: HDMI Max Audio PCM Channels=2
Jun 30 18:11:13 vusolo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0
Jun 30 18:11:13 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 1
Jun 30 18:11:13 vusolo2 user.warn kernel: [VID]: VIDEO_PLAY 1 2 0
Jun 30 18:11:13 vusolo2 user.warn kernel: [VID]: VIDEO_CONTINUE 1 1
Jun 30 18:11:13 vusolo2 user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 1 1 0
Jun 30 18:11:13 vusolo2 user.warn kernel: [VID]: VIDEO_STOP 0 1
Jun 30 18:11:13 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0
Jun 30 18:11:13 vusolo2 user.err kernel: [LCD]: unknown cmd 0x1015
Jun 30 18:11:17 vusolo2 user.warn kernel: [AUD]: HDMI Max Audio PCM Channels=2
Jun 30 18:11:18 vusolo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0
Jun 30 18:11:18 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 1
Jun 30 18:11:18 vusolo2 user.warn kernel: [VID]: VIDEO_PLAY 1 2 0
Jun 30 18:11:18 vusolo2 user.warn kernel: [VID]: VIDEO_CONTINUE 1 1
Jun 30 18:11:18 vusolo2 user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 1 1 0
Jun 30 18:11:18 vusolo2 user.warn kernel: [VID]: VIDEO_STOP 0 1
Jun 30 18:11:18 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0
Jun 30 18:11:18 vusolo2 user.err kernel: [LCD]: unknown cmd 0x1015
Jun 30 18:11:22 vusolo2 user.warn kernel: [AUD]: HDMI Max Audio PCM Channels=2
Jun 30 18:11:23 vusolo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0
Jun 30 18:11:23 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 1
Jun 30 18:11:23 vusolo2 user.warn kernel: [VID]: VIDEO_PLAY 1 2 0
Jun 30 18:11:23 vusolo2 user.warn kernel: [VID]: VIDEO_CONTINUE 1 1
Jun 30 18:11:23 vusolo2 user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 1 1 0
Jun 30 18:11:23 vusolo2 user.warn kernel: [VID]: VIDEO_STOP 0 1
Jun 30 18:11:23 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0
Jun 30 18:11:24 vusolo2 user.err kernel: [LCD]: unknown cmd 0x1015
Jun 30 18:11:27 vusolo2 user.warn kernel: [AUD]: HDMI Max Audio PCM Channels=2
Jun 30 18:11:28 vusolo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0
Jun 30 18:11:28 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 1
Jun 30 18:11:28 vusolo2 user.warn kernel: [VID]: VIDEO_PLAY 1 2 0
Jun 30 18:11:28 vusolo2 user.warn kernel: [VID]: VIDEO_CONTINUE 1 1
Jun 30 18:11:28 vusolo2 user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 1 1 0
Jun 30 18:11:29 vusolo2 user.warn kernel: [VID]: VIDEO_STOP 0 1
Jun 30 18:11:29 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0
Jun 30 18:11:29 vusolo2 user.err kernel: [LCD]: unknown cmd 0x1015
Jun 30 18:11:32 vusolo2 user.warn kernel: [AUD]: HDMI Max Audio PCM Channels=2
Jun 30 18:11:33 vusolo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0
Jun 30 18:11:33 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 1
Jun 30 18:11:33 vusolo2 user.warn kernel: [VID]: VIDEO_PLAY 1 2 0
Jun 30 18:11:33 vusolo2 user.warn kernel: [VID]: VIDEO_CONTINUE 1 1
Jun 30 18:11:33 vusolo2 user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 1 1 0
Jun 30 18:11:34 vusolo2 user.warn kernel: [VID]: VIDEO_STOP 0 1
Jun 30 18:11:34 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0
Jun 30 18:11:34 vusolo2 user.err kernel: [LCD]: unknown cmd 0x1015
Jun 30 18:11:38 vusolo2 user.warn kernel: [AUD]: HDMI Max Audio PCM Channels=2
Jun 30 18:11:39 vusolo2 daemon.info init: Id "gui" respawning too fast: disabled for 5 minutes
Jun 30 18:16:40 vusolo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0
Jun 30 18:16:40 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 1
Jun 30 18:16:40 vusolo2 user.warn kernel: [VID]: VIDEO_PLAY 1 2 0
Jun 30 18:16:40 vusolo2 user.warn kernel: [VID]: VIDEO_CONTINUE 1 1
Jun 30 18:16:40 vusolo2 user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 1 1 0
Jun 30 18:16:40 vusolo2 user.warn kernel: [VID]: VIDEO_STOP 0 1
Jun 30 18:16:40 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0
Jun 30 18:16:41 vusolo2 user.err kernel: [LCD]: unknown cmd 0x1015
Jun 30 18:16:44 vusolo2 user.warn kernel: [AUD]: HDMI Max Audio PCM Channels=2
root@vusolo2:/etc/enigma2#

lfc84
30-06-14, 18:37
some more info..




root@vusolo2:/etc# more inittab
# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.
id:3:initdefault:

# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS

# What to do in single-user mode.
~~:S:wait:/sbin/sulogin

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin

gui:3:respawn:/usr/bin/enigma2.sh
x:1:once:/tmp/image_restore.sh

lfc84
30-06-14, 19:27
i flashed with a backup from the start of the month and fixed the issues

lfc84
30-06-14, 20:34
OK, the plot thickens....

I reverted to a backup taken on the 4th June and everything was working ok. Rebooted. Still all ok.

Then I enabled a weekend image backup. Rebooted and I got the same problems as outlined above.

Definitely an issue with the scheduler imo

I'll revert to 4 June backup and not add any backup or reboot schedule. That will fix the problem

lfc84
03-07-14, 16:11
Done a bit more investigation on this and it would appear to be a corruption with the kernel.

I noticed that included in the backups is some kernel files.

I've decided to update to the latest version so I will see how that goes.