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 -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
