Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Simon Vincent <simon.vincent@xsilon.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: Kernel crash when using multiple interfaces
Date: Mon, 18 May 2015 16:00:47 +0200	[thread overview]
Message-ID: <20150518140045.GA749@omega> (raw)
In-Reply-To: <5559C58F.6010607@xsilon.com>

Hi Simon,

On Mon, May 18, 2015 at 11:57:19AM +0100, Simon Vincent wrote:
> Hi Alex,
> 
> I can confirm your patch still results in the bad paging request.
> Maybe you are not seeing it as you have a slightly different setup.
> 
> If I understand correctly you have two virtual phys going to a single wpan
> interface
> e.g.
> phy0 -> wpan0
> phy1 -> wpan0
> 
> My setup is two separate transceivers. Each with its own phy and wpan
> interface.
> e.g.
> phy0 -> wpan0
> phy1 -> wpan1
> 

 From view of mac802154 layer this setup should be the same. Both running
two times alloc_hw and register_hw for alloc/register a wpan phy. The
driver layer is different.

With your solution to putting the worker resource on the heap then the
problem is solved?

Can you provide more information about the "bad paging request" issue? A
stacktrace or something else?

I currently have no idea why you have this issue.

- Alex

  reply	other threads:[~2015-05-18 14:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 12:54 Kernel crash when using multiple interfaces Simon Vincent
2015-05-15 14:20 ` Alexander Aring
2015-05-15 15:02   ` Simon Vincent
2015-05-15 15:23     ` Alexander Aring
2015-05-16 15:33     ` Alexander Aring
2015-05-18 10:57       ` Simon Vincent
2015-05-18 14:00         ` Alexander Aring [this message]
2015-05-18 15:05           ` Simon Vincent
2015-05-18 15:37             ` Alexander Aring
2015-05-18 16:27               ` Alexander Aring
2015-05-19 11:18                 ` Simon Vincent
2015-05-15 15:28 ` Alexander Aring

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=20150518140045.GA749@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=simon.vincent@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox