On Thu, 19 Feb 2004, Chip Salzenberg wrote: > Still fails in 2.6.3. Logs, with debugging on, are included below. > > A clue: The failure is not caused by re-plugging per se. It's > triggered by APM suspension. When I tested my system today with > 2.6.3, it worked OK at first; then I got the idea to suspend and > try again, and then it failed.
Or maybe it's triggered by the APM resume -- kind of hard to tell the difference, though. One key bit of information is this line in your log, shortly after the resume takes place: > 16:06:41 hub 2-0:1.0: port 1, status 101, change 1, 12 Mb/s It's referring to the USB port on your computer into which you plugged the composite keyboard/trackpad. Status 101 means the port is powered up and there is a device connected, good so far. But change 1 means that there has been a change in the connection status; i.e., the cable was disconnected and then plugged back in. I think it's safe to assume you didn't actually unplug the keyboard while your computer was asleep, so there must be something else causing the USB controller to report that change in the connection status. I don't know what it might be, though. In itself that's not so bad. If the system, seeing that something was indeed plugged in, had gone ahead and reinitialized the keyboard you probably wouldn't have noticed that anything unusual had happened. It's not clear why it didn't do that; I'll have to get back to you later on this one. Alan Stern ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
