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

RE: [bluetooth-dev] BT apps: What about client code?



> -----Original Message-----
> From: Mattias Ĺgren [mailto:mattias.agren@xxxxxxx.com]
> Sent: Tuesday, June 26, 2001 4:26 PM
> To: 'Hervé Suaudeau'; bluetooth-dev@xxxxxxx.com
> Subject: RE: [bluetooth-dev] BT apps: What about client code?
> > Running apps/bluetooth/experimental/btdm as a server is quite 
> > functional
> > (exept crashes while closing the connection), but what about 
> > the client
> 
> Could you provide some logs and a description of what happens ?

Mattias,

Sorry about delay for this answer but I had difficulties generating a good  
error report.
You can find (at the end) the oops report generated by the crash.

Description of the operations:
The operation that was done are in 7 steps:
 1 - Starting btdm on local (btdm -u /dev/ttyS1 -s 57600 -m1)
 2 - A service discovery request by the remote conputer
 3 - A connection on Serial port profile (remote request)
 4 - A PPP connection from the remote station (in Windows)
     (On local there is in options.ttyBT0:  noauth, local, debug,
                            record pppd.log, lock, mtu 296, dump)
	-- THE PPP CONNECTION IS FULLY FONCTIONNAL  --
 5 - A close of the PPP connection (remote request)
 6 - A close of the Serial port profile (remote request)
 7 - A reconnection of Serial port profile (remote request)
Sometimes the crash occurs before... (after the first close)


I generated a 9000 lines syslog report (with all debug options enabled) and 
there are some errors in:
Step 2 :
11:48:18 kernel:  BT SYS: ERROR :process_return_param: 
WRITE_LINK_POLICY_SETTINGS: Unknown HCI Command
----> Normal, because I use the EBDK
11:48:18 kernel:  BT SYS: ERROR :process_return_param: 
WRITE_LINK_POLICY_SETTINGS: Unknown HCI Command
----> Normal, because I use the EBDK
Step 4 :
11:49:05 kernel: BT SYS: ERROR :hci_receive_data: 3104 is too big for our HCI 
input buffers -- discarding
buffer
11:49:05 kernel: BT SYS: ERROR :hci_receive_data: discarding 56 bytes
11:49:05 kernel: BT SYS: ERROR :hci_receive_data: discarding 16 bytes
11:49:14 kernel: BT SYS: ERROR :hci_receive_data: discarding 47 bytes
11:49:14 kernel: BT SYS: ERROR :hci_receive_data: discarding 56 bytes
11:49:14 kernel: BT SYS: ERROR :hci_receive_data: discarding 11 bytes
11:49:15 kernel: BT SYS: ERROR :hci_receive_data: discarding 43 bytes
11:49:15 kernel: BT SYS: ERROR :hci_receive_data: discarding 56 bytes
11:49:15 kernel: BT SYS: ERROR :hci_receive_data: discarding 56 bytes
11:49:15 kernel: BT SYS: ERROR :hci_receive_data: discarding 56 bytes
11:49:15 kernel: BT SYS: ERROR :hci_receive_data: discarding 57 bytes
11:49:15 kernel: BT SYS: ERROR :hci_receive_data: discarding 64 bytes
11:49:15 kernel: BT SYS: ERROR :hci_receive_data: discarding 27 bytes
11:49:17 kernel: BT SYS: ERROR :l2cap_receive_data: packet too big [2922], 
discard packet
11:49:20 kernel: BT SYS: ERROR :hci_receive_data: discarding 16 bytes
Step 5:
11:49:37 kernel: BT SYS: ERROR :hci_receive_data: discarding 22 bytes
11:49:37 kernel: BT SYS: ERROR :hci_receive_data: discarding 24 bytes
Step 7:
11:51:22 kernel:  BT SYS: ERROR :process_return_param: 
WRITE_LINK_POLICY_SETTINGS: Unknown HCI Command
----> Normal, because I use the EBDK


I have statically compiled the driver with my 2.4.2 kernel in order to get a 
good call trace.
I have set the following options:
    <*> Bluetooth driver
    (Ericsson)    Bluetooth harware type
    [ ]   Block when setting baudrate    
    [ ]   Bluetooth proc entries         
    [*]   Input buffering                
    [ ]   Use Security Manager           
    [ ]   Use L2CAP timers               
    [ ]   Allow connectionless L2CAP     
    [ ]   Enable TCI                     
    [ ]   Enable M/S Switch              
    (None)   Bluetooth reset pin         

Thanks for all.
Regards.

Herve SUAUDEAU

-----------------------Oops report------------------------------------
Oops: 0000
CPU:    0
EIP:    0010:[<45505954>]
EFLAGS: 00010202 
eax: 45505954	 ebx: c6580000   ecx: c0354e38=(bt_ctrl +18/1c0) edx: 00000000
esi: 00000000	 edi: 00000000	 ebp: c0369853=(hci_data+93/fc0) esp: c02f1ed0 
(init_task_union + 1ed0/2000)
ds: 0018   es: 0018	   ss: 0018
Process swapper (pid: 0, stackpage=c02f1000=(init_task_union + 1000/2000) )
Stack:	c01b110b   bt_feedstack + ab/d4
 	   	c6580000   ?	
 	   	00000004   DATA
 	   	c0369854   hci_data   		+ 94/fc0
 	   	c01b3464   update_ncp 		+ dc/e0
 	   	00000013   DATA
 	   	00000005   DATA
 	   	c01b3a84   process_event 	+ 6e0/61c
       	00000001   DATA
       	c0369854   hci_data   		+ 94/fc0
       	c0295de0   NR_TYPES	  		+ ...
       	c02f1f74   init_task_union	+ .../2000
       	c0369850   hci_data   		+ 90/fc0
       	00000000   DATA	   			+ ...
       	c0369853   hci_data   		+ 93/fc0
       	c0113510   printk  			+ ...
	   	c02f1f74   init_task_union 	+ .../2000
	   	c0369850   hci_data   		+ 90/fc0
	   	00000000   DATA
	   	c0369852   hci_data   		+ 92/fc0
	   	00000282   DATA
	   	00000001   DATA
	   	c01b2f0a   hci_receive_data + ...
	   	c0369853   hci_data   		+ 93/fc0
Call Trace: [<c01b110b> : bt_feedstack 		+ ab/d4		] 
		[<c01b3464> : update_ncp		+ dc/e0		] 
		[<c01b3a84> : process_event 		+ 6e0/61c	] 
		[<c0113510> : printk			+ 154/160	] 
		[<c01b2f0a> : hci_receive_data	+ 402/53c	]
            [<c01b132b> : bt_receive_data   	+ 5/14		] 
            [<c01b1316> : hci_receive_data_task	+ 5a/60		] 
            [<c0116e34> :  __run_task_queue 	+ 4c/68		] 
            [<c0119152> : immediate_bh		+ 16/1c		] 
            [<c0116d5f> : bh_action			+ 1b/60		] 
            [<c0116c98> : tasklet_hi_action 	+ 3c/60		] 
            [<c0116b9f> : do_softirq		+ 3f/64		]
            [<c01071f0> : default_idle		+ 0/28 		] 
            [<c01111f5> : schedule			+ 319/394	] 
            [<c01071f0> : default_idle		+ 0/28 		] 
            [<c01071f0> : default_idle		+ 0/28 		] 
            [<c0100018> : startup_32		+ 18/139	] 
            [<c0107285> : cpu_idle			+ 4d/54		] 
            [<c0105000> : empty_bad_page		+ 0/1000 	] 
            [<c0100191> : L6				+ 0/2		] 

Code: Bad IPD value
Kernel panic: Aiee, killing interrupt handler! 
In interupt handler - not syncing

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