#9193 NORM Not Tri: Marvell WLAN wedges on quick StandBy

Zarro Boogs per Child bugtracker at laptop.org
Tue Jan 13 14:34:49 EST 2009


#9193: Marvell WLAN wedges on quick StandBy
-------------------------------+--------------------------------------------
 Reporter:  wmb at firmworks.com  |                 Owner:  rchokshi     
     Type:  defect             |                Status:  new          
 Priority:  normal             |             Milestone:  Not Triaged  
Component:  not assigned       |               Version:  not specified
 Keywords:                     |           Next_action:  never set    
 Verified:  0                  |   Deployment_affected:               
Blockedby:                     |              Blocking:               
-------------------------------+--------------------------------------------
 Under Windows, put the machine into StandBy mode.  Then wakeup from
 StandBy mode, and then re-enter StandBy mode before the wireless driver
 has finished associating with an access point (i.e. before the second set
 of flashes of the WLAN activity LED).  When you wake up from that second
 StandBy, the wireless won't work.  The balloon help in the System Tray
 says "Wireless Network Connection is not connected, Wireless network
 unavailable", and stays that way (on a normal wakeup, that message
 disappears after a few seconds, when the wireless starts up and connects).

 This is easier to reproduce if you have the power button set to invoke
 StandBy directly, so it's easy to invoke StandBy quickly.  You can also do
 it quickly by shutting the lid.

 Sometimes you can make it work again by doing another StandBy/wakeup
 cycle, but I have also seen cases where you had to go into the device
 manager and disable/re-enable the device to make it work right, and in one
 case I'm pretty sure I had to reboot to recover the wireless functionality

 Driver version: 8.72.706.716 and .717 behave identically in this respect

 Firmware version: the version that was submitted to Microsoft

 BIOS version: OFW Q2E27 and Insyde BIOS behave identically in this respect

 OS version: Windows XP SP2 and SP3 - fails identically

-- 
Ticket URL: <http://dev.laptop.org/ticket/9193>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system


More information about the Bugs mailing list