Bug 11672 - Setup fails to continue or provide feedback if network connection is lost after FW update
: Setup fails to continue or provide feedback if network connection is lost aft...
Status: RESOLVED FIXED
Product: SB Touch
Classification: Unclassified
Component: Setup
: unspecified
: PC Other
: -- normal (vote)
: MP
Assigned To: Richard Titmuss
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-06 10:46 UTC by Dan Evans
Modified: 2009-09-08 09:16 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Evans 2009-04-06 10:46:28 UTC
(using 5156 & 5198)

If you successfully connect Fab4 via ethernet, and it does a firmware update, but you then pull the ethernet cable during the restart... Fab4 restarts and settles on a default menu of: My Music, Settings, and App Guide.  

There's no error indicating a loss of connectivity and no way to continue on to SN setup *after* you restore that connectivity.

Because setup was not actually completed, this should be handled differently than bug 11314.  We need to provide feedback about the failure and/or guide the user on to complete setup.

I will try this with WiFi as well.
Comment 1 Dan Evans 2009-04-06 12:07:28 UTC
3 notes:

1. I got this bug slightly wrong as I had forgotten to delete my MAC from fab4.sn.com.  So, I think Fab4 considered the setup complete when I did not.  The behavior described above is still not ideal, but neither is it as bad as I first thought.

2. Since realizing I hadn't deleted it properly, I've tried with the MAC deleted from fab4.sn.com which led me to comment 7 on bug 11555.  I got repeated errors when trying to get reconnected to the network after plugging the ethernet cable back in.  Log attached to bug 11555.

3. After restarting, Fab4 took upwards of 30 seconds to time-out and provide an error.  When on ethernet, we should know immediately if the ethernet plug is disconnected or we have no link.
Comment 2 Dan Evans 2009-04-06 12:09:09 UTC
WiFi note: (using 5156)

When trying this via WiFi I got the same results as above in item #2-- the incorrect error, "A firewall or other mechanism seems to be blocking..."  This is after a successful connection to WiFi, successful fw update, but I turned OFF the WiFi while it was restarting.  After coming back from restart, it first correctly detected the WiFi was gone, but after restarting the WiFi and pressing "Try again" I got stuck in the "firewall" error loop.  I'm not sure if this is bug 11555 or should be separate?
Comment 3 Blackketter Dean 2009-04-06 22:26:21 UTC
Richard: this is an MP issue, right?
Comment 4 Richard Titmuss 2009-04-07 13:51:00 UTC
Fixed in r5221.