public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, Gene Heskett <gene.heskett@gmail.com>
Subject: Re: 2.6.25.1, stray noise in dmesg
Date: Thu, 5 Jun 2008 12:38:15 -0700	[thread overview]
Message-ID: <20080605193815.GA32072@kroah.com> (raw)
In-Reply-To: <200806052050.34537.elendil@planet.nl>

On Thu, Jun 05, 2008 at 08:50:33PM +0200, Frans Pop wrote:
> On Friday 02 May 2008, Frans Pop wrote:
> > Gene Heskett wrote:
> > > I just rebooted to 2.6.25.1, and was momentarily panic'd by the
> > > messages going by early in the boot, but on putting 2&2 together,
> > > found they were just noise.
> > >
> > > From dmesg:
> > > [root@coyote ~]# dmesg|grep unable
> > > [    2.093502] hub 1-0:1.0: unable to enumerate USB device on port 2
> > > [    2.248475] hub 1-0:1.0: unable to enumerate USB device on port 5
> > > [    2.454444] hub 1-0:1.0: unable to enumerate USB device on port 6
> >
> > I'm seeing these too (hub 5-0):
> > hub 5-0:1.0: USB hub found
> > hub 5-0:1.0: unable to enumerate USB device on port 5
> > hub 5-0:1.0: unable to enumerate USB device on port 7
> 
> I'm going to bring this up one last time.
> 
> Google currently already shows 1060 hits for this new error:
> http://www.google.com/search?q=%22unable+to+enumerate+USB+device%22&ie=UTF-8&oe=UTF-8
> 
> This one is particularly interesting as it shows quite a few systems
> are affected: https://bugzilla.redhat.com/show_bug.cgi?id=446845
> 
> Given its apparent prevalence I'm still wondering whether this is
> really broken hardware in all cases or that there could be an error
> in detection in some cases.
> 
> Note that in my case this is not with an external hub or anything, but just
> the internal USB ports of the system.
> 
> One thing with this message is that because of its "error" status, it
> also shows when the system is booted with the "quiet" option. Could it be
> an option to apply the following patch so that at least that is avoided?

I agree, I'll change the message to be this, thanks for the patch.

greg k-h

  reply	other threads:[~2008-06-05 19:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 15:26 2.6.25.1, stray noise in dmesg Gene Heskett
2008-05-02 16:14 ` Greg KH
2008-05-02 17:10 ` Frans Pop
2008-06-05 18:50   ` Frans Pop
2008-06-05 19:38     ` Greg KH [this message]
2008-06-06 12:55       ` Frans Pop
2008-06-06 20:42         ` Greg KH

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=20080605193815.GA32072@kroah.com \
    --to=greg@kroah.com \
    --cc=elendil@planet.nl \
    --cc=gene.heskett@gmail.com \
    --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