Bug 9115 - Jive: 7.3 FW: Stuck in "Free Your Music " screen for about 5 mins.
: Jive: 7.3 FW: Stuck in "Free Your Music " screen for about 5 mins.
Status: RESOLVED DUPLICATE of bug 9231
Product: SB Controller
Classification: Unclassified
Component: Power Management
: unspecified
: Other Other
: -- normal (vote)
: 7.3
Assigned To: Squeezebox QA Team email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-11 16:05 UTC by Wallace Lai
Modified: 2008-08-21 04:15 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments
Putty log for this bug. Log is a bit long because it captured great deal of other tests also. (80.92 KB, application/octet-stream)
2008-08-11 16:09 UTC, Wallace Lai
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wallace Lai 2008-08-11 16:05:48 UTC
FW:  jive_7.3_r2830.bin

Steps to Reproduce:
1.  Downgrade Jive to jive_7.1_r2447.bin.
2.  Upgrade the Jive to jive_7.3_r2830.bin.
3.  After the upgrade, Jive reboots.
4.  During the reboot process, notice the unit is stuck at "Free Your Music" screen for at least five(5) minutes.  It eventually finished rebooting and went on to the auto PlayMode test.
Comment 1 Wallace Lai 2008-08-11 16:07:47 UTC
Hi, Richard,

The Jive unit that this bug happened is not the same as the one gotten stuck at "Logitech" screen this morning.
Comment 2 Wallace Lai 2008-08-11 16:09:44 UTC
Created attachment 3780 [details]
Putty log for this bug.  Log is a bit long because it captured great deal of other tests also.
Comment 3 Wallace Lai 2008-08-11 16:10:48 UTC
This bug has not been reproduced yet.  However, it needs to be logged here.  Will close it if cannot be reproduced in the future.
Comment 4 Wallace Lai 2008-08-18 10:36:15 UTC
Just reproduced this bug on another Jive unit with firmware jive_7.3_r2860.bin.
Therefore this is not caused by a bad hardware.
It is very time consuming to reproduce.  A user basically runs into it intermittently.
Comment 5 Richard Titmuss 2008-08-21 04:15:54 UTC

*** This bug has been marked as a duplicate of bug 9231 ***