[SOLVED] USB problem
Posted: Mon Oct 04, 2010 11:12 am
Hi all,
I'm working with three FitPC2 with Ubuntu 10.04LTS. They are powered by LiIon battery and they are mounted on moving vehicles. At these FitPC2 I've attached three USB peripherals each (2 video converter WIS GO7007 and 1 Arduino nano).
My systems work perfectly if I run a "test mode" with vehicle stopped in station, but when I move the vehicles I get randomly the video converters stop working in the moment I get these messages from kernel (on hub 1, port 4,5):
This is the output for "lsusb -t":
If I execute a software reset of the USB Hub (or remove and insert again the driver for the go7007 peripherals) the system start again working fine.
I know that FitPC has a non standard power supply for USB peripherals, and I think OS can't really know if my peripherals are requesting much current, that I know isn't so.
I made a lot of test about USB connection for vibration issues, and finally I soldered the wires on motherboard and on the external board. So I can realize that isn't vibration that disconnect for a really short time the peripherals.
I'm sure the problem is somewhere else.
Have you some suggestion about what can produce this messages on the kernel?
Thank you very much, Davide
I'm working with three FitPC2 with Ubuntu 10.04LTS. They are powered by LiIon battery and they are mounted on moving vehicles. At these FitPC2 I've attached three USB peripherals each (2 video converter WIS GO7007 and 1 Arduino nano).
My systems work perfectly if I run a "test mode" with vehicle stopped in station, but when I move the vehicles I get randomly the video converters stop working in the moment I get these messages from kernel (on hub 1, port 4,5):
Code: Select all
[ 8902.545792] hub 1-0:1.0: over-current change on port 5
[ 8902.648092] hub 3-0:1.0: over-current change on port 2
[ 8902.760113] hub 4-0:1.0: over-current change on port 1
[ 9033.248991] hub 1-0:1.0: over-current change on port 2
[ 9033.356071] hub 2-0:1.0: over-current change on port 1
[ 9033.472678] hub 2-0:1.0: over-current change on port 2
[ 9163.518845] hub 1-0:1.0: over-current change on port 4
[ 9163.628047] hub 1-0:1.0: over-current change on port 5
[ 9163.736087] hub 4-0:1.0: over-current change on port 1
[ 9163.844099] hub 3-0:1.0: over-current change on port 2
[ 9330.497743] hub 1-0:1.0: over-current change on port 4
[ 9330.604069] hub 1-0:1.0: over-current change on port 5
[ 9330.712078] hub 3-0:1.0: over-current change on port 2
[ 9330.820078] hub 1-0:1.0: over-current change on port 1
[ 9330.928069] hub 1-0:1.0: over-current change on port 2
[ 9331.036068] hub 1-0:1.0: over-current change on port 4
[ 9331.144063] hub 2-0:1.0: over-current change on port 1
[ 9331.257498] hub 2-0:1.0: over-current change on port 2
[ 9331.813612] hub 4-0:1.0: over-current change on port 1
[ 9629.512122] hub 2-0:1.0: over-current change on port 1
[ 9629.636772] hub 2-0:1.0: over-current change on port 2
[ 9908.016240] hub 4-0:1.0: over-current change on port 1
[10367.021995] hub 1-0:1.0: over-current change on port 4
[10367.172809] hub 1-0:1.0: over-current change on port 5
[11452.560114] hub 4-0:1.0: over-current change on port 1
[11452.704104] hub 1-0:1.0: over-current change on port 4
[11452.820046] hub 1-0:1.0: over-current change on port 5Code: Select all
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 2: Dev 2, If 0, Class=>ifc, Driver=lirc_igorplugusb, 1.5M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 2: Dev 7, If 0, Class=vend., Driver=ftdi_sio, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M
|__ Port 4: Dev 14, If 0, Class=vend., Driver=go7007, 480M
|__ Port 5: Dev 15, If 0, Class=vend., Driver=go7007, 480MI know that FitPC has a non standard power supply for USB peripherals, and I think OS can't really know if my peripherals are requesting much current, that I know isn't so.
I made a lot of test about USB connection for vibration issues, and finally I soldered the wires on motherboard and on the external board. So I can realize that isn't vibration that disconnect for a really short time the peripherals.
I'm sure the problem is somewhere else.
Have you some suggestion about what can produce this messages on the kernel?
Thank you very much, Davide