Bugzilla – Bug 9067
Jive loses connection to Ray via bridge mode. (Was: Jive units got stuck in update failure mode.)
Last modified: 2008-11-17 10:00:50 UTC
Ever since the apperance of the, old 7.2 (new 7.3) jive FW, a few Jive units sometimes get stuck in the failure mode. They are not able to update either automatically or manually. Performing a Factory Reset help some of the times. It is now happenign with this new 7.2(old 7.1) build. For example, this morning, AutoSmokeTestsSys performed the following tests and passed most of them. Then everything started failing. DownGrade Jive to jive_7.1_r2447.bin -- PASS Update Jive to jive_7.2_r2792.bin -- PASS Update Jive to jive_7.2_r2792.bin -- PASS DownGrade Jive to jive_7.1_r2447.bin -- PASS Then everything started failing. Now, this unit cannot even go back to jive_7.1_r2447.bin automatically or manually. The same issue happened yesterday with another Jive unit. There had been failures in 7.1 builds. However, they had been confirmed to be real failures. With 7.2, some failures may be due to Jive units acting funny.
Created attachment 3756 [details] Log file of failed tests. Log file of failed tests.
Created attachment 3757 [details] After the PlayMode test failed on this Smoke tests run, everything started failing. Even the tests that passed frior to this.
Richard to look at this on monday
Created attachment 3776 [details] Putty log when this happened.
Richard has asked Ben to review on Thursday with Wallace.
I'll talk to Wallace about sending a unit or two to Ben that's exhibiting the problem. QA also needs to test this manually to verify that there's no problem upgrading from ss 7.1 -> ss 7.2 -> ss 7.3
James has completed testing that upgrade path on multiple units manually, and they have passed.
Created attachment 3841 [details] Another putty log for this bug. Basically, the Jive keeps going to "Try again..." after trying to update. Can this be a network problem? Is it OK to change the scripts to update from SD card instead?
I need the application log from the SD card to see what's gone wrong here. Thanks.
Updating from SD card work most of the time. How does James update his? From PC or an SD card? Richard's lua script was written to update the Jive from a PC. If changed to update from SD card, would the tests be just as valid? Or is the SmokeTestsSys digging up lots of unexpected bugs that it should not be changed to avoid them? A resolution is needed now.
No, the test should update from a PC as that's what we expect the user to. I need to see the log file from the SD card, then we can work out what's failing.
Created attachment 3842 [details] Here is the message log file in the Jive unit. Hi, Richard, Is there any other log file inside the Jive unit that is needed?
No, thanks that the correct log. The key lines are: Aug 20 03:41:39 (none) user.err jive: (NetworkThread.lua:139) - network thread timeout for Task(SocketHttp {www.slimdevices.com}(W)) Aug 20 03:41:39 (none) user.err jive: (SocketHttp.lua:350) - SocketHttp {www.slimdevices.com}:t_sendRequest.pump: inactivity timeout Aug 20 03:41:39 (none) user.warn jive: (Upgrade.lua:91) - download Failed err=inactivity timeout That shows it was trying to download the firmware from www.slimdevices.com and not your local SC. It looks like the download failed as the http connection could not connect. It does not look from the logs like the Controller connected to a player - it must do this before the software upgrade. Do you see the player menus (e.g. Music Library) on the menu? If not select your test player from Choose Player, and retest. Ben has a bug (not sure if it made 7.2 or not), to prevent users getting to the software update menu if no player is selected (and no sd card is available) already. That would catch this problem in a more user friendly way.
Do you see the player menus (e.g. Music Library) on the menu? No, the "Home" menu consists of "Settings", "Extras", and "Choose Player" items. Choosing test Player and try to upgdate fw to see what happens. Update complete. It works. It was failing a little earlier. Jive is connected to the Ray via bridge mode. This means the connection is unstable. Thanks. This is great help. Really appreciate it. Will see how SmokeTestsSys can handle it.
By the way, the messges log file attached here is the same provided by the auto tests system email. The messages file for every smoke test is archived in the auto tests sys web server. Links to them are in the all tests results emails.
Marking as invalid, this bug was caused by a failure of the auto test system.
This is not an invalid bug, and it is not caused by the Auto Tests System. Jive is losing connection to Ray, therefore cannot update from the PC. Glad that Auto Tests Sys found this. Not happy that this happens too often. Auto Tests Sys may be able to handle this later, but that masks a serious problem. The Jives are 5 cm from the Rays. The connections must not be dropped. This bug needs to be fixed.
Here is a better description of the steps: FW: 7.2 and 7.3 HW: MP, not old engineering samples Steps to Reproduce: 1. Factory reset both Jive and Ray. 2. Connect them together with bridge mode. Connected them to a test PC with SC running. 3. Leave them alone for a while. 4. Notice sometimes the Jive drops connection to the Ray. The user has to select a player again. 5. Sometimes the signal icon turns blue. However, most of the time, it stays white. The user has no idea there is a connection problem. 6. Sometimes this problem happens right after updating firmware. Most of the time, this problem prevents firmware update from a PC. It is causing problem with the AutoSmokeTestsSys. Work Around: Go to Home menu and choose the player again. Sometimes, again and again.
Created attachment 3856 [details] putty log for a Jive with wifi icon turned blue this morning.
Created attachment 3857 [details] messages log file from the Jive unit. FW: 7.3 r2867.
Chris to talk to wallace and clarify this bug report.
Wallace are you still seeing this? Or has it improved with the recent Squeezebox Controller firmware fixes?
Tried many times with jive_7.3_r3354.bin. Bug as written is no longer seen.