#10270 HIGH Not Tri: wlan goes missing during runin

[Zarro Boogs per Child]

#10270: wlan goes missing during runin
--------------------+-------------------------------------------------------
 Reporter:  rsmith  |                 Owner:  dsaxena      
     Type:  defect  |                Status:  new          
 Priority:  high    |             Milestone:  Not Triaged  
Component:  kernel  |               Version:  not specified
 Keywords:          |           Next_action:  reproduce    
 Verified:  0       |   Deployment_affected:               
Blockedby:          |              Blocking:               
--------------------+-------------------------------------------------------
 This is a top level ticket for 3 different wlan problems that are
 occurring during runin.

 The following issues have been observed:

 1) Wlan some times shows up as eth1 rather than eth0

 This issue has a temporary fix in runin versions '0.9.40'.  It still
 generates an error but the script will delete the persistent rules file
 for udev so that on the next boot it will return to eth0.  The long term
 fix is to create a udev rule that pins the wlan to eth0 always.

 2) Libertas fails to load firmware.

 This issue has 2 different flavors.  The first is if you remove the
 libertas module from the kernel yet do not power cycle the wlan card.
 The 2nd is the same result but it happens at odd times in the runin
 sequence.  Sometimes on the 1st boot and some times after a
 suspend/resume.

 3) Wlan card fails to respond after power up.

 In this case the wlan fails to respond after a mmc power up.  Kernel logs
 look like:

 {{{
 <4>[ 1245.312719] sdhci_reset: wlan w/u control is 0x0
 <7>[ 1245.312731] sdhci-pci 0000:00:0c.0: setting latency timer to 64
 <4>[ 1245.312757] sdhci_set_power: new power value = 14
 <4>[ 1245.322795] sdhci_set_power: new power value = 14
 <4>[ 1245.373206] sdhci_set_ios: power off for mmc0 from b061ba25
 <4>[ 1245.373214] sdhci_set_power: new power value = 0
 <4>[ 1245.373225] sdhci_set_power: new power value = 14
 <4>[ 1245.427424] sdhci_set_ios: power off for mmc1 from b061ba25
 <4>[ 1245.427432] sdhci_set_power: new power value = 0
 }}}

 This seems to occur after a lot of suspend/resumes.

 Issues 2 and 3 are so far cannot be duplicated by OLPC or Quanta.  Quanta
 has tried to pin it to specific hardware but so far that has failed.
 Usually when you re-run the tests then they will pass.  Quanta has taken 2
 of the cards that failed on the line and run them again for 48 hours with
 no failures.

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