Return-Path: Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) Subject: Re: l2cap sockets not properly multiplexed on ARM From: Marcel Holtmann In-Reply-To: Date: Thu, 31 Oct 2013 15:20:18 +0100 Cc: Alexander Holler , "linux-bluetooth@vger.kernel.org" Message-Id: References: <5270EC62.6070705@ahsoftware.de>,<5270F19A.4030408@ahsoftware.de> ,<527114A4.5010207@ahsoftware.de> <4A213FF7-48BA-4906-8868-7C3A227EF954@holtmann.org>,<527190DA.6000805@ahsoftware.de> To: Tim Tisdall Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Tim, >> As Anderson Lizardo already mentioned, maybe first verify that the x86 >> kernel 3.4 doesn't have the same problem and that it's really a problem >> of the ARM kernel. Up to now he didn't say what kernel version he uses >> on x86. > > here's my desktop version: > $ uname -a > Linux tzing 3.8.0-32-generic #47-Ubuntu SMP Tue Oct 1 22:35:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux > > I'm trying to get an older version of the kernel running on another machine and then I'll report back I actually need to know if bluetooth-next tree still has this issue. That is first and foremost the one thing that needs to be checked. Regards Marcel