https://bugzilla.kernel.org/show_bug.cgi?id=80301 Bug ID: 80301 Summary: RFCOMM never disconnects Product: Drivers Version: 2.5 Kernel Version: 3.15.5 Hardware: i386 OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Bluetooth Assignee: linux-bluetooth@xxxxxxxxxxxxxxx Reporter: kcilorak@xxxxxxxxx Regression: No This is kind of a strange one. When you create an RFCOMM connection with either rfcomm bind rfcomm* 00:00:00:00:00:00 or rfcomm connect rfcomm* 00:00:00:00:00:00 The device works and the bluetooth hardware functions as expected, but when you shut off the remote Bluetooth device or it gets out of range the RFCOMM connection never closes. You can still open it with minicom or any other application. There is nothing on the other end to talk to but you can open it. In all previous kernels when the device shuts off or gets out of range the port closes. With connect the port gets removed and with bind the connection closes but the RFCOMM port still exists but you cannot access it. With this bug when using bind the port just starts working again when the device becomes visible, so it seems like it never hangs up. Using connect the RFCOMM connection eventually times out and the connect closes but the RFCOMM doesn't leaving it corrupt and impossible to remove without a reboot. -- You are receiving this mail because: You are the assignee for the bug. -- 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
