Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...
[VU+ Duo2] Spinning Vix
- Thread starter Fuzzy
- Start date
Well although when I first added these two timers I also got vix spinner so I flashed back to backup done a little earlier today (ie a clean slate) I then enabled debug mode and rebooted but this time around I couldn't re-create vix spinner.
This/these bug(s) are a mystery...
the spinning vix logo pretty much implies that the CPU is busy (too busy to do anything else).
Therefore it doesn't matter how many times you report you've had the spinner, you need to:
post debug logs
otherwise this won't go anywhere.
I'm running a duo2 and am not suffering with a 'spinning vix'.
Along with a debug log, it's also worth telnetting to the box, running the
command (or htop if you've installed it) and check which process is using the CPU.
Note the processs details and Id, and post this along with the debug log, and also then run
This will list the threads of the process consuming the CPU and might also help to give some clue.
Without some or all of this it's impossible to guess what the cause may be, or as I said previously, whether everyone has the same issue or different ones.
So please, help us to help you!
Therefore it doesn't matter how many times you report you've had the spinner, you need to:
post debug logs
otherwise this won't go anywhere.
I'm running a duo2 and am not suffering with a 'spinning vix'.
Along with a debug log, it's also worth telnetting to the box, running the
Code:
topNote the processs details and Id, and post this along with the debug log, and also then run
Code:
top -H -p <ProcessID>Without some or all of this it's impossible to guess what the cause may be, or as I said previously, whether everyone has the same issue or different ones.
So please, help us to help you!
I'd recommend using putty.
Create a telnet connection to the ip address of your e2 box, log in with the root user and password, and from there you can run the commands.
Obviously be careful as you can run any Linux command here, so make sure you know what the commands will do if you're not familiar, and don't just run commands without understanding the full ramifications
(I appreciate this isn't something the novice user might be comfortable with!)
Code:
http://www.chiark.greenend.org.uk/~sgtatham/putty/Obviously be careful as you can run any Linux command here, so make sure you know what the commands will do if you're not familiar, and don't just run commands without understanding the full ramifications
(I appreciate this isn't something the novice user might be comfortable with!)
@Pembo,
I did that when I had my spinning vix.
The overall CPU usage remained between 0 to 30% during the spinning vix and the top two processes using most cpu (alternate between the two) was between "top" and "mgcamd 1.38".
I don't believe mgcamd being issue itself for two reasons because one that hasn't itself changed in a very long time and two, even now whilst it's not spinning the same two processes are hogging the most cpu (although the overall CPU usage again remains between 0 and 30%).
Basically, I can't see any difference when running "top" either during the spinning vix or when it's running normally!
I did that when I had my spinning vix.
The overall CPU usage remained between 0 to 30% during the spinning vix and the top two processes using most cpu (alternate between the two) was between "top" and "mgcamd 1.38".
I don't believe mgcamd being issue itself for two reasons because one that hasn't itself changed in a very long time and two, even now whilst it's not spinning the same two processes are hogging the most cpu (although the overall CPU usage again remains between 0 and 30%).
Basically, I can't see any difference when running "top" either during the spinning vix or when it's running normally!
Last edited:
Thanks bbbuk - I knew you would have done this already 
I just want everyone who is complaining about this to start helping us to diagnose the issues more, as it could be a multitude of different things! I know I personally had the spinning vix originally on hades and this was to do with a corrupt epg cache, and this was caused pretty much by a repetitive loop of errors showing in the debug log (not a crash dump!). After fixing this, it had not reoccurred.
Also the timers seem to be of some suspicion here based on others findings.
I just want everyone who is complaining about this to start helping us to diagnose the issues more, as it could be a multitude of different things! I know I personally had the spinning vix originally on hades and this was to do with a corrupt epg cache, and this was caused pretty much by a repetitive loop of errors showing in the debug log (not a crash dump!). After fixing this, it had not reoccurred.
Also the timers seem to be of some suspicion here based on others findings.
Reports like this are pretty useless.
Box used, tuner & EPG setup, debug logs...
I re-enabled debug logs and purposely went to EPG and scrolled around things and selected a programme to record (as autotimer). This time, I got the spinning vix again (and still now as I type this).
Attach are debug logs and piped output of "top". Top, from what I can see, only shows an overall cpu usage of between 0 and 30% (same as my post yesterday).
View attachment Enigma2-01-01-1970_01-00-15.txt
View attachment to.txt
Looking at debug logs, it looks like it added the autotimer fine but then it started processing other events in my autotimer already (like polling the autotimer again) and then spinning vix. I noticed I have events not found in epgcache errors!
I'm no expert but that to me looking like that this time the spinning vix happened whilst it was processing (ie re-populating timers from autotimers)?
My setup is Solo2 (clean flash with no restore of settings just manually added autotimer.xml file). Sky 28.2 epg data obtained via CrossEPG/OpenTV.
Attach are debug logs and piped output of "top". Top, from what I can see, only shows an overall cpu usage of between 0 and 30% (same as my post yesterday).
View attachment Enigma2-01-01-1970_01-00-15.txt
View attachment to.txt
Looking at debug logs, it looks like it added the autotimer fine but then it started processing other events in my autotimer already (like polling the autotimer again) and then spinning vix. I noticed I have events not found in epgcache errors!
Code:
action -> ColorActions green
[SKIN] processing screen AutoTimerEditor:
[SKIN] processing screen SetupSummary:
KEY: 399 GREEN
action -> SetupActions save
[AutoTimer] No changes in configuration, won't parse
[AutoTimer] No changes in configuration, won't parse
< 194.536464> [eEPGCache] event 001c not found in epgcache
< 194.537893> [eEPGCache] event 02f2 not found in epgcache
< 194.539419> [eEPGCache] event 0719 not found in epgcache
< 194.540854> [eEPGCache] event 0262 not found in epgcache
< 194.542326> [eEPGCache] event e9aa not found in epgcache
< 194.544295> [eEPGCache] event 07e1 not found in epgcache
< 194.545828> [eEPGCache] event 07aa not found in epgcache
< 194.653960> [eEPGCache] lookup events with 'Coronation Street' in title (ignore case)
KEY: 399 GREEN
[AutoTimer] Skipping timer because it has not changed.
[AutoTimer] Skipping timer because it has not changed.
[AutoTimer] Skipping timer because it has not changed.
[AutoTimer] Skipping timer because it has not changed.
[AutoTimer] Skipping timer because it has not changed.
< 195.601996> [eEPGCache] lookup events with 'Inside Manchester's Midland Hotel' in title (ignore case)
KEY: 106 RIGHT
action -> DirectionActions right
< 199.506266> [gRC] main thread is non-idle! display spinner!I'm no expert but that to me looking like that this time the spinning vix happened whilst it was processing (ie re-populating timers from autotimers)?
My setup is Solo2 (clean flash with no restore of settings just manually added autotimer.xml file). Sky 28.2 epg data obtained via CrossEPG/OpenTV.
Last edited:
I too have been having this problem with a Mutant 2400 since updating to Hades 11. The debug log does not seem to have anything in it to help
as the log itself seems not to be updated as soon as the spinning VIX appears and the box then "locks up". I have to power off,
It definitely seems to be EPG or Autotimer related as it only seems to happen when I am browsing the EPG to add autotimers or timers - all seems
to work fine as long as I am not doing anything with the timers.
Previously was using OpenPLI on the Dreambox DM8000 and had been very impressed with the Mutant2400 using Vix until this ongoing problem.
More than willing to help with uploading debug logs but seems pointless if no data gets stored the log as soon as the problem arises.
as the log itself seems not to be updated as soon as the spinning VIX appears and the box then "locks up". I have to power off,
It definitely seems to be EPG or Autotimer related as it only seems to happen when I am browsing the EPG to add autotimers or timers - all seems
to work fine as long as I am not doing anything with the timers.
Previously was using OpenPLI on the Dreambox DM8000 and had been very impressed with the Mutant2400 using Vix until this ongoing problem.
More than willing to help with uploading debug logs but seems pointless if no data gets stored the log as soon as the problem arises.
Ok another spinner shortly after adding an autotimer.... View attachment Enigma2-01-01-1970_01-00-15.log
This debug log looks similar to my other one and another forum members log I looked at. Spinner seems to happen around the time it's polling.
I'm going to try something.....
UPDATE: I disabled polling within menu for autotimer and restarted box and still I had a spinner shortly after adding a autotimer. Looking at attached log for this, the last thing it was doing was polling my existing autotimer which I would have thought it wouldn't after me disabling the polling.
View attachment Enigma2-afterapparentlyturningoffpolling.log
I shall do one more last test....
UPDATE 2:
I put box to sleep and deleted actual autotimer.xml and timer.xml files and then once box was up and running I added about 8 autotimers without a problem. After adding the 8th autotimer I got bored of doing that so I just started scrolling around epg and then hey presto spinner again. Log attached of this...
View attachment Enigma2-afterwipingautotimers.log
Same as other logs... The last thing it's doing before spinner is polling autotimers. At this point, with no autotimers it looks like I got a lot further before spinner and point of note is that I still had polling set to disabled from menu.
This debug log looks similar to my other one and another forum members log I looked at. Spinner seems to happen around the time it's polling.
I'm going to try something.....
UPDATE: I disabled polling within menu for autotimer and restarted box and still I had a spinner shortly after adding a autotimer. Looking at attached log for this, the last thing it was doing was polling my existing autotimer which I would have thought it wouldn't after me disabling the polling.
View attachment Enigma2-afterapparentlyturningoffpolling.log
I shall do one more last test....
UPDATE 2:
I put box to sleep and deleted actual autotimer.xml and timer.xml files and then once box was up and running I added about 8 autotimers without a problem. After adding the 8th autotimer I got bored of doing that so I just started scrolling around epg and then hey presto spinner again. Log attached of this...
View attachment Enigma2-afterwipingautotimers.log
Same as other logs... The last thing it's doing before spinner is polling autotimers. At this point, with no autotimers it looks like I got a lot further before spinner and point of note is that I still had polling set to disabled from menu.
Last edited:
Ran out of time before editing ones own post is disabled.
Now i'm going to flash clean flash with no restores again but this time without manually copying autotimer.xml over. I shall use default skin.
I'll post back...
So further to my last few posts, I did a clean usb flash with no restore of settings. Kept everything as default except just setup epg for 28.2 via CrossEPG/OpenTV and setup ABM for my local area. These settings are what I always do. Installed no plugins whatsoever. Prior to this I did remove crossepg files inc epg data from internal hdd (and chose option to delete epg data also).
I managed to get add a few autotimers before spinning vix returned. Attached is log...
View attachment Enigma2-reshinstallhades11.log
As with other logs, spinner happens whilst polling autotimers. "Top" during spinner was just top itself and "init" again overall cpu usage was between 0 to 30%.
I managed to get add a few autotimers before spinning vix returned. Attached is log...
View attachment Enigma2-reshinstallhades11.log
As with other logs, spinner happens whilst polling autotimers. "Top" during spinner was just top itself and "init" again overall cpu usage was between 0 to 30%.
abu baniaz
Moderator
Can you try with a fresh flash of Hades 010 please? (009 seems fine).
Similar threads
