usb/82660: EHCI: I/O stuck in state 'physrd'/panic

[Stefan Walter]

>Number:         82660
>Category:       usb
>Synopsis:       EHCI: I/O stuck in state 'physrd'/panic
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jun 26 09:20:10 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Stefan Walter
>Release:        FreeBSD 5.4-STABLE i386
>Organization:
Infinity Approximation Task Force
>Environment:
System: FreeBSD kyuzo.dunkelkammer.void 5.4-STABLE FreeBSD 5.4-STABLE #0: Fri Jun 24 15:41:24 CEST 2005 root at kyuzo.dunkelkammer.void:/usr/src/sys/i386/compile/KYUZO i386
>Description:
After updating to a recent RELENG_5 (see environment data), I thought I'd give
USB 2.0 a try to speed up data exchange with my USB sticks. The controller is
correctly identified, it seems:

ehci0: <VIA VT6202 USB 2.0 controller> mem 0xdbfdf700-0xdbfdf7ff irq 3 at device 16.3 on pci0

When plugging in an USB stick, it is correctly identified, too:

umass0: USB Flash Disk, rev 2.00/2.00, addr 2
da2 at umass-sim0 bus 0 target 0 lun 0
da2: < USB BAR 2.00> Removable Direct Access SCSI-2 device
da2: 40.000MB/s transfers
da2: 124MB (255744 512 byte sectors: 64H 32S/T 124C)

I can also list the content of the FAT filesystem with mtools' mdir command.
When trying to copy a file from the stick to a local filesystem, however,
mcopy is almost immediately stuck in state "physrd" (according to top(1))
after copying a varying number of bytes (between 100 and 2200 KB is what I've
seen so far). I cannot kill the mtools process, but pulling out the USB stick
helps - it panics some time after doing that, though.

The same happens when trying to dump the whole USB stick to a file with
"dd if=/dev/da2 of=stickimage bs=1024". The dd process also hangs in state
"physrd" eventually.

It doesn't seem to be a problem with IRQ sharing, as both "vmstat -i" and
dmesg indicate that ehci0 doesn't share its IRQ with anything else. The USB
stick works fine (with ehci, too) on a notebook with an Intel ICH4 chipset.
>How-To-Repeat:
	
>Fix:

	


>Release-Note:
>Audit-Trail:
>Unformatted: