On Tue, Feb 05, 2002 at 02:49:34PM +0530, Phani Ram wrote:
>
> hi ,
> I am encountering the following error with kernel - 2.4 .14 and the fixed
> toggle patch posted a few days back(usb-uhci version 1.275 ) applied .
>
> I even tried with uhci.c( 2.4 .14) with the patch applied for fixed toggle
> as well but to no avail.
>
> The USB Bluetooth device from CSR is being used over USB . While ftp'ing ,
> the 'ls ' command prompts the following error====>
>
> usb-uhci.c: interrupt , status 3 , frame# 219
> usb-uhci.c: interrupt , status 3 , frame# 219
Not good, looks like an error in either the device or the bluetooth driver.
> bluetooth.c: bluetooth_write_bulk_callback
> last message repeated 3 times
> usb-uhci.c : process_transfer: fixed toggle
> usb-uhci.c: process_transfer:fixed toggle
>
> bluetooth.c:bluetooth_write_bulk_callback - nonzero write bulk status
> received - 110
>
> after that , i receive messages from
> hub.c:port 1 connenction change
> usb.c: USB disconnect on device 2
The device disconnects itself from USB, a strange behavior...
> Any patch to fix the above problem ????
>
> Why is the fixed_toggle coming up ??? Is it a problem with data
> synchronisation when handling fast data transfer over bluetooth ?
The "fixed toggle" message appears when a short bulk read appears, while
there are queued bulk reads behind it. Due to the dumbness of the UHCI-chip
this event may need correction of the data toggles all the queued
descriptors for this pipe. Guessing from the log info above, this seems to
be not the root cause for the problem...
--
Georg Acher, [EMAIL PROTECTED]
http://www.in.tum.de/~acher/
"Oh no, not again !" The bowl of petunias
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
