public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Alan Stern <stern@rowland.harvard.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [GIT PATCH] USB patches for 2.6.25-git
Date: Fri, 25 Apr 2008 17:20:04 -0700	[thread overview]
Message-ID: <20080426002004.GA23817@suse.de> (raw)
In-Reply-To: <alpine.LFD.1.10.0804251645190.2813@woody.linux-foundation.org>

On Fri, Apr 25, 2008 at 04:51:51PM -0700, Linus Torvalds wrote:
> 
> 
> On Thu, 24 Apr 2008, Greg KH wrote:
> >
> > Here is a set of USB patches against your current git tree.
> 
> Hmm. This seesm to have brought with it some new errors.
> 
> >From my dmesg:
> 
> 	ACPI: PCI Interrupt 0000:00:1a.1[B] -> GSI 21 (level, low) -> IRQ 21
> 	PCI: Setting latency timer of device 0000:00:1a.1 to 64
> 	uhci_hcd 0000:00:1a.1: UHCI Host Controller
> 	uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
> 	uhci_hcd 0000:00:1a.1: irq 21, io base 0x00002080
> 	usb usb4: configuration #1 chosen from 1 choice
> 	hub 4-0:1.0: USB hub found
> 	hub 4-0:1.0: 2 ports detected
> **	hub 1-0:1.0: unable to enumerate USB device on port 4
> 	usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
> 	usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> 	usb usb4: Product: UHCI Host Controller
> 	usb usb4: Manufacturer: Linux 2.6.25-05086-g3dd7b71 uhci_hcd
> 	usb usb4: SerialNumber: 0000:00:1a.1
> 
> there's a few of them there, and they seem to be new (ie they don't show 
> up in my previous message logs). dmesg | grep shows a total of four:
> 
> 	hub 1-0:1.0: unable to enumerate USB device on port 4
> 	hub 2-0:1.0: unable to enumerate USB device on port 2
> 	hub 2-0:1.0: unable to enumerate USB device on port 3
> 	hub 2-0:1.0: unable to enumerate USB device on port 4
> 
> but things seem to work. Whether that is because I don't have anything 
> *connected* at those ports or not, I don't know ;)

This was always happening before, but now we are actually logging the
error.  Commit 6427f7995338387ddded92f98adec19ddbf0ae5e was the one, and
Alan Stern added it to the tree to help try to determine some reports
that people had been having at times.

It should be harmless, right Alan?

thanks,

greg k-h

  reply	other threads:[~2008-04-26  0:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25  4:53 [GIT PATCH] USB patches for 2.6.25-git Greg KH
2008-04-25 23:51 ` Linus Torvalds
2008-04-26  0:20   ` Greg KH [this message]
2008-04-26 20:12     ` Alan Stern
  -- strict thread matches above, loose matches on Subject: below --
2008-05-02 17:30 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=20080426002004.GA23817@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    --cc=torvalds@linux-foundation.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