2010-09-06, 14:54
Dear everyone,
Just to post some update on my situation.
To start with: hibernation and al that green stuff is turned OFF on my xbmc and NAS as well.
So this cannot have any influence on the problem analysis. Everyone can be sure about the fact that this is not a attempt-to-resume-hardware issue.
So I've tried the same thing on protocol: NFS instead of samba, with auto mount solution.
(allowing xbmc onto NFS on my nas, and changing my automount settings on the xbmc)
Take into account that *everything* that has a relation to a samba share needs to be removed from your xbmc box: in your favourites, playlists, library (music&movies) etc etc. Check out the sources.xml also to clean unneeded remnants.
Result:
I had the impression that it was faster and more stable. Also the hangups were gone.
But today:
I've done an intensive extract (about 45min!) from my NAS.
Result:
A xbmc hangup that was already running stable for quite some days again, it played music and many movies without any problems.
SSH was still working, and killing xbmc.bin process did not change the state of the machine: the hdd led kept happily shining.
Conclusion:
This hangup problem looks a network-resource-unavailability problem.
What I do not understand is that xbmc needs to poll network resources for some reason?!
Anyone an idea?
Just to post some update on my situation.
To start with: hibernation and al that green stuff is turned OFF on my xbmc and NAS as well.
So this cannot have any influence on the problem analysis. Everyone can be sure about the fact that this is not a attempt-to-resume-hardware issue.
So I've tried the same thing on protocol: NFS instead of samba, with auto mount solution.
(allowing xbmc onto NFS on my nas, and changing my automount settings on the xbmc)
Take into account that *everything* that has a relation to a samba share needs to be removed from your xbmc box: in your favourites, playlists, library (music&movies) etc etc. Check out the sources.xml also to clean unneeded remnants.
Result:
I had the impression that it was faster and more stable. Also the hangups were gone.
But today:
I've done an intensive extract (about 45min!) from my NAS.
Result:
A xbmc hangup that was already running stable for quite some days again, it played music and many movies without any problems.
SSH was still working, and killing xbmc.bin process did not change the state of the machine: the hdd led kept happily shining.
Conclusion:
This hangup problem looks a network-resource-unavailability problem.
What I do not understand is that xbmc needs to poll network resources for some reason?!
Anyone an idea?
