Overo USB (hub 1-0:1.0) enumerate error messages generated without apparent cause
David Perez <dpplopez <at> gmail.com>
2014-09-06 16:26:55 GMT
I have an Overo Earth with Tobi connected to an externally powered USB
camera using the OTG port. The system works fine (even after the event I'm
about to describe).
Several days ago, my terminal (connected to Overo using the Console port)
started to show this message repeatedly:
There was no apparent cause for the message to appear: no hardware issue I
was aware of, no change in system configuration... I was just using the
Overo system to develop my application and to carry out tests. But even no
problem at all with the USB camera and my application, which is able to
access the webcam and works fine.
The message seems to refer to the HOST USB port (correct me if I'm wrong: I
have assumed this from the dmesg log below), which I have never used: when
the problem started there was nothing connected to that port. As stated
before, my only USB device is a webcam camera with external power. The
messages regarding the webcam detection and loading show no problem and no
noticeable difference from webcam related messages before this problem
started (I'm not reporting these messages here to keep the post within a
reasonable extension; if required, let me know).
The problematic messages appear in dmesg as soon as the EHCI driver is
loaded, the usb1 bus is registered and the OMAP-EHCI Host Controller is
found and added as 1-0:1.0. Everything seems ok in the messages related to
After this, some additional messages related to the OTG USB port and other
devices initialization appear. But then, just several milliseconds later,
the following messages start to appear repeatedly, intermixed with other
This set of messages go on coming out forever. The system starts up without
problem (appart from the cluttering of my terminal, which I stop by calling
dmesg -n 1), but the messages go on for a long while. Sometimes, they stop
with the following:
I don't know if this (usb1 is autosuspended and messages stop) happens
always or not. I do know that in several tests I have seen dmesg timestamps
of 1500 or higher, while in other tests (like the one reported above) the
suspension kicks in before.
My system kernel:
I'm not an expert on Linux or Overo at all, and thus I could be overseeing
something important. I have read on other posts that some kernel versions
had problems similar to this.
Does anyone have any hint on the possible cause of this?
Also, as my system seems to be working, is it safe to just remove the
offending messages from the terminal and use the board? Is it possible to
somehow disable the unused HOST USB port to avoid this?
And, by the way, what device does the message refer to? What is the
offending device that cannot be enumerated?
Thank you so much in advance,
View this message in context: http://gumstix.8.x6.nabble.com/Overo-USB-hub-1-0-1-0-enumerate-error-messages-generated-without-apparent-cause-tp4969450.html
Sent from the Gumstix mailing list archive at Nabble.com.
Video for Nerds. Stuff that matters.