Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - USB driver issue: (8 Items)
   
USB driver issue  
I ran into a strange issue with the USB driver last week on a new computer model being tested for use with our QNX 4.25 
application.
The USB mouse pointer suddeny started being hardly responsive - it moved in large steps with a few seconds interval when
 moving the mouse.
When running the "usb" command on the command line, it was also slow to respond and showed error messages about "input/
output error" for all USB devices on the bus.

We use the USB 2.00L drivers and the Proc32 4.25R kernel.
A reboot resolve the problem.

Have you seen this problem before? Is there anyway for me to find more information about possible root cause in case it 
happens again?
Re: USB driver issue  
Hi Darel,

Sorry for the delay with my answer. We have not faced off such issue before. Is it reproducible behavior?

Respectfully,
Oleg

> I ran into a strange issue with the USB driver last week on a new computer 
> model being tested for use with our QNX 4.25 application.
> The USB mouse pointer suddeny started being hardly responsive - it moved in 
> large steps with a few seconds interval when moving the mouse.
> When running the "usb" command on the command line, it was also slow to 
> respond and showed error messages about "input/output error" for all USB 
> devices on the bus.
> 
> We use the USB 2.00L drivers and the Proc32 4.25R kernel.
> A reboot resolve the problem.
> 
> Have you seen this problem before? Is there anyway for me to find more 
> information about possible root cause in case it happens again?


Re: USB driver issue  
Hi,

  We have not been able to provoke the error but during the weekend it happened again. No-one was using the system at 
the time, it was just up and running with communication on serial and network ports to associated equipment.
  When running command "usb" I get the following output:
USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
device 1 - descriptors - Input/output error
device 2 - descriptors - Input/output error
device 3 - descriptors - Input/output error
device 4 - descriptors - Input/output error


Re: USB driver issue  
Hi Darel,

It's too difficult to debug it remotely. But if this issue will occur again then you can send me output of following 
commands just after the system start:

sin
sin ar
sin ver
sin ir
show_pci -vvv

And output of sin ar just after the issue occurs.

Please send the output in one tarball.

Respectfully,
Oleg

> Hi,
> 
>   We have not been able to provoke the error but during the weekend it 
> happened again. No-one was using the system at the time, it was just up and 
> running with communication on serial and network ports to associated equipment
> .
>   When running command "usb" I get the following output:
> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
> device 1 - descriptors - Input/output error
> device 2 - descriptors - Input/output error
> device 3 - descriptors - Input/output error
> device 4 - descriptors - Input/output error
> 
> 
Re: USB driver issue  
Hi,
  We have not managed to find a way to reliably reproduce the issue, but it did happens once again and we could collect 
the information you requested. See attached zip file for various sin outputs.
  Slaying and restarting io-usb (and other drivers that depend in it, like devu-mouse) resolved the issue so it seems 
that io-usb ends up in some state that it cannot recover from but that a restart resolves. 
Attachment: Compressed file sin_usb.zip 29.08 KB
Re: USB driver issue  
Hi Darel,

Here is a couple of recommendations:

1) Try to play with USB options in BIOS (usually in Advanced-> USB Configuration).
2) There is two mouse devices —  /dev/mousein (created by Mouse manager) and /dev/usbmouse0 (usb-mouse). Try to use USB
 mouse with Input manager. Change the line in your /etc/config/trap/input.$NODE for mouse to:

Input msoft fd -d/dev/usbmouse0

Make backup of input.$NODE before and don't forget for keyboard.

Respectfully,
Oleg

> Hi,
>   We have not managed to find a way to reliably reproduce the issue, but it 
> did happens once again and we could collect the information you requested. See
>  attached zip file for various sin outputs.
>   Slaying and restarting io-usb (and other drivers that depend in it, like 
> devu-mouse) resolved the issue so it seems that io-usb ends up in some state 
> that it cannot recover from but that a restart resolves. 


Re: USB driver issue  
Hi Oleg,

  I have looked into the above issue again from our side after it had been observed again and I have a few findings that
 may be of interest:

* It seems certain USB input devices are more likely to cause issues with the USB driver. For example, with a "Microsoft
 Intellimouse Optical USB Mouse" we can see that the 'usb' tool often reports input/output errors if executed while 
moving the mouse pointer. The same does not happen for other input devices, such as HP USB mouse or Kensington trackball
.

* It seems certain models of USB memory sticks are more likely than others to cause the entire USB driver to stop 
working as was mentioned in previous posts. For example, Sandisk Cruzer Blade drives appear to be more likely to cause 
these issues than other models. To provoke such issues, we have found that if you run the 'usb' command to check on USB 
device status while copying files to the USB drive it can easily cause input/output error for these Sandisk devices. And
 in some cases, the USB driver never fully recovers.

* As mentioned earlier, it is generally enough to slay and re-start io-usb (and then associated drivers like devu-mouse)
 to get everything up and running again.

Is there any additional information you can think of that we could try to collect to give you an even better picture of 
what's really going on? 
Re: USB driver issue  
Hi Christian,

We have not faced of this issue before. To debug it we should reproduce the issue with specified HW.

Respectfully,
Oleg

> Hi Oleg,
> 
>   I have looked into the above issue again from our side after it had been 
> observed again and I have a few findings that may be of interest:
> 
> * It seems certain USB input devices are more likely to cause issues with the 
> USB driver. For example, with a "Microsoft Intellimouse Optical USB Mouse" we 
> can see that the 'usb' tool often reports input/output errors if executed 
> while moving the mouse pointer. The same does not happen for other input 
> devices, such as HP USB mouse or Kensington trackball.
> 
> * It seems certain models of USB memory sticks are more likely than others to 
> cause the entire USB driver to stop working as was mentioned in previous posts
> . For example, Sandisk Cruzer Blade drives appear to be more likely to cause 
> these issues than other models. To provoke such issues, we have found that if 
> you run the 'usb' command to check on USB device status while copying files to
>  the USB drive it can easily cause input/output error for these Sandisk 
> devices. And in some cases, the USB driver never fully recovers.
> 
> * As mentioned earlier, it is generally enough to slay and re-start io-usb 
> (and then associated drivers like devu-mouse) to get everything up and running
>  again.
> 
> Is there any additional information you can think of that we could try to 
> collect to give you an even better picture of what's really going on?