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

Re: [bluetooth-dev] my branch



here is another log. i enabled pretty much everything there is.... seems
like the hci.c is the problem...




Mar 21 20:38:43 tec-pc-jg kernel: BT (driver) bt_ioctl: HCINQUIRY
Mar 21 20:38:43 tec-pc-jg kernel: HCI: hci_inquiry
Mar 21 20:38:43 tec-pc-jg kernel: 
Mar 21 20:38:43 tec-pc-jg kernel: hci_inquiry (9)
Mar 21 20:38:43 tec-pc-jg kernel:    0x01 0x01 0x04 0x05 0x9e 0x8b 0x33
0x64 0x0a 
Mar 21 20:38:43 tec-pc-jg kernel: HCI: insert_cmd
Mar 21 20:38:43 tec-pc-jg kernel: HCI: start_cmd_timer
Mar 21 20:38:43 tec-pc-jg kernel: HCI: send_cmd_queue, start:
Num_HCI_Command_Packets=1
Mar 21 20:38:43 tec-pc-jg kernel: 
Mar 21 20:38:43 tec-pc-jg kernel: send_cmd_queue,  (4)
Mar 21 20:38:43 tec-pc-jg kernel:    0x01 0x09 0x10 0x00 
Mar 21 20:38:43 tec-pc-jg kernel: BT DATA <--|X|      4
Mar 21 20:38:43 tec-pc-jg kernel: 
Mar 21 20:38:43 tec-pc-jg kernel: bt_write_lower_driver : (4)
Mar 21 20:38:43 tec-pc-jg kernel:    0x01 0x09 0x10 0x00 
Mar 21 20:38:43 tec-pc-jg kernel: HCI: send_cmd_queue, sent data...,
freeing memory
Mar 21 20:38:43 tec-pc-jg kernel: HCI: send_cmd_queue, end : 1 cmds left
in queue
Mar 21 20:38:46 tec-pc-jg kernel: cmd_timeout, Timeout when waiting for
command response
Mar 21 20:38:46 tec-pc-jg btd: Killing SDP server 
Mar 21 20:38:46 tec-pc-jg btd: Shutting down bluetooth stack 
Mar 21 20:38:46 tec-pc-jg kernel: BT SYS: Shutting down bluetooth stack
Mar 21 20:38:46 tec-pc-jg kernel: BT SYS: Shutting down RFCOMM
Mar 21 20:38:46 tec-pc-jg kernel: BT SYS: Shutting down SDP
Mar 21 20:38:46 tec-pc-jg kernel: BT SYS: Shutting down TCS
Mar 21 20:38:46 tec-pc-jg kernel: BT SYS: Shutting down L2CAP
Mar 21 20:38:46 tec-pc-jg kernel: BT SYS: Shutting down BTMEM
Mar 21 20:38:46 tec-pc-jg btd: close_device
Mar 21 20:38:46 tec-pc-jg kernel: BT (driver) bt_close on line 7
Mar 21 20:38:46 tec-pc-jg kernel: BT SYS: Unregistering tty on line 7
Mar 21 20:38:46 tec-pc-jg kernel: BT (ldisc) bt_tty_ioctl cmd 0x540b
Mar 21 20:38:46 tec-pc-jg kernel: BT (ldisc) bt_tty_ioctl: forwarding
ioctl 0x540b to n_tty line disc
Mar 21 20:38:46 tec-pc-jg btd: close_device




/***************** Bluetooth Debug defines
***********************************/

#define BT_DATA_DEBUG 1
#define BT_DATAFLOW_DEBUG 1 /* print pkt */

#define BT_DRIVER_DEBUG 1

#define BT_LDISC_DEBUG 1

#define BT_DBG_STR "BT " 

/****************** HCI Debug defines
****************************************/
/* Possibility to turn on/off debug for separate sections, in the hci
layer */

#define DEBUG_HCI_QUEUEING 1
/* Debug for the queueing when sending data */

#define DEBUG_HCI_INDATA 1
/* Prints out how many characters that is received by hci_recieve_data()
*/

#define DEBUG_HCI_STATE 1
/* Will enable/disable debug for the receive states (WAIT_FOR_xxx) */

#define DEBUG_HCI_RECEIVING_PROCESS 1
/* Will enable/disable debug during the receiving process */

#define DEBUG_HCI_SEND_PROCESS 1
/* Will enable/disable debug during the sending process (only data, no
cmds) */

#define DEBUG_DATAFLOW 1
/* Enables / disables the printing of the bytes thar are sent/received
*/

#define DEBUG_HCI_CTRL 1
/* Enables / disables debug for the HCI control and signaling */

#define DEBUG_HCI_CMD 1
/* Enables / disables debug for the HCI commands */




Gordon McNutt wrote:
> 
> Jan Beutel wrote:
> 
> > i am running kernel 2.2.18 on redhat.
> >
> > my bt hw is ericsson p3d with p9a firmware.
> >
> > and yes, i get a time out waiting. see below:
> >
> > [root@pc-3581 bin]# btd -r client
> > Bluetooth Control Application
> > -----------------------------
> > Running as client
> > Physdev /dev/ttyS0, btdev /dev/ttyBT0, speed 115200 baud
> > Registered bluetooth line discipline on /dev/ttyS0
> > Init stack
> > Setting write_scan_enable in Ericsson module!
> > Setting event filter in Ericsson module!
> > Setting baudrate in Ericsson module!
> > Now entering cmd line mode
> >
> > Menu
> > ------------------------
> >   inq <Max number of responses> (inquiry scan)
> >   rf_conn <xx:xx:xx:xx:xx:xx> <srv ch> <line>
> >   rf_send <nbr bytes> <nbr repeats> <line>
> >   rf_disc <line>
> >   rf_wait <line>
> >   me <1/0>
> >   setbd <xx:xx:xx:xx:xx:xx>
> >   readbd
> >   reset
> >   role_switch <xx:xx:xx:xx:xx:xx> <role> (0=master, 1=slave)
> >   ppp
> >   quit
> > > inq 10 10
> > Inquiry: Resource temporarily unavailable
> > [root@pc-3581 bin]#
> >
> > Mar 21 17:00:09 pc-3581 kernel: BT SYS: Now 2 open fd:s for ttyBTC
> > Mar 21 17:00:09 pc-3581 kernel: BT (driver) bt_ioctl: forwarding ioctl
> > 0x540b to serial driver
> > Mar 21 17:00:09 pc-3581 kernel: BT (driver) bt_flush_buffer
> > Mar 21 17:00:09 pc-3581 kernel: BT (driver) bt_ioctl: HCINQUIRY
> > Mar 21 17:00:12 pc-3581 kernel: cmd_timeout, Timeout when waiting for
> > command response
> > Mar 21 17:00:12 pc-3581 btd: Shutting down bluetooth stack
> >
> > then it's gone...
> 
> Ok, that's good info.
> 
> First the easy one. btd shouldn't bail just because the inquiry ioctl failed.
> I'll check that in as soon as sourceforge let's me connect again.
> 
> Now, the timeout is the command timeout, not the HCI inquiry timeout. This
> implies that the Host Controller didn't kick back a Command Status event, or we
> got one but didn't do the right thing. Can you turn on BT_DATAFLOW_DEBUG and post
> me the log?
> 
> Thanks,
> --gmcnutt
> 
> -
> To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
> the body of a message to majordomo@xxxxxxx.com

-- 
Jan Beutel                                 j.beutel@xxxxxxx.org
Computer Engineering and Networks Laboratory, ETZ G63
ETH Zurich                              +41 1 632 70 32 Phone
Gloriastrasse 35                          +41 1 632 10 35 Fax
CH 8092 Zurich/Switzerland  http://www.tik.ee.ethz.ch/~beutel
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com