Here is a set of USB patches against your current git tree.
They do a lot of different things, mostly all new driver updates and

powermanagement changes for the USB layer.  The shortlog below has all

the details.
Please pull from:

	master.kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6.git/
All of these patches have been in the linux-next and -mm tree for quite

some time.
The full patches will be sent to the linux-usb-devel mailing list, if

anyone wants to see them.
thanks,
greg k-h
 Documentation/usb/anchors.txt          |   50 +

 Documentation/usb/callbacks.txt        |  132 +

 Documentation/usb/persist.txt          |   43 +-

 Documentation/usb/usb-serial.txt       |    7 +-

 drivers/input/joystick/xpad.c          |   20 +-

 drivers/usb/atm/cxacru.c               |    2 +-

 drivers/usb/atm/ueagle-atm.c           |    6 +-

 drivers/usb/atm/usbatm.c               |   27 +-

 drivers/usb/atm/usbatm.h               |    2 +-

 drivers/usb/class/cdc-acm.c            |   98 +-

 drivers/usb/class/cdc-acm.h            |    7 +-

 drivers/usb/core/Kconfig               |   42 +-

 drivers/usb/core/config.c              |   17 +

 drivers/usb/core/devio.c               |   73 +-

 drivers/usb/core/driver.c              |   52 +-

 drivers/usb/core/hcd-pci.c             |   15 +-

 drivers/usb/core/hcd.c                 |   25 +-

 drivers/usb/core/hcd.h                 |    9 +-

 drivers/usb/core/hub.c                 |  396 ++-

 drivers/usb/core/hub.h                 |    9 +-

 drivers/usb/core/inode.c               |    4 +-

 drivers/usb/core/message.c             |   17 +-

 drivers/usb/core/quirks.c              |   14 +

 drivers/usb/core/sysfs.c               |   22 +-

 drivers/usb/core/urb.c                 |   26 +-

 drivers/usb/core/usb.h                 |    2 -

 drivers/usb/gadget/Kconfig             |   18 +-

 drivers/usb/gadget/amd5536udc.c        |   10 +

 drivers/usb/gadget/at91_udc.c          |    9 +-

 drivers/usb/gadget/dummy_hcd.c         |   98 +-

 dr...
[ message continues ]

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 ;)
Full dmesg appended, in case it tells you something.
			Linus
---

Linux version 2.6.25-05086-g3dd7b71 (torvalds@woody.linux-foundation.org) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #121 SMP Fri Apr 25 15:51:55 PDT 2008

Command line: rhgb quiet

BIOS-provided physical RAM map:

 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)

 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)

 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)

 BIOS-e820: 0000000000100000 - 00000000cf585000 (usable)

 BIOS-e820: 00000000cf585000 - 00000000cf591000 (reserved)

 BIOS-e820: 00000000cf591000 - 00000000cf62b000 (usable)

 BIOS-e820: 00000000cf62b000 - 00000000cf6a6000 (ACPI NVS)

 BIOS...
[ message continues ]

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

--

That's right.  For some reason those hubs must report connections on

those ports even though nothing is actually attached.  When the kernel

tries to enumerate them, naturally it fails.
Previously there were error pathways in the enumeration code in which

we would never log an error message, which meant that people had no

indication there really was a problem.  That's why this message was

added.
But it looks like the new message may show up more often than we want.

I've seen it happen when a low- or full-speed device is plugged into a

high-speed bus, because of the port handover.  This may be the same

sort of thing or it may be something different; I can't tell without

the verbose USB debugging log.
In any event the message is indeed harmless.  It doesn't represent a

real change in behavior; it simply reports a potential error that

previously would go unreported.
Alan Stern
--