From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f175.google.com ([209.85.212.175]:38362 "EHLO mail-wi0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751852AbbEGRBA (ORCPT ); Thu, 7 May 2015 13:01:00 -0400 Received: by wiun10 with SMTP id n10so67440309wiu.1 for ; Thu, 07 May 2015 10:00:59 -0700 (PDT) Date: Thu, 7 May 2015 19:00:53 +0200 From: Alexander Aring Subject: Re: Oops with latest bluetooth-next kernel. Message-ID: <20150507170052.GA714@omega> References: <554B414B.50408@xsilon.com> <20150507122441.GA17485@omega> <554B8456.9090107@xsilon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <554B8456.9090107@xsilon.com> Sender: linux-wpan-owner@vger.kernel.org List-ID: To: Martin Townsend Cc: linux-wpan@vger.kernel.org Hi, On Thu, May 07, 2015 at 04:27:18PM +0100, Martin Townsend wrote: > Thanks for your reply Alex, after a bit of debugging I've tracked it down to our RPL application. If I disable this at startup there are no lock ups. As soon as I start the daemon it brings the Kernel down so I need to investigate why this happens. > > I'll have a go at updating the fakelb as it's useful for RPL and MPL. > ok. I also note on your outputs that the MIB defaults different what we have currently. Interface wpan2 ifindex 12 wpan_dev 0x200000002 extended_addr 0x1013749720940844 short_addr 0xffff pan_id 0xffff type node max_frame_retries 4 hehe, our mib default is -1 (no aret/csma-ca). min_be 4 also here. max_be 9 here as well. max_csma_backoffs 8 we have 4 here. lbt 0 Did you change that inside the kernel, so you have some patches on top of bluetooth-next? - Alex