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

Re: [bluetooth-dev] Connection hangs



OK. Here's a debug trace of my problem (well bluetooth's problem anyway).
Near the bottom there is an unrecognized parameter. Is it indicative of
using an ericsson board with the wrong software?

Any help would help!		

Oct  6 11:50:05 M-Mouse kernel: CONNECTION_COMPLETE  (11)
Oct  6 11:50:05
M-Mouse kernel:    0x00 0x01 0x00 0x45 0x00 0x31 0x03 0x02 0x01 0x01 0x00

Oct  6 11:50:05 M-Mouse kernel: HCI: hci_send_data: 12 bytes 
Oct  6
11:50:05 M-Mouse kernel: HCI: hci_send_data: send one packet immediately

Oct  6 11:50:05 M-Mouse kernel: HCI: send_acl_packet: send 12 bytes (excl
HCI header) out of 12
Oct  6 11:50:05 M-Mouse kernel: HCI: send_acl_packet:
There are 5 bytes space for the headers
Oct  6 11:50:05 M-Mouse kernel: BT
DRVbt_write_lower_driver:  17 chars 
Oct  6 11:50:05 M-Mouse kernel: BT
DRVbt_write_lower_driver: write_wakeup ldisc (N_TTY)
Oct  6 11:50:05
M-Mouse kernel: HCI: send_acl_packet: unsubscribing tx_buf.
Oct  6 11:50:05
M-Mouse kernel: HCI: change_connection_packet_type: for connnection handle
0x1
Oct  6 11:50:05 M-Mouse kernel: HCI: send_cmd : cmd_num 1
Oct  6
11:50:05 M-Mouse kernel: HCI: send_cmd_queue: start (cmd_num:1)
Oct  6
11:50:05 M-Mouse kernel: HCI: send_cmd_queue : 0 cmds left in queue
Oct  6
11:50:05 M-Mouse kernel: BT DRVbt_write_lower_driver:  8 chars 
Oct  6
11:50:05 M-Mouse kernel: BT DRVbt_write_lower_driver: write_wakeup ldisc
(N_TTY)
Oct  6 11:50:05 M-Mouse kernel: HCI: send_cmd: Sucessfully sent HCI
command
Oct  6 11:50:05 M-Mouse kernel: BT DRVbt_receive_lower_stack 7
bytes
Oct  6 11:50:05 M-Mouse kernel: HCI: hci_receive_data:
WAIT_FOR_PACKET_TYPE
Oct  6 11:50:05 M-Mouse kernel: HCI: hci_receive_data:
WAIT_FOR_EVENT_TYPE
Oct  6 11:50:05 M-Mouse kernel: HCI: hci_receive_data:
WAIT_FOR_EVENT_LENGTH
Oct  6 11:50:05 M-Mouse kernel: HCI: process_event:
COMMAND_STATUS (status:0x0)
Oct  6 11:50:05 M-Mouse kernel: HCI: now
cmd_num = 0
Oct  6 11:50:05 M-Mouse kernel:  HCI: send_cmd_queue: start
(cmd_num:0)
Oct  6 11:50:05 M-Mouse kernel: HCI: send_cmd_queue : 0 cmds
left in queue
Oct  6 11:50:05 M-Mouse kernel: BT DRVbt_receive_lower_stack
15 bytes
Oct  6 11:50:05 M-Mouse kernel: HCI: hci_receive_data:
WAIT_FOR_PACKET_TYPE
Oct  6 11:50:05 M-Mouse kernel: HCI: hci_receive_data:
WAIT_FOR_EVENT_TYPE
Oct  6 11:50:05 M-Mouse kernel: HCI: hci_receive_data:
WAIT_FOR_EVENT_LENGTH
Oct  6 11:50:05 M-Mouse kernel: HCI: process_event:
CHANGE_CONNECTION_PACKET_TYPE
Oct  6 11:50:05 M-Mouse kernel: HCI:
hci_receive_data: WAIT_FOR_PACKET_TYPE
Oct  6 11:50:05 M-Mouse kernel: HCI:
hci_receive_data: WAIT_FOR_EVENT_TYPE
Oct  6 11:50:05 M-Mouse kernel: HCI:
hci_receive_data: WAIT_FOR_EVENT_LENGTH
Oct  6 11:50:05 M-Mouse kernel:
HCI: process_event: COMMAND_COMPLETE
Oct  6 11:50:05 M-Mouse kernel:  HCI:
process_event: now cmd_num = 1
Oct  6 11:50:05 M-Mouse kernel:  HCI:
process_return_param: Not recognised! 
Oct  6 11:50:05 M-Mouse kernel: HCI:
send_cmd_queue: start (cmd_num:1)
Oct  6 11:50:05 M-Mouse kernel: HCI:
send_cmd_queue : 0 cmds left in queue



>Hello everyone,
>
>I have just downloaded the bluetooth module and compiled it under SuSE6.2
>Kernel 2.2.17. I issue the command ./btd -u ttyS1 -s 57600 -r client to an
>ericsson board and shortly afterwards the menu appears. I have another
>board connected to a Windows98 machine and some propriety control software.
>Issuing the con ??:??:??:??:??:?? 0 command connects the ericsson board to
>the other board and the Windows software reports an active connection.
>However the Linux program appears to halt and the command cursor '>' does
>not reappear. My only option is to CTRL-C in Linux and disconnect the
>bluetooth connection at the windows end.
>
>Has anyone else experienced this symptom? Is there a fix?
>
>Thankyou
>David
>
>
>