USB2514 HUB: Only Port 4 Works for Passive Devices

Hello.

I'm having a rather weird problem with a USB2514-based 4-port HUB design that is connected to my own board having a PXA320 uController using an R8A66597FP as USB Controller.

When plugging a passive device - ie. one to be powered from the HUB - into ports 1-3, the Linux driver for the USB Controller reports

usb 2-1.4.1.1: new full-speed USB device number 8 using r8a66597_hcd
usb 2-1.4.1.1: device descriptor read/64, error -104
usb 2-1.4.1.1: device descriptor read/64, error -104
usb 2-1.4.1.1: new full-speed USB device number 9 using r8a66597_hcd
usb 2-1.4.1.1: device descriptor read/64, error -104
usb 2-1.4.1.1: device descriptor read/64, error -104
usb 2-1.4.1.1: new full-speed USB device number 10 using r8a66597_hcd
usb 2-1.4.1.1: device not accepting address 10, error -104
usb 2-1.4.1.1: new full-speed USB device number 11 using r8a66597_hcd
usb 2-1.4.1.1: device not accepting address 11, error -104
hub 2-1.4.1:1.0: unable to enumerate USB device on port 1

but accepts and enumerates the device correctly, when plugged into port 4.

Active, self-powered devices, however, are recognized and enumerated correctly on all 4 ports.

The above pattern exists for both a built-in USB2514-based HUB on my own PCB and for an external Evaluation Board with the USB2514.

When plugging the Evaluation Board HUB to eg. a Windows PC, all 4 ports are also working as expected.

The error -104 "Connection Reset by Peer" is sledomly observed and described, but most people tend to suspect some sort of a power issue for this type of error.
However, I cannot figure out why this should always be a problem for ports 1-3, while port 4 always operates as expected...
So... I would suspect some sort of software-dependent "feature"...

Does anybody here have some clues and/or experiences?

Thanks.

Best regards - Jesper K.