Return-Path: From: Szymon Janc To: Andrea Cc: linux-bluetooth@vger.kernel.org Subject: Re: partial success with PS3 sixaxis Date: Fri, 28 Feb 2014 11:35:29 +0100 Message-ID: <1521205.0Q940hgGyU@uw000953> In-Reply-To: <53086B93.3080503@gmail.com> References: <52FBE820.6050701@gmail.com> <1484977.kC8PK9znGI@uw000953> <53086B93.3080503@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Andrea, On Saturday 22 of February 2014 09:19:15 Andrea wrote: > On 20/02/14 09:47, Szymon Janc wrote: > > Hi Andrea, > > > > > > This is a known regression on kernels >3.9. Should be fixed in 3.15 AFAIR. > > > > you really mean 3.15? not even 3.14? AFAIK yes, this regression was only spotted in mid December when sixaxis patches were submitted and proper fix turns out to be not that trivial. > then, my last issue is the following: > > on Fedora 19 x86 things work with a Bluetooth 4.0 dongle > > 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) > > running 3.12.11 (Fedora version) > > > > unfortunately on a Raspberry Pi ARM6, Arch Linux with kernel 3.13.3 I get a strange kernel oops > after a random time of successful usage (could be 1 minute or 2 days) > > I struggle to get a meaningful stack trace (the whole system dies, need to attach a serial console), > would you know of any issues on this architecture? it seems to be a NULL pointer exception. > The same crash happens with a different dongle (older bluetooth 2 from broadcom) I haven't seen any issues on my PC but I wasn't using it on any ARM device. -- Best regards, Szymon Janc