Hi,
I've been trying to setup some recently-acquired hardware and
encountered what I perceive to be possible bugs in the xHCI code.
Specifically, I've got a Shuttle SH51R4, which utilises an ASMedia
ASM1042 chipset (seemingly xHCI compliant) and I'm trying to connect a
HotWay h82-su3s2 external drive chassis. Inside the chassis, I have
connected four Hitachi Deskstar 7k3000 drives. For confirmation
purposes, I have successfully used this setup in Windows 7 and achieved
well over 100MB/s transfer rates on a per-drive basis. The config also
works when plugged into a USB 2 port in all Linux Kernel's I've tried.
Without exception, I've experienced catastrophic failures using the xHCI
drivers in varying kernel versions. Under CentOS 6.0's customised
2.6.32 kernel, connecting the drive chassis hard-locks the PC and I
would assume has caused a kernel panic. Under more recent kernels, a
volume of errors are produced, notably 'WARN: Stalled endpoint' which
then seems to degenerate into a cascade of resulting errors. The
debugging below is on 3.1.0-RC4 however is equally representative of
several other kernel versions tested.
On the system I've been testing, the connected drives are resolved as
sdc, sdd, sde and sdf.
Rather than attach slabs of text for the errors, I've uploaded the
various debugging outputs that I assume you'd require:
dmesg: http://pastebin.com/raw.php?i=PdUqCtzw
lsusb -v: http://pastebin.com/raw.php?i=JW0L3BPa
lsusb -vvv: http://pastebin.com/raw.php?i=yRRcUp31
lspci -vvv: http://pastebin.com/raw.php?i=Bt3vtJ1E
Thank you in advance of your help.
Cheers,
Matt.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
