Thanks for the reply David, but where exactly does this leave me and the others experiencing this problem? Is there any more information I can provide that might help? Any possible solutions, patches, etc?
On Thu, 5 Aug 2004 08:34:27 -0700, David Brownell <[EMAIL PROTECTED]> wrote: > On Wednesday 04 August 2004 20:57, Michael Guterl wrote: > > > Attached are my dmesg's from each kernel, each time I booted fully, > > then plugged the USB keyboard in, and then the USB mouse. My kernel > > config is also attached, along with the output of lspci -v, (David > > Brownell mentioned "lspci -w" but this isn't a valid option, and I > > Actually that was "-vv" (two v's, not double-v), but don't bother. > > The dmesg output shows this is a HID failure. It's likely connected > with some changes in the unlink logic, since that's what returns > the "-ENOENT" status. The usb_kill_urb() changes added a new > URB state as I recall, maybe that's part of the issue here... since > that routine replaced the previous "synchronous unlink" logic. > > - Dave > > ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
