From: Robert Hancock <rwh461@mail.usask.ca>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Logs being spammed with "Unable to enumerate USB device"
Date: Tue, 23 Sep 2008 18:14:19 -0600 [thread overview]
Message-ID: <48D9865B.8080806@mail.usask.ca> (raw)
In-Reply-To: <fa.dl+pVhW/kcgBFo0dsyPEgn0MhtE@ifi.uio.no>
Larry Finger wrote:
> At times, my logs are filled with multiple copies of the following
> message:
>
> hub 4-0:1.0: unable to enumerate USB device on port 5
>
> The output of lsusb is as follows:
>
> Bus 003 Device 002: ID 04f2:b016 Chicony Electronics Co., Ltd
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> The hubs are built into an HP dv2815nr laptop, and nothing is plugged in.
>
> I'm currently running v2.6.27-rc7 from the linux-2.6 git tree, but it
> does not seem to be a regression. In checking my back logs, my first
> such "storm" happened on July 25, with successive ones on September 8,
> 9, 12 and 21.
>
> Is this an indication of hardware failure? What further info is
> required? Any suggestions for debugging code to try to pinpoint the
> problem?
Is this just occurring during bootup? I think this is normal if the EHCI
driver is loaded after UHCI or OHCI because it causes the device to be
switched away from the other controller that's trying to enumerate it,
at least momentarily.
next parent reply other threads:[~2008-09-24 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.dl+pVhW/kcgBFo0dsyPEgn0MhtE@ifi.uio.no>
2008-09-24 0:14 ` Robert Hancock [this message]
2008-09-24 1:00 ` Logs being spammed with "Unable to enumerate USB device" Larry Finger
2008-09-30 23:38 ` Larry Finger
2008-09-22 18:37 Larry Finger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48D9865B.8080806@mail.usask.ca \
--to=rwh461@mail.usask.ca \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox