Bugzilla – Bug 4804
player reboots each 20 seconds when buffering
Last modified: 2012-02-27 17:33:09 UTC
After upgrading to the last firmware coming with Slimserver 6.5.1 my player reboots each 20 sec or so. I tried connecting to the wired and wireless and same problem. AlienBBC is the only that I can play. I connected the player straight to the cable modem and still same problem. I think is something wrong with the buffer. I went back to slimserver 6.3.1 firmware version and the problem got fixed.
Eliad, SlimServer 6.3.1 included firmware 55. Firmware 72 is with SlimServer 6.5.1. Firmware 76 is with the current 6.5.2 nightly. Would you try installing the nightly and see if you still have the problem? You can get it at http://www.slimdevices.com/dev_nightly.html
I tried some more experimentation with the firmware. I tried the last nightly with firmware 76. It works better. Now I can listen to my slimserver songs. On the internet radio after a couple of minutes my slimbox it would reboot. I think it happens when the buffer gets empty. Now I am playing with firmware 64 (slimserver 6.5.0) this one seems to behave better, no interuptions so far. Only problem is that it doesn't connect to Live365 stations. Maybe is something wrong with slimserver 6.5.0. Eliad
Eliad, are you still experiencing problems? There have been some issues on and off with Live365 sites, but I think they are all resolved at the moment.
I have tried different firmaware versions to see which ones works. The last one that comes with slimserver 6.5.2 (i believe is version 82) makes the slimbox reboot about about 10 sec of playing a song either from slimserver library or from squeezenetwork. Same thing happens with the firmware coming with slimserver 6.5.1. The firmware coming with 6.5.0 does not make the slimbox reboot every 10 seconds or so. This version 64 does have some issues with internet radio though. I am quite frustrated about this. Eliad
Are you still experiencing these issues? We have not been able to reproduce your issues. Our support group suggests you contact them regarding a possible RMA of the product.
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version. If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.