Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Anoop Kant <Anoop.Kant@LNTTECHSERVICES.COM>
Cc: "linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: Re: Linux-Bluetoothnext: Ping6 execution for virtual Phy : System freezes
Date: Mon, 12 Oct 2015 23:00:49 +0200	[thread overview]
Message-ID: <20151012210044.GA2962@omega> (raw)
In-Reply-To: <51C7DE700DAED543997957503C74C84501077E08@POCITMSEXMB05.LntUniverse.com>

On Mon, Oct 12, 2015 at 10:47:32AM +0000, Anoop Kant wrote:
> Thanks Alex.
> With stable version, I did not face any issue in configuration of 6lowpan interfaces for fake devices when used linux-stable .
>  Ping6 also worked fine between virtual devices.
> 
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/
> 

Okay, then I think there is some issue with belongs to your architecture
(x86?) which is currently in bluetooth-next (or update again
bluetooth-next and test it again, there was some rebases to net-next
the last days).

Or you checkout some earlier commit inside bluetooth-next and look if you
have issues, if it seems to work -> then run git bisect [0].

Running git bisect would be great to report some commit which breaks
something.
I suppose it's architecture related because I don't have this issue on
my setup.

Maybe it's fine for you that you use the stable-tree for your virtual
phy testing, but for the greatest features and sending patch you will
need run/test/base patches on bluetooth-next.

- Alex

[0] http://webchick.net/node/99

      reply	other threads:[~2015-10-12 21:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 10:15 Linux-Bluetoothnext: Ping6 execution for virtual Phy : System freezes Anoop Kant
2015-10-01 10:28 ` Alexander Aring
     [not found]   ` <51C7DE700DAED543997957503C74C84501074D8A@POCITMSEXMB05.LntUniverse.com>
     [not found]     ` <20151001120802.GA25840@omega>
     [not found]       ` <51C7DE700DAED543997957503C74C84501074DF2@POCITMSEXMB05.LntUniverse.com>
     [not found]         ` <20151001124628.GA28241@omega>
     [not found]           ` <51C7DE700DAED543997957503C74C84501074E42@POCITMSEXMB05.LntUniverse.com>
2015-10-01 14:25             ` Alexander Aring
     [not found]               ` <51C7DE700DAED543997957503C74C84501074FF8@POCITMSEXMB05.LntUniverse.com>
2015-10-02  7:24                 ` Alexander Aring
2015-10-12 10:47                   ` Anoop Kant
2015-10-12 21:00                     ` Alexander Aring [this message]

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=20151012210044.GA2962@omega \
    --to=alex.aring@gmail.com \
    --cc=Anoop.Kant@LNTTECHSERVICES.COM \
    --cc=linux-wpan@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox