View Full Version : Bootloop with timers.xml when reboot DUO after adding timers.
Bootloop with timers.xml when reboot DUO after adding timers.
Attached two log files from different dates and timers.xml file. Taking timers.xml file away it boots normal.
16960
16961
16962
Same BSOD log with build 112
16963
I have moved this into it's own thread. Please remember that when posting a potential bug if you post it in the release / discussion thread it can easily get lost and overlooked in the jumble of other posts.
This way with it's own thread it is more visible and more likely to be picked up by the team.
Rob van der Does
20-05-12, 07:58
Bootloop with timers.xml when reboot DUO after adding timers.
Attached two log files from different dates and timers.xml file. Taking timers.xml file away it boots normal.
Same BSOD log with build 112
16963
That probably means the file is corrupt or has entries that are not compatible with your present setup.
Best start to make new timers from scratch.
I have moved this into it's own thread. Please remember that when posting a potential bug if you post it in the release / discussion thread it can easily get lost and overlooked in the jumble of other posts.
This way with it's own thread it is more visible and more likely to be picked up by the team.
Yes thanks, it was on my mind to create new thread :)
That probably means the file is corrupt or has entries that are not compatible with your present setup.
Best start to make new timers from scratch.
First .log is with old timers.xml which has followed me years and years and another .logs are timers which are made from scratch with OpenVIX 2.4
Rob van der Does
20-05-12, 08:08
Are the recording-locations in the timers really available in your present setup?
I copied my own timers.xml and autotimers.xml files from a 2.3 version image to a early 2.4 image without problems. although i have not done it for the last few builds. I did however copy my autotimers.xml file between 2.4-96 and 2.4-101 without a problem.
Are the recording-locations in the timers really available in your present setup?
What do you mean about recording-locations?
All timers in this timers.xml are added via EPG with my current setup.
What do you mean about recording-locations?
All timers in this timers.xml are added via EPG with my current setup.
I will try it again from scratch.
what he means is have you changed the location the recording's are saved to ? for example if you were previously saving the recordings to a NAS drive is that drive still present and mounted correctly ( that was only a example ).
what he means is have you changed the location the recording's are saved to ? for example if you were previously saving the recordings to a NAS drive is that drive still present and mounted correctly ( that was only a example ).
ah, ok. no i havent change location, I all ways use default location. Recordings with and without timers do work, until i reboot :)
AutoTimers as well, those can be there before reboot.
Then is is possible there may be some form of corruption in the .xml files due to their age that is causing the BSoD, try setting them up form new within the image it self instead of copying over a existing file.
Checked openpli forum and looks like im not alone and there is some fix for it?
http://openpli.org/forums/topic/23028-timers-bug-latest-build-sat-24th-mar-2012-vuduo/page__hl__timers
Then is is possible there may be some form of corruption in the .xml files due to their age that is causing the BSoD, try setting them up form new within the image it self instead of copying over a existing file.
My current timers.xml (which also causes BSOD loop) are made with OpenVIX 2.4 directly from standard EPG :)
Rob van der Does
20-05-12, 10:06
Checked openpli forum and looks like im not alone and there is some fix for it?
hxxp://openpli.org/forums/topic/23028-timers-bug-latest-build-sat-24th-mar-2012-vuduo/page__hl__timers
If it were the same problem, the same solution would have solved this as well.
Checked openpli forum and looks like im not alone and there is some fix for it?
http://openpli.org/forums/topic/23028-timers-bug-latest-build-sat-24th-mar-2012-vuduo/page__hl__timers
please in future code your links, i have no problem with you linking to the Pli forum but code them, if your unsure how to code them just ask.
If it were the same problem, the same solution would have solved this as well.
True, this another fix was from 24 of March. So it is something else.
And it happen again, made new timer list from scratch with 2.4 and it crash when surfing on channel list and BSoD loop started.
Newest log attached.
16991
And it happen again, made new timer list from scratch with 2.4 and it crash when surfing on channel list and BSoD loop started.
Newest log attached.
16991
please post a screen sot of the timer entry screen, seems to be an issue with the repeat part of the screen.
also please post your mount location where recording are saving to. is it using symlinks ?
please post a screen sot of the timer entry screen, seems to be an issue with the repeat part of the screen.
also please post your mount location where recording are saving to. is it using symlinks ?
Here you go.
16996
16997
Mount has done with Network Browser (If i remember right. Normally I do mount manually with remote control), mount point has been the same maybe 5 years or more.
root@vuduo:~# mount
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,sync,relatime)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,size=64k,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sda1 on /media/usb type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=002 2,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
usbfs on /proc/bus/usb type usbfs (rw,relatime)
tmpfs on /var/volatile type tmpfs (rw,relatime)
192.168.1.6:/mnt/video/dream/ on /media/net/nas type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen =255,soft,proto=tcp,port=65535,timeo=14,retrans=3, sec=sys,local_lock=none,addr=192.168.1.6)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
192.168.1.6:/mnt/video/dream/ on /media/net/NAS type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen =255,soft,proto=tcp,port=65535,timeo=14,retrans=3, sec=sys,local_lock=none,addr=192.168.1.6)
Here you go.
16996
16997
Mount has done with Network Browser (If i remember right. Normally I do mount manually with remote control), mount point has been the same maybe 5 years or more.
root@vuduo:~# mount
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,sync,relatime)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,size=64k,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sda1 on /media/usb type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=002 2,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
usbfs on /proc/bus/usb type usbfs (rw,relatime)
tmpfs on /var/volatile type tmpfs (rw,relatime)
192.168.1.6:/mnt/video/dream/ on /media/net/nas type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen =255,soft,proto=tcp,port=65535,timeo=14,retrans=3, sec=sys,local_lock=none,addr=192.168.1.6)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
192.168.1.6:/mnt/video/dream/ on /media/net/NAS type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen =255,soft,proto=tcp,port=65535,timeo=14,retrans=3, sec=sys,local_lock=none,addr=192.168.1.6)
i need to see the actual timer entry screen not the timer list screen.
also from what i can see from your mounts, you have the same mount in 2 locations, why ?, can you remove one please and see if it helps.
192.168.1.6:/mnt/video/dream/ on /media/net/nas
192.168.1.6:/mnt/video/dream/ on /media/net/NAS
i need to see the actual timer entry screen not the timer list screen.
Second picture on my previous post is not what you need?
http://www.world-of-satellite.com/attachment.php?attachmentid=16997&d=1337574845
also from what i can see from your mounts, you have the same mount in 2 locations, why ?, can you remove one please and see if it helps.
192.168.1.6:/mnt/video/dream/ on /media/net/nas
192.168.1.6:/mnt/video/dream/ on /media/net/NAS
That one is my bad, iŽll try remove "nas" and leave "NAS" as it is acting hdd.
root@vuduo:/media# ls -l
lrwxrwxrwx 1 root root 14 May 18 17:52 hdd -> /media/net/NAS
drwxr-xr-x 4 root root 288 May 18 17:52 net
drwxrwxrwx 4 root root 4096 May 21 07:34 usb
root@vuduo:/media/net# ls -l
drwxrwxrwx 11 1000 messageb 4096 May 21 04:02 NAS
drwxrwxrwx 11 1000 messageb 4096 May 21 04:02 nas
root@vuduo:/media/net#
Rob van der Does
21-05-12, 11:10
During testing periods I had several times issues like this: all were down to wrong mounts ('left overs' from previous tests).
During testing periods I had several times issues like this: all were down to wrong mounts ('left overs' from previous tests).
Ok, sounds promising. Maybe enigma2 do not handle correct capitals and lowercase then, if it will give this weird behaviour with two mounts where another one is capitals and second with lower case.
Another mount is now removed and testing continues :)
Rob van der Does
21-05-12, 11:58
Linux (and hence Enigma) is indeed case-sensitive.
Linux (and hence Enigma) is indeed case-sensitive.
Yeah.
umm, another mount was some left over to fstab, mount manager on Network was only showing NAS as mount, so i deleted nas line from fstab.
Rob van der Does
21-05-12, 16:21
umm, another mount was some left over to fstab, mount manager on Network was only showing NAS as mount, so i deleted nas line from fstab.
Maybe it's best to start all over: delete automount and fstab (after stopping E2), and make all mounts again. Better be safe than....
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.