From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [Bluez-devel] Connection with a phonestaysopenafterclosingRFCOMM channel From: Marcel Holtmann To: BlueZ Mailing List In-Reply-To: References: Content-Type: text/plain Message-Id: <1109807677.8284.41.camel@pegasus> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 03 Mar 2005 00:54:37 +0100 Hi Victor, > 2.6.10-mh4 - did not help so this is still a problem with the current Bluetooth subsystem. > lsmod - /proc/modules is empty, but i have no modules (everything i > need is compiled into kernel)... Too bad, because I don't know of any other way to check the module reference counting. If there is something wrong we would be sure that I have to look for that. > l2cap: > 72:FF:28:C6:10:00 42:E4:11:DE:0F:00 1 3 0x0040 0x0043 1024 251 0x0 > 00:00:00:00:00:00 00:00:00:00:00:00 4 19 0x0000 0x0000 48 48 0x0 > 00:00:00:00:00:00 00:00:00:00:00:00 4 17 0x0000 0x0000 48 48 0x0 > 00:00:00:00:00:00 00:00:00:00:00:00 4 1 0x0000 0x0000 672 0 0x0 > 00:00:00:00:00:00 00:00:00:00:00:00 4 3 0x0000 0x0000 1024 0 0x0 The L2CAP PSM 3 for RFCOMM is still connected. It's actually that what I expected. > Am I missing something? No, because we should simply close the DLCI 0 when no other RFCOMM channel is open. Regards Marcel ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel