#1752 BLOC Trial-2: USB wireless suspend/resume failure at setup phase

[Zarro Boogs per Child]

#1752: USB wireless suspend/resume failure at setup phase
-----------------------+----------------------------------------------------
  Reporter:  marcelo   |       Owner:  rchokshi
      Type:  defect    |      Status:  new     
  Priority:  blocker   |   Milestone:  Trial-2 
 Component:  wireless  |     Version:          
Resolution:            |    Keywords:          
  Verified:  0         |  
-----------------------+----------------------------------------------------
Changes (by rchokshi):

 * cc: marcelo at kvack.org (added)

Comment:

 Replying to [comment:26 rsmith]:
 > suspend/resume cycles.  There are about 5 or 6 or so suspend/resume
 cycles that worked and then the last one hung the machine.
 > >
 > > This trace is quite inconclusive, honestly. In the final crash, it
 only shows an incomplete IN transaction.
 >
 > I have to work on EC problems but Chris Ball can drive the analyzer.
 Its set up and ready to go.  Tell us how to give you more info.  More
 traces of the same thing?  More retries in the kernel?

 I think it would be great if you can send a bad trace and a good trace
 with the circumstances in Trac # 2621. This will probably go a long way in
 explaining the root cause of this issue.

 >
 > We can also do some sort of VNC thing where we talk on the phone and you
 can look at the data in real time.

 Yes, this might help. Please let me know what time would be good for you.
 We will create our schedule during that time.

 In addition to my other questions above which are still unanswered:

 It is clear that during the suspend/resume cycle, the firmware is not
 involved at all, i.e. it is in fully awake state.

 So, I cannot think of any possibility of failure that could be caused by
 firmware because the device basically do almost nothing during
 suspend/resume cycle.

 Because of that, this suspend/resume cycle is eventually the same as
 enumeration cycle to the firmware side. So, we thought that doing just a
 regression on the enumeration cycle would suffice to test whether the USB
 design of 8388 is an issue. So, we did enumeration cycle test. It was
 okay. This is assuming that the wakeup is not wireless-initiated.

 Enumeration cycle test can be done with the software tool in Win XP PC.
 That tool can be downloaded from usb.org web site.

 Could you confirm if you are using 5.110.17.p0?

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