From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: <1261177347.4041.103.camel@localhost.localdomain> References: <113d36d80909110053ybd2c203xeda76bd36248bb17@mail.gmail.com> <1252687514.8931.77.camel@violet> <113d36d80909140210n476f5826x1ae2ea621b57782c@mail.gmail.com> <35c90d960909211752u389e5d6dqbd4afe0e055c43d0@mail.gmail.com> <35c90d960909211829u71880f94j861055c61efc8c@mail.gmail.com> <35c90d960909221318m4b918d2dg3e2688a89427319a@mail.gmail.com> <508e92ca0912180620l3550bdb7w1211094681cbc87b@mail.gmail.com> <1261173555.4041.91.camel@localhost.localdomain> <35c90d960912181430t4bf36fb9gbc6ae71eeaf16602@mail.gmail.com> <1261177347.4041.103.camel@localhost.localdomain> Date: Wed, 30 Dec 2009 14:22:35 +0000 Message-ID: Subject: Re: kernel panic happens when disconnecting Bluetooth headset From: Luiz Pena To: Marcel Holtmann Cc: Nick Pelly , Andrei Emeltchenko , Lan Zhu , linux-bluetooth@vger.kernel.org Content-Type: text/plain; charset=windows-1252 List-ID: Hi all. I was wondering if you solved the problem eventually and how you did it? In addition, you mentioned that some L2CAP specific API should be added to the kernel so direct use of L2CAP sockets won=92t be necessary anymore =96 anybody working on that? Thanks ahead and happy new years eve.