From: Frans Pop <elendil@planet.nl>
To: linux-kernel@vger.kernel.org
Cc: Gene Heskett <gene.heskett@gmail.com>
Subject: Re: 2.6.25.1, stray noise in dmesg
Date: Fri, 2 May 2008 19:10:44 +0200 [thread overview]
Message-ID: <200805021910.45266.elendil@planet.nl> (raw)
In-Reply-To: <200805021126.15225.gene.heskett@gmail.com>
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):
USB Universal Host Controller Interface driver v3.0
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb5: configuration #1 chosen from 1 choice
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
usb 3-1: new low speed USB device using uhci_hcd and address 2
usb 3-1: configuration #1 chosen from 1 choice
usb 4-1: new low speed USB device using uhci_hcd and address 2
usb 4-1: configuration #1 chosen from 1 choice
With 2.6.25 the 2 "unable to enumerate" lines were not there.
The changing order in which USB busses are detected makes comparison
awkward, but these seem to be the only new lines.
$ lsusb # with 2.6.25-git
Bus 005 Device 001: ID 1d6b:0002
Bus 004 Device 002: ID 046d:c50d Logitech, Inc.
Bus 004 Device 001: ID 1d6b:0001
Bus 003 Device 002: ID 05a4:9841 Ortek Technology, Inc.
Bus 003 Device 001: ID 1d6b:0001
Bus 001 Device 001: ID 1d6b:0001
Bus 002 Device 001: ID 1d6b:0001
$ lsusb #with 2.6.25
Bus 005 Device 002: ID 046d:c50d Logitech, Inc.
Bus 005 Device 001: ID 1d6b:0001
Bus 004 Device 002: ID 05a4:9841 Ortek Technology, Inc.
Bus 004 Device 001: ID 1d6b:0001
Bus 003 Device 001: ID 1d6b:0001
Bus 002 Device 001: ID 1d6b:0002
Comparing the two there is one "new" device. Strange that "Bus 001" is
missing in lsusb with 2.6.25 because dmesg does mention it as assigned.
next prev parent reply other threads:[~2008-05-02 17:10 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 [this message]
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=200805021910.45266.elendil@planet.nl \
--to=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