From: Greg KH <greg@kroah.com>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25.1, stray noise in dmesg
Date: Fri, 2 May 2008 09:14:47 -0700 [thread overview]
Message-ID: <20080502161447.GB6852@kroah.com> (raw)
In-Reply-To: <200805021126.15225.gene.heskett@gmail.com>
On Fri, May 02, 2008 at 11:26:15AM -0400, Gene Heskett wrote:
> Greetings;
>
> 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
> And lsusb:
> [root@coyote ~]# lsusb
> Bus 001 Device 011: ID 04b8:010f Seiko Epson Corp. Perfection 1250
> Bus 001 Device 010: ID 046d:c510 Logitech, Inc.
> Bus 001 Device 009: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
> Bus 001 Device 008: ID 0409:0059 NEC Corp. HighSpeed Hub
> Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
> Bus 001 Device 006: ID 050d:0751 Belkin Components
> Bus 001 Device 002: ID 0409:0059 NEC Corp. HighSpeed Hub
> Bus 001 Device 001: ID 1d6b:0002
> Bus 003 Device 002: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
> Bus 003 Device 001: ID 1d6b:0001
> Bus 002 Device 003: ID 06a3:8021 Saitek PLC Eclipse II Keyboard
> Bus 002 Device 002: ID 04b8:0005 Seiko Epson Corp. Stylus Printer
> Bus 002 Device 001: ID 1d6b:0001
>
> Indicating 3 empty ports, which is not correct either, but everything
> that is plugged in is accounted for. However, if there is no device
> there, is it supposed to tell us? In which case it should do that 2-3
> more times in dmesg.
That's because your hardware is trying to enumerate a device, yet there
really isn't one there at all. Blame the hardware :)
This warning is new, but it's needed as we now notice if we fail to
enumerate a device that might really be there.
thanks,
greg k-h
next prev parent reply other threads:[~2008-05-02 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 15:26 Gene Heskett
2008-05-02 16:14 ` Greg KH [this message]
2008-05-02 17:10 ` Frans Pop
2008-06-05 18:50 ` Frans Pop
2008-06-05 19:38 ` Greg KH
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=20080502161447.GB6852@kroah.com \
--to=greg@kroah.com \
--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
Powered by JetHome