Vu+ Duo crashing after timeshift/FF

[edanto]

I've recently updated to 2.3 (new bootloader/new image), have updated VIX, and while most things are going well, it's crashed a couple of times after fast forwarding post timeshift.

Situation has been that it's been on pause for perhaps 10/15 mins, and then I start to play it again. Comes to an ad break, I Fast Forward and then press play or pause ..... all crashes, spinning logo. This has only happened 3 times since Saturday, and it's worked fine at least 10 times.

I don't seem to have a crashlog for those crashes; maybe I should have left the logo spinning longer, it was left for about 2/3 minutes before I flicked the switch.

There are only 2 crashlogs from 2012 in the hdd folder. Both are attached to this, but from the date stamp I think they are crashes from a few days ago when it was crashing after doing a sat scan.

Is there any more information that I can provide to make it easier to troubleshoot?

 

[edanto]

Damn, happened again. Spinning logo as we speak. Is there anyway I can get info about what's crashing it, or what process has hung the box?

(there's no response to anything when pressing buttons on the remote)

 

[edanto]

Is there some way I can log into the box and run the 'top' command? (bear with me, I've just discovered the top command through google!)

There is indeed - and here are the results. (if anyone is as n00b as me and want to know how to do this, just telnet to the IP of your box, log in and at the # type 'top' and hit enter.


Mem: 135600K used, 2680K free, 0K shrd, 8920K buff, 42604K cached
CPU: 2% usr 6% sys 0% nic 77% idle 11% io 0% irq 1% sirq
Load average: 0.56 0.78 0.89 3/92 823
PID PPID USER STAT VSZ %MEM %CPU COMMAND
483 477 root S 144m 107% 7% /usr/bin/enigma2
460 1 root S 18588 13% 2% /usr/bin/usbtunerhelper
100 2 root SW 0 0% 1% [sched_high]
822 820 root R 3264 2% 0% top
819 417 root S 3268 2% 0% telnetd
448 1 root S 14272 10% 0% /usr/sbin/smbd
450 448 root S 14272 10% 0% /usr/sbin/smbd
451 1 root S 7044 5% 0% /usr/sbin/nmbd
474 1 avahi S 3620 3% 0% avahi-daemon: running [vuduo.local]
475 474 avahi S 3500 3% 0% avahi-daemon: chroot helper
417 1 root S 3312 2% 0% /usr/sbin/inetd
820 819 root S 3260 2% 0% -sh
478 1 root S 3012 2% 0% /sbin/getty 38400 tty1
456 1 root S 2948 2% 0% /sbin/klogd -n
454 1 root S 2948 2% 0% /sbin/syslogd -n -O /var/log/messages
415 1 root S 2948 2% 0% /usr/sbin/crond -c /etc/cron/crontabs
477 1 root S 2948 2% 0% /bin/sh /usr/bin/enigma2.sh
403 1 messageb S 2832 2% 0% /usr/bin/dbus-daemon --system


Looks like I'm struggling with memory. What's the solution for that? Is there an equivalent of a page file I can set up?

 

[zola25]

If you want to setup a swap file push the blue button then pick Vix and at the bottom of the new menu that opens is the swap manager.

 

[edanto]

Thanks, I've set that to 96MB of the HD, hopefully it'll make a difference.

Is the swap file a common thing to activate? It kindof sounds like a useful thing!

 

[BadBoy]

let me know how you get in as the same happened to me but I have an et9k

Sent from my Galaxy Nexus using Tapatalk

 

[zola25]

If you have a usb stick it is better to use that so your disk does not spin up and down if the swap file is used(same goes for picons)

 

[tsx]

Snap, same here! Might give it a quick go tonight.

 

[zola25]

Forgot to add make sure you are using the latest drivers with the fix for the recording bug ftp them to lib >modules >3.1.1 >extra you will see 3 files in there make a backup of those and copy the ones from the archive overwriting the original ones, then reboot the receiver.
These only work on the new linux 3.1.1 kernel ONLY

 

[edanto]

Thanks.

How do I know if I have the new 3.1.1 kernel - I have not done anything to upgrade the kernel and have no idea if it is part of the VIX image, or a completely different thing. I see this thread (http://www.world-of-satellite.com/s...nux-3-1-1)-25-12-2011&highlight=kernel+3.1.1) mentions the 3.1.1 kernel and I have updated completely to VIX 2.3, so I think that means that the kernel is at 3.1.1.

But I have done a software upgrade from inside VIX, would that not have brought down any fixes available?

 

[zola25]

To find out what version you are running push the menu button then information then about then you can see your version number build kernel etc.
The latest to driver release is not on the online update unless i am mistaken