Hi Marcel,
Thanks for the feedback.
I'll try to reproduce on latest build and send the required info.
Regards,
Kiran
On Friday, 6 June 2014, Marcel Holtmann <[email protected]> wrote:
> Hi Kiran,
>
> Below are the traces used by author for submitting patch previously.
>
> [ 132.856414] rfcomm:rfcomm_sock_shutdown: sock c5cb3a20, sk c63fca00
> [ 132.856933] rfcomm:__rfcomm_sock_close: sk c63fca00 state 5 socket
c5cb3a20
> [ 132.857788] rfcomm:__rfcomm_dlc_close: dlc c61ea240 state 7 dlci 38
> err 0 session c63d4ba0
> [ 132.858612] rfcomm:rfcomm_send_disc: c63d4ba0 dlci 38
> [ 132.859069] rfcomm:rfcomm_send_frame: session c63d4ba0 len 4
> [ 132.859893] l2cap:l2cap_sock_sendmsg: sock c5cb38c0, sk c63fc800
> [ 132.860351] rfcomm:rfcomm_dlc_set_timer: dlc c61ea240 state 8 timeout
2000
> [ 133.863739] rfcomm:rfcomm_sock_release: sock c5cb3a20, sk c63fca00
> [ 133.864257] rfcomm:rfcomm_sock_shutdown: sock c5cb3a20, sk c63fca00
> [ 133.865081] rfcomm:rfcomm_sock_kill: sk c63fca00 state 5 refcnt 2
> [ 133.865539] rfcomm:rfcomm_sock_destruct: sk c63fca00 dlc c61ea240
>
> they need to be run against a recent bluetooth-next tree. And we also
need HCI traces to show the problem.
> Regards
> Marcel
>