[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bluetooth-dev] problems encountered when using USB



The P9A seems to have some bugs in it.  We aren't sure what workarounds
will work (since it supposedly works under windows)  There have been
some indications that this is caused by a firmware crash.  I do not know
if there are update firmware drivers.  I have seen similar problems in
my own devices, but usually my devices fail to receive the
NUM_COMPLETED_PACKETS message.

I am not sure what is causing the packet too long message.  The best way
to debug this is to turn on full debugging in the USB driver and
recompile.  That way you should get full prinouts of each packet
received.  Then you have to tediously decode the packets by hand and
figure out what is going on.

Basically some packet is coming in with a length that does not match the
overall length of the packet.  This confuses the USB driver.  

Turn on the debugging and start looking for the packets that screw up
the driver.  Let me know what you find out, but definitely put in some
time looking at it yourself and then let us know what it looks like. 

Thanks.


> hi all,
> 
> i tried to use USB to connect the bt device to the host pc. it seems that
> the bt usb driver in the kernel tree is not very stable, pc hung frequently.
> 
> i was  able to setup the PPP connection btw 2 bt devices. and i used 'ping
> xxx.xxx.xxx.xxx -I ppp0' to ping the remote machine, the link worked fine,
> no packect was lost. however, when i ran a http sever at one side and tried
> to retrive a html from the remote side using that link, the link was down,
> no data could be received any more. 
> log messages (server side) attached below showed that the bt device was
> disconneted and reconnected automatically. any idea about this situation?
> 
> my system info: redhat 6.2 (2.2.18 kernel)
>                 axis stack v20001115
>                 bt firmware P9A
> server ./btduser -i  usb -d xxx.xxx.xxx.xxx -D xxx.xxx.xxx.xxx -e 0 -m
> client ./btduser -i  usb -d xxx.xxx.xxx.xxx -D xxx.xxx.xxx.xxx -e 0 -r
> client
> 
> you help will be appreciated!!
> 
> best regards,
> liu yong
> 
> Jan 16 13:02:53 clearfire btduser: Initiating signal handler 
> Jan 16 13:02:53 clearfire btduser: Opening socket /tmp/ipa_server 
> Jan 16 13:02:53 clearfire btduser: open_socket /tmp/ipa_server failed
> Jan 16 13:02:53 clearfire btduser: Could not find IP Assign server 
> Jan 16 13:02:53 clearfire btduser: Starting SDP server 
> Jan 16 13:02:53 clearfire kernel: usb-uhci.c: ENXIO c0418280, flags 0, urb
> c7bd8820, burb c7bd8820 
> Jan 16 13:02:53 clearfire kernel: usb-uhci.c: ENXIO 40428280, flags 0, urb
> c7bd7860, burb c7bd7860 
> Jan 16 13:02:54 clearfire btduser: Current HW set to USB 
> Jan 16 13:02:54 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 836 
> Jan 16 13:02:54 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 844 
> Jan 16 13:02:55 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 1844 
> Jan 16 13:02:55 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 1845 
> Jan 16 13:02:55 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 1854 
> Jan 16 13:02:55 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 1855 
> Jan 16 13:02:56 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 808 
> Jan 16 13:03:07 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 1162 
> Jan 16 13:15:48 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 957 
> Jan 16 13:15:54 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 849 
> Jan 16 13:15:54 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 859 
> Jan 16 13:17:35 clearfire btduser: build_pppdopt
> Jan 16 13:17:35 clearfire btduser: IP addresses used :
> 155.69.145.173:155.69.145.165
> Jan 16 13:17:35 clearfire btduser: start pppd...
> Jan 16 13:17:35 clearfire btduser: Spawned pppd[870] in the background
> Jan 16 13:17:35 clearfire btduser: Starting ppp server on /dev/ttyBT0
> Jan 16 13:17:35 clearfire modprobe: modprobe: Can't locate module ppp0
> Jan 16 13:17:35 clearfire kernel: registered device ppp0 
> Jan 16 13:17:35 clearfire pppd[870]: pppd 2.3.11 started by root, uid 0
> Jan 16 13:17:35 clearfire pppd[870]: Using interface ppp0
> Jan 16 13:17:35 clearfire pppd[870]: Connect: ppp0 <--> /dev/pts/3
> Jan 16 13:17:40 clearfire pppd[870]: not replacing existing default route to
> eth0 [155.69.151.254]
> Jan 16 13:17:40 clearfire pppd[870]: found interface eth0 for proxy arp
> Jan 16 13:17:40 clearfire pppd[870]: local  IP address 155.69.145.173
> Jan 16 13:17:40 clearfire pppd[870]: remote IP address 155.69.145.165
> Jan 16 13:20:31 clearfire kernel: bluetooth.c: bluetooth_int_callback -
> packet was too long 
> Jan 16 13:20:43 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 1328 /*lots of them*/
> 
> Jan 16 13:20:44 clearfire kernel: usb.c: USB disconnect on device 2 /*be
> disconnected*/
> Jan 16 13:20:44 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 1444 /*lots of them*/
> Jan 16 13:20:44 clearfire kernel: bluetooth.c: Bluetooth converter now
> disconnected from ttyUB0 /*reconnected*/
> Jan 16 13:20:44 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 1464 /*lots of them*/
> Jan 16 13:20:44 clearfire kernel: usb-uhci.c: interrupt, stcallback 
> Jan 16 13:20:44 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 1720 /*lots of them*/
> Jan 16 13:20:44 clearfire kernel:  status received: -84 
> Jan 16 13:20:44 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 1966 /*lots of them*/
> Jan 16 13:20:45 clearfire kernel: usb-uhci.c: interrupt,
> sth_read_bulk_callback 
> Jan 16 13:20:45 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 440 /*lots of them*/
> Jan 16 13:20:45 clearfire kernel: usb.c: USB new device connect, assigned
> device number 2 
> Jan 16 13:20:45 clearfire kernel: usb-uhci.c: interrupt, status 3, frame#
> 1216 /*lots of them*/
> Jan 16 13:20:46 clearfire kernel: Manufacturer: Ericsson 
> Jan 16 13:20:46 clearfire kernel: Product: Bluetooth Device 
> Jan 16 13:20:46 clearfire kernel: bluetooth.c: USB Bluetooth converter
> detected 
> Jan 16 13:20:46 clearfire kernel: bluetooth.c: Bluetooth converter now
> attached to ttyUB0 (or usb/ttub/0 for devfs) 
> Jan 16 13:27:50 clearfire pppd[870]: Terminating on signal 2.
> Jan 16 13:27:50 clearfire btduser: Killing SDP server 
> Jan 16 13:27:50 clearfire btduser: Killing pppd 
> Jan 16 13:27:50 clearfire btduser: Shutting down bluetooth stack 
> Jan 16 13:27:50 clearfire pppd[870]: Terminating on signal 15.
> Jan 16 13:27:56 clearfire pppd[870]: Connection terminated.
> Jan 16 13:27:56 clearfire pppd[870]: Connect time 10.3 minutes.
> Jan 16 13:27:56 clearfire pppd[870]: Sent 27104 bytes, received 17627 bytes.
> Jan 16 13:27:56 clearfire pppd[870]: Exit.
> -
> To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
> the body of a message to majordomo@xxxxxxx.com



-- 
----                                                                   
Mark Corner                                      
mcorner@xxxxxxx.edu
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com