> > get these to stderr > > > > usb_control/bulk_msg: timeout > > usb-ohci.c: unlink URB timeout > > These messages are normal, as the visor disconnects itself after it is > finished syncing.
They were generated by the 'cat /proc/bus/usb/devices' that I issued after the mouse had locked and the sync already failed (according to the visor display). I don't remember ever seeing them before, but I haven't had verbose debugging enabled in quite a while. > I don't think the visor has much to do with the mouse. > Does the mouse fail over time, if you don't use the visor? The mouse seems to work fine (> a few days) as long as I don't sync the visor. When I do use both it seems to take a random amount of mouse motion to cause the lockup, sometimes merely clicking to bring forward the xterm tailing syslog will do it, other times I can move the mouse and click buttons as fast as I want with no problem. One other thing that occurred to me was a problem that a couple of us experienced and discussed on the usbvisor-unix list in early May, with strange hard reboots caused by inserting the visor into the cradle, but only when plugged into one of the 2 USB ports (see attached message below). I still use the same computer, and the mouse is now plugged into the USB port that was causing the trouble. Maybe I have a hardware problem, what do you think? I'll try swapping the two devices when I get home tonight to see if anything changes for the better, or if I go back to getting the random hard boots. At least now I have ext3 fs, so the hard boots won't take so long. Once again, thanks for the help. Chris P. -- [EMAIL PROTECTED] http://cpayne.freeshell.org Date: Wed, 2 May 2001 07:46:41 +0000 From: Chris Payne <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Charles Philip Chan <[EMAIL PROTECTED]> Subject: Re: [Usbvisor-unix] Occasional Crash User-Agent: Mutt/1.2.4i In-Reply-To: <[EMAIL PROTECTED]>; from [EMAIL PROTECTED] on +Fri, Apr 27, 2001 at 09:17:49PM -0400 > Once in a while when I insert my Visor Deluxe into the cradle it crashes > the system. Have anyone else encountered this problem? I am running > kernel 2.4.2 on an OHCI based system. I get similar response on my IBM Aptiva E4N with an OHCI based controller and 2.4.3. It's like a hardware reset is pulled, as I go directly to POST. After a few times, I tried various groundings of me, the visor, etc, but it still happened about 50% of the time. I did find out (by accident) that it does not happen when the cradle is plugged into the other USB port. As to what "other" means in hardware, I'm not that familiar with USB, but that is the "fix" that I used for now, as the visor cradle is my only USB device anyway. Good Luck Chris P. _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
