Re: [Rt2400-devel] Resuming rt73usb wireless network dongle: ep0in 3strikes
Alan Stern <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 5 Sep 2007, Mattias Nissler wrote: > > Hell, I just realize it seems to *work* now! I've just run 4 tests and > > each time it came back as it should. I was never able to do this > > before... Only thing I changed is ehci-hcd now being a module and the > > ehci_dbg() call in the loop that prints the port status word. Weirdness! > > > > Anyway, I don't have more time right know, will try to compile ehci-hcd > > back into the kernel and see whether the issue comes back then... Maybe > > it's a timing problem? > > Ok, now I have ehci-hcd back in the kernel and see the problem again. > Full suspend log is at > http://www-user.rhrk.uni-kl.de/~nissler/rt73usb_sr/syslog_suspend_to_disk_4.txt > > Note the port status word on resume is the same as in the previous log > that didn't show the problem. It could indeed be a timing problem. In ehci_pci_resume(), you can try adding an msleep() call right before the first "return 0". I don't know how long a delay would be needed, but 1000 ms should be more than enough. Another possibility is to print out in ehci_bus_resume() the port status values in the second loop (read the status register again at the end of the loop to get the value following the write). Maybe some sort of connect status change will show up. Whatever the problem is, it seems to be specific to your hardware or firmware. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel