[Trac #1138] iwlist command failure.

[Zarro Boogs per Child]

#1138: iwlist command failure.
--------------------------------+-------------------------------------------
 Reporter:  swagle at marvell.com  |        Owner:  jcardona
     Type:  defect              |       Status:  new     
 Priority:  blocker             |    Milestone:  Trial-1 
Component:  wireless            |   Resolution:          
 Keywords:                      |  
--------------------------------+-------------------------------------------
Comment (by jcardona):

 Replying to [comment:4 mbletsas]:
 > Replying to [comment:3 jcardona]:
 > > One more thing to try:  revert to a previous wireless firwmare
 (5.220.9p9).
 > > Rebooted several times, the problem did not appear.
 > >
 > > Restored 5.220.10p2, the problem reappeared.
 >
 > One more thing:
 >
 > meshy3 has been updated to the latest laptop firmware (Q2B81), which
 resets the 8388 during startup. meshy8 (most probably) runs an earlier
 version that doesn't.

 Based on this, I wanted to see if I could get meshy3 to fail.  I left this
 script running overnight, on my host.  One instance pointing to meshy3,
 another to meshy9 (meshy8 is rejecting connections).

 {{{
 while true
 do
         date
         ssh root at meshy3 ethtool -i msh0
         ssh root at meshy3 reboot
         sleep 120
 done
 }}}

 The summary is:

  * The failure appears in both, meshy9 more frequently than meshy3 (~50%
 vs. ~30%)
  * After a number of iterations (meshy9: 51, meshy3:75) both nodes lose
 connectivity through the network (crash?)

 So this seems to be an easy way to reproduce:  keep rebooting until it
 fails.

 Logs attached.

-- 
Ticket URL: <http://dev.laptop.org/ticket/1138#comment:6>
One Laptop Per Child <http://laptop.org/>