Bugzilla – Bug 3093
Firmware 35 hangs
Last modified: 2008-12-15 11:56:50 UTC
I installed the 3/02 6.2.2 with firmware 35. After running for some period of time, the SB hangs. It still claims to have a wireless signal, but it can no longer be pinged, and it will not connect. A power cycle will unhang it. It seems to get into this state fairly reliable if I stop the server and restart it. I am running a Linksys WRT54G V2 wireless router in B/G mode, 128 bit WEP security. I have reverted to 33, but would be happy to do any experiments needed to resolve this.
(In reply to comment #0) I experienced exactly the same thing yesterday after upgrading to 02/03 (2 March) nightly for 6.2.2. and firmware 35 for the first time. SB hangs, often in the middle of a song. Unplugging the power was the only way to reset (if I killed Slimserver, the SB menu stayed up in the "hung" position. Running SS on Linux (Buffalo Linkstation, open firmware), with a Belkin pre-N v2000, g only network, WPA encryption - because of this couldn't capture any info in the Event viewer. Downgraded to an older nightly v33, running again with no problems. Is there any way to debug this issue with my setup ?
for the record, this is at least indirectly related to bug3080, which was duped as a post to the forum, and this bug report then created in response to another post in that same thread. bug3080 refers to FW35 using 6.5, this one is FW35 in 6.2.2
(In reply to comment #2) > for the record, this is at least indirectly related to bug3080, which was duped > as a post to the forum, and this bug report then created in response to another > post in that same thread. bug3080 refers to FW35 using 6.5, this one is FW35 > in 6.2.2 For the avoidance of any doubt, the behaviour I am experiencing does not appear to be related to the Time/Date Screensaver (as at least part of bug3080 appears to be). Slimserver simply hangs in the middle of a song (with the spectrum analyser screensaver) or whilst streaming radio, without any specific input from the remote or otherwise. I wasn't able to force the "crash" (for want of a better word) - inputting lots of commands didn't cause it. I will try upgrading to the latest nightly and see if I can pin the behaviour down better than currently - conscious there's not much information to go on here.
chris, can you help me out with this one too?
This morning, both my SB3 boxes were hung as described in this bug. They both are running 33, so its not a 35 bug. I still believe that 35 increases the occurance rate, but that's hard to prove. Detailed description of hung state; Screen blank. Trying to power on or hit most keys causes sequence Waking up server, followed by connecting to server, followed after a while by blank screen. Going to view current settings shows normal entries, and a normal signal strength which is varying over time. SB3 cannot be pinged. My wireless router lists it as inactive in the wireless clients list. (I'm using MAC filtering, so the router knows about it). Holding power down resets things, and the SB3 connects and operates correctly. While I was entering this, I had left the SB3 in the show settings mode, I believe on the firmware number line. When I went back to it and pressed the power key, it connected and displayed the power off screen saver (time). So the situation sometimes clears itself. I've seen this before, always after being in the show settings page for a while. Wild guess - the reconnect to server logic gets hung in a loop which doesn't let the underlying stack operate. This is a completely made up idea, with now knowledge of the firmware design. But you might look at what would be different when in the show settings page.
*** Bug 3080 has been marked as a duplicate of this bug. ***
I am starting to suspect that this is related to G to B switching in the network. I was running a B/G mixed mode main access point, and a B only extra access point. As I've noted in 3132 the SB3 seems to like to switch to the secondary even though its weaker. In doing so, it was (?) switching from G to B. My laptop is also B only, and others have suggested that turning on a B only device might switch the router to B only mode. (I don't know that this is true). I have run both access point in B mode for several days and have not seen the hang that this bug reports. As 3132 reports, the SB3 does switch between access points, and has some trouble doing that. But it does not hang.
(In reply to comment #7) My network is g-only and the hang seemed to occur intermittently. There was also nothing on my network that could have forced the switch down. I do have some further info, which may help. This weekend I finally finished setting up a dedicated music server, running XP (not linx), and with significantly more RAM (1024, whereas it was 256). Since switching slimserver over to this server, I've not had a single hangup or problem with fw35 and I've been playing music non-stop for 12 hours a day or so for the last three days. Could it be a resourcing issue or an xp/Linux os issue ?
Ok, Dean asked me to check a couple of things out ... When the SB freezes, the following actions "fix" it: 1. Press and hold left arrow. Reconnect to Slimserver. 2. Restart slimserver When it happens again I'll try restarting the AP to see if that also makes the SB reconnect. R.
I have run into a similar situation twice this weekend. My SB3 device freezes up, the first time over it was frozen with the clock. The 2nd time around it was hung in Now playing halfway between a song. My network is a mixed devices with 3 b devices and 2 g devices. But for most part at any given time, only the 2 g devices are alive and active(iMac & the SB3). Gov
Sounds familiar: since svn updating Monday to 6581 and firmware 35, my SB2 keeps locking up, mostly overnight or during the day when we're at work, leaving the date/time frozen. I've had to disconnect power to get it working again. Firmware 33 was not as bad, it would just occasionally stop playing. I had no problems with firmware 28. Router is a Linksys WRT54GS, the only wireless clients are an SB2 and an SB1G.
Just an update. I opened this bug. But I've been running for weeks B only with two access points, two SB3. Both seem able to switch from one access point to the other. And NO HANGS. So I really think, whatever it is, its G or Mixed B/G related. When I originally opened this, I was running mixed to let the SB3's use G, even though my laptop is B only.
Following up on comment #9 ( https://bugs-archive.lyrion.org/show_bug.cgi?id=3093#c9 ) I can confirm that restarting the access point causes the SB to reconnect too.
There may be more than one bug here. If you are running 6.5, a bug was fixed in the last nightly that addresses a lockup in the player. Try updating to the latest nightly release to see if it's fixed for you.
As is noted above, this bug is now apparently tracking more than one problem - BUT I opened it originally. AFAIK, after two days of running, Firmware 36 fixes my problem. To be specific. I have a linksys wrt54g and an (old) IBM High Rate B only access point, both serving a single network in my house. I have a B only laptop with a Cisco 350 minipci adapter. With firmare 33 and 35, if I ran the WRT54G in mixed mode, i would see the hangs reported. If I ran in B only mode, I did NOT see any hangs. With 36, I have been running mixed B/G for more than two days now without a hang. Both my SB3's have switched from one adapter to the other at least once without hanging. I'm not closing this because of the "more than one bug" issue mentioned above.
Hi Marc, Did you mean to close this bug? Is anyone else on the cc list still having this problem with FW 36 or 37? thx
(In reply to comment #16) > Hi Marc, > Did you mean to close this bug? Is anyone else on the cc list still having > this problem with FW 36 or 37? > thx I've note experienced this at all on f/w 36. Haven't yet tried 37.
Closing this bug - if anyone else has other problems that they think are in this, I guess they can either open a new bug or reopen this one. But I'm definitely happy as of Fireware 36 - and 37 is good as well so far.
This bug has been fixed in the latest release of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.