-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Usb issues #24
Comments
2 questions: Does the problem still exist with: v3.7.10-x10 To Test: and does it occur with: v3.9-rc6: To Test: Background: I'm thinking of doing the v3.7.10 -> v3.9-rc(7/8) jump with my images by default for everyone... |
The problem arises on the long run (no problem for 16 days for I am not able to test multiple hardwares at a time anymore as we have Le ven. 12 avril 2013 14:56:32 CEST, Robert Nelson a écrit :
|
Ah no problem, I never know what type of environment (hands of end user/production/testing/etc) these images are being used in. ;) Yuck, so searching on google, this has come before with the ftdi_sio drivers.. No good hints.. Mainline vs 3.7.1: One or two changes other then vid/pid additions... So you'll probally not see a difference.. |
Note: Found a thread related to this kind of issue. The thread states that this should be related to power issues but the guy having the problem was using an external non powered hub, which is not my case (I plug my devices directly on the beagle) but this is still interesting to note. |
Other note: I am using socat to pipe the tty on a socket. |
Third note: The problem now seems to happen every 10-20 hours (on the board in production). FWICT this seems to be degrading (is that even a word? :) ) over time. |
On a beagleboard:
uname -a : Linux arm 3.7.1-x4 #1 SMP Fri Jan 25 12:52:47 CET 2013 armv7l armv7l armv7l GNU/Linux
lsb_release -a:
Distributor ID: Ubuntu
Description: Ubuntu 12.10
Release: 12.10
Codename: quantal
symptoms:
Tried to reset the usb bus using ioctl USBDEVFS_RESET, but the device then fails to enumerate.
When switching the usb port it does work though ( I mean when connecting the usb device to another physical usb port)
The text was updated successfully, but these errors were encountered: