Investigate rfcomm inconsistency.
How to reproduce:
- machine A: rfcomm listen /dev/rfcomm0 1
- machine B: rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1
- machine A: rfcomm release /dev/rfcomm0
machine A kernel: 2.6.24-16-386 #1 Thu Apr 10 12:50:06 UTC 2008 i686 GNU/Linux
machine B kernel: 2.6.25-rc1 #1 SMP Tue Feb 12 18:02:51 BRT 2008 x86_64 GNU/Linux
After execute the steps above, the rfcomm module becomes inconsistent:
1) machine A: "$rfcomm listen /dev/rfcomm0 1
Waiting for connection on channel 1
Can't create RFCOMM TTY: File exists"
2) machine A: "$rfcomm listen /dev/rfcomm2 1
Waiting for connection on channel 1"
from machine B: rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1
=> machine A never accepts/receives the connection