Mailing List Archive

2.6.25.1, stray noise in dmesg
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.

I realize this is picking minor nits. :)

Thanks.

--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Shick's Law:
There is no problem a good miracle can't solve.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25.1, stray noise in dmesg [ In reply to ]
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25.1, stray noise in dmesg [ In reply to ]
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25.1, stray noise in dmesg [ In reply to ]
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?

---
From: Frans Pop <elendil@planet.nl>

usb core: lower severity of 'unable to enumerate USB device' message

This message is relatively common and in most cases can be safely
ignored. Lower its severity from 'err' to 'notice' so it is not printed
on the console when systems are booted with the "quiet" boot parameter.

Signed-off-by: Frans Pop <elendil@planet.nl>

diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
index 8eb4da3..ea1ef37 100644
--- a/drivers/usb/core/hub.c
+++ b/drivers/usb/core/hub.c
@@ -2756,7 +2756,7 @@ loop:
if (hub->hdev->parent ||
!hcd->driver->port_handed_over ||
!(hcd->driver->port_handed_over)(hcd, port1))
- dev_err(hub_dev, "unable to enumerate USB device on port %d\n",
+ dev_notice(hub_dev, "unable to enumerate USB device on port %d\n",
port1);

done:
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25.1, stray noise in dmesg [ In reply to ]
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25.1, stray noise in dmesg [ In reply to ]
On Thursday 05 June 2008, Greg KH wrote:
> On Thu, Jun 05, 2008 at 08:50:33PM +0200, Frans Pop wrote:
> > On Friday 02 May 2008, Frans Pop wrote:
> > > 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
> >
> > 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.

I'm not sure that it is needed anymore. Looks like for me the messages
have disappeared with -rc5, probably due to 3a31155cfff0935e (Alan Stern,
"USB: EHCI: suppress unwanted error messages").
So it wasn't broken hardware after all :-)

If that solves all or most cases the error was being hit, lowering its
severity is probably not needed.

Cheers,
FJP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25.1, stray noise in dmesg [ In reply to ]
On Fri, Jun 06, 2008 at 02:55:55PM +0200, Frans Pop wrote:
> On Thursday 05 June 2008, Greg KH wrote:
> > On Thu, Jun 05, 2008 at 08:50:33PM +0200, Frans Pop wrote:
> > > On Friday 02 May 2008, Frans Pop wrote:
> > > > 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
> > >
> > > 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.
>
> I'm not sure that it is needed anymore. Looks like for me the messages
> have disappeared with -rc5, probably due to 3a31155cfff0935e (Alan Stern,
> "USB: EHCI: suppress unwanted error messages").
> So it wasn't broken hardware after all :-)
>
> If that solves all or most cases the error was being hit, lowering its
> severity is probably not needed.

Ah, nevermind then, I'll not worry about this :)

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/