Return-Path: MIME-Version: 1.0 Date: Tue, 11 Mar 2014 14:44:46 -0700 Message-ID: Subject: rctest -c "Can't connect: Device or resource busy (16)" From: Scott James Remnant To: "linux-bluetooth@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Is this expected behavior for RFCOMM? When using rctest -r on one side, and rctest -c (connect/disconnect/connect...) on the other, the client side fails to connect a significant percentage of the time: rctest[23705]: Can't connect: Device or resource busy (16) rctest[23705]: Can't connect: Device or resource busy (16) rctest[23705]: Can't connect: Device or resource busy (16) rctest[23705]: Can't connect: Device or resource busy (16) rctest[23705]: Can't connect: Device or resource busy (16) rctest[23705]: Can't connect: Device or resource busy (16) rctest[23705]: Connected [handle 34817, class 0xff8801, priority 0] rctest[23705]: Can't connect: Device or resource busy (16) rctest[23705]: Can't connect: Device or resource busy (16) rctest[23705]: Can't connect: Device or resource busy (16) rctest[23705]: Can't connect: Device or resource busy (16) rctest[23705]: Can't connect: Device or resource busy (16) rctest[23705]: Can't connect: Device or resource busy (16) Scott