On Monday 18 December 2006 11:19 pm, Will Tucker wrote:
> U-Boot 1.1.3 (Jun 5 2006 - 16:57:39)
> Uncompressing
> Linux.............................................................
> ................................. done, booting the.Linux version
> 2.6.10_mvl401-
> davinci_evm ([EMAIL PROTECTED]) (gcc version 3.4.3 (MontaVista
> 3.4.3-25.0.30.0501131 20
> 05-07-23)) #35 Mon Dec 18 16:48:24 MST 2006
>
>
> I'm not a Linux expert...
>
> As far as I can tell, a message is sent to the usb driver
More likely to the "usb device". And there are devices that misbehave,
no fault of the USB host side but just flakey device firmware.
> and it doesn't respond. See the red
Text messages don't include color. :)
> 1) How would a Linux expert go about fixing this?
> - What kind of more information do I need to supply?
Turn on USB debugging in kernel config. Nothing you've shown suggests
USB is the issue here, but at least it's known you can get a lot more
information about what's going on by a detailed USB trace. musb_hdrc
supports its own debugging, with potentially obscenely verbose levels
of event tracing; read the source code to see what's going on,
/proc/driver/musb_hdrc can be written to change the tracing level.
But more usual is just
> - Is there any commands I can perform to debug more?
Well you could _start_ debugging as desribed above; what you show
below would be at the wrong level if this were a USB problem rather
than, for example, a bug in the Bluetooth stack.
> - Who would know how to fix this?
> - I also have the same issue on the git tree.
It's useful to know the issue (whatever it is!) is still open.
- Dave
> Thanks,
>
> Will
>
> Debug mostly from hci_core.c
>
> [EMAIL PROTECTED]:~# lsusb
> Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
> Bus 001 Device 001: ID 04d6:0000 Mentor Graphics
> [EMAIL PROTECTED]:~# hciconfig
> hci_sock_create: sock c67c5a60
> hci_sock_ioctl: cmd 800448d2 arg 26008
> hci_sock_ioctl: cmd 800448d3 arg 253e4
> hci_dev_get: 0
> hci0: Type: USB
> BDhci_sock_release: sock c67c5a60 sk c07aab60
> Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
> DOWN
> RX bytes:0 acl:0 sco:0 events:0 errors:0
> TX bytes:0 acl:0 sco:0 commands:0 errors:0
> [EMAIL PROTECTED]:~# hciconfig hci0 up
> hci_sock_create: sock c0009a00
> hci_sock_ioctl: cmd 800448d3 arg 253e4
> hci_dev_get: 0
> Mainhci_sock_ioctl: cmd 400448c9 arg 0
> :1
> hci_dev_get: 0
> hci_dev_open: hci0 c07abe00
> hci_usb_open: hci0
> hci_usb_intr_rx_submit: hci0
> hci_usb_bulk_rx_submit: hci0 urb c65521b4
> hci_usb_rx_complete: hci0 urb c6552734 type 4 status 0 count 6 flags 0
> __recv_frame: hci0 type 4 data c05d84e0 count 6
> __recv_frame: new packet len 6
> hci_usb_rx_complete: hci0 urb c6552734 type 4 resubmit status 0
> __hci_request: hci0 start
> hci_init_req: hci0 0
> hci_send_cmd: hci0 ogf 0x4 ocf 0x3 plen 0
> hci_send_cmd: skb len 3
> hci_send_cmd: hci0 ogf 0x4 ocf 0x5 plen 0
> hci_cmd_task: hci0 cmd 1
> hci_send_frame: hci0 type 1 len 3
> hci_usb_send_frame: hci0 type 1 len 3
> hci_usb_tx_process: hci0
> hci_usb_send_ctrl: :1
> hci_usb_send_ctrl: hci0 skb c7385780 len 3
> __tx_submit: hci0 urb c6552134 type 1
> hci_send_cmd: skb len 3
> hci_send_cmd: hci0 ogf 0x4 ocf 0x9 plen 0
> hci_cmd_task: hci0 cmd 0
> hci_send_cmd: skb len 3
> hci_send_cmd: hci0 ogf 0x3 ocf 0x25 plen 0
> hci_cmd_task: hci0 cmd 0
> hci_send_cmd: skb len 3
> hci_send_cmd: hci0 ogf 0x3 ocf 0x5 plen 2
> hci_cmd_task: hci0 cmd 0
> hci_send_cmd: skb len 5
> hci_send_cmd: hci0 ogf 0x3 ocf 0x18 plen 2
> hci_cmd_task: hci0 cmd 0
> hci_send_cmd: skb len 5
> hci_send_cmd: hci0 ogf 0x3 ocf 0x16 plen 2
> hci_cmd_task: hci0 cmd 0
> hci_send_cmd: skb len 5
> hci_cmd_task: hci0 cmd 0
> __hci_request: hci0 end: err -110
This is presumably a timeout of some kind, but I have no idea
how the Bluetooth stack behaves or what might have triggered
it. Or even if it's associated with USB at all... maybe USB
is behaving perfctly and the problem is in the device firmware
or in the Bluetooth driver.
> hci_usb_flush: hci0
> hci_usb_close: hci0
> hci_usb_unlink_urbs: hci0
> hci_usb_unlink_urbs: hci0 unlinking _urb c6552120 type 1 urb c6552134
> hci_usb_tx_complete: hci0 urb c6552134 status -2 flags 0
> hci_usb_unlink_urbs: hci0 freeing _urb c6552120 type 1 urb c6552134
> hci_usb_unlink_urbs: hci0 unlinking _urb c65521a0 type 2 urb c65521b4
> hci_usb_rx_complete: hci0 urb c65521b4 type 2 status -2 count 0 flags 0
> hci_usb_unlink_urbs: hci0 freeing _urb c65521a0 type 2 urb c65521b4
> hci_usb_unlink_urbs: hci0 unlinking _urb c6552720 type 4 urb c6552734
> hci_usb_rx_complete: hci0 urb c6552734 type 4 status -2 count 0 flags 0
> hci_usb_unlink_urbs: hci0 freeing _urb c6552720 type 4 urb c6552734
> hci_usb_flush: hci0
> Can't init device hchci_sock_release: sock c0009a00 sk c07aa8a0
> i0: Connection timed out (110)
> [EMAIL PROTECTED]:~#
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
