On Fri, Jul 08, 2011 at 10:28:48AM -0400, Alan Stern wrote: > On Fri, 8 Jul 2011, Rajkumar Manoharan wrote: > > > Hi, > > > > In 3.0.0-rc6-wl kernel, ath9k_htc device failed to resume > > when we do rtcwake. But the same driver and firmware seems to > > be working properly with older (2.6.38) kernel. In dmesg was logged with > > following error. > > > > ehci_hcd 0000:00:1a.7: GetStatus port:1 status 001002 0 ACK POWER sig=se0 CSC > > hub 1-0:1.0: port 1: status 0100 change 0001 > > ehci_hcd 0000:00:1a.7: GetStatus port:3 status 003002 0 ACK POWER OWNER sig=se0 CSC > > ehci_hcd 0000:00:1a.7: GetStatus port:4 status 003002 0 ACK POWER OWNER sig=se0 CSC > > ehci_hcd 0000:00:1a.7: GetStatus port:6 status 001803 0 ACK POWER sig=j CSC CONNECT > > hub 1-0:1.0: port 6: status 0501 change 0001 > > hub 1-0:1.0: port 1 status 0000.0100 after resume, -19 > > usb 1-6: finish reset-resume > > usb 1-1: can't resume, status -19 > > hub 1-0:1.0: logical disconnect on port 1 > > > > Please help me to find out where things went wrong. > > The device disconnected itself while it was suspended, and then > reconnected after the system had resumed. > > > (complete kernel.log attached) > > You can see the reconnect messages near the end of the log. > Yes. But the driver's resume never be called. So device reconfiguration failed. > Have you compared this to a log from 2.6.38? > I didn't compare the kern logs. but driver's resume was invoked and configurations were restored properly in 2.6.38. > I don't know of anything that would cause the behavior to change. Does > this disconnect happen every time you suspend? If it does, you can try > using git bisect to find out when the problem was introduced. > Yes diconnect happens always. I'll do bisect. -- Rajkumar -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
