All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Martin Townsend <martin.townsend@xsilon.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: Oops with latest bluetooth-next kernel.
Date: Thu, 7 May 2015 19:00:53 +0200	[thread overview]
Message-ID: <20150507170052.GA714@omega> (raw)
In-Reply-To: <554B8456.9090107@xsilon.com>

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

  reply	other threads:[~2015-05-07 17:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 10:41 Oops with latest bluetooth-next kernel Martin Townsend
2015-05-07 12:24 ` Alexander Aring
2015-05-07 15:27   ` Martin Townsend
2015-05-07 17:00     ` Alexander Aring [this message]
2015-05-07 17:10       ` Alexander Aring
2015-05-07 17:21         ` Alexander Aring
2015-05-07 18:26       ` Martin Townsend

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150507170052.GA714@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=martin.townsend@xsilon.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.