I haven't been able to cause an oops, and up until just a minute ago
things seemed to be working fine. But on my latest sync attempt, I got
this in the dmesg log:
hub 1-0:0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 1-0:0: new USB device on port 2, assigned address 3
usb 1-2: USB device not accepting new address=3 (error=-110)
hub 1-0:0: new USB device on port 2, assigned address 4
usb 1-2: USB device not accepting new address=4 (error=-110)
hub 1-0:0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 1-0:0: new USB device on port 2, assigned address 5
usb 1-2: USB device not accepting new address=5 (error=-110)
hub 1-0:0: new USB device on port 2, assigned address 6
usb 1-2: USB device not accepting new address=6 (error=-110)
and the sync failed.
I'll be upgrading to -bk[latest] later today anyway, and will let you
know if I see further problems with visor USB hotsync...
Torrey Hoffman
thoffman@arnor.net
On Mon, 2003-05-19 at 17:15, Greg KH wrote:
> On Mon, May 19, 2003 at 02:43:34PM -0700, Torrey Hoffman wrote:
> > I got a non-fatal oops while trying to hotsync my Handspring Visor.
> > My system is still running as I send this email, but the hotsync didn't
> > work.
>
> Can you try with the latest -bk tree? I can successfully sync using it,
> but did have some problems with a few of the older revs.
>
> thanks,
>
> greg k-h
-- Torrey Hoffman <thoffman@arnor.net>- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/