From: Simon Vincent <simon.vincent@xsilon.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: Kernel crash when using multiple interfaces
Date: Tue, 19 May 2015 12:18:24 +0100 [thread overview]
Message-ID: <555B1C00.20900@xsilon.com> (raw)
In-Reply-To: <20150518162727.GD749@omega>
Hi Alex,
I am not sure why it was crashing yesterday. I have done a clean build
today and it looks fine.
I would proceed with your patch and I will let you know if I see any
problems in the future.
- Simon
On 18/05/15 17:27, Alexander Aring wrote:
> On Mon, May 18, 2015 at 05:37:12PM +0200, Alexander Aring wrote:
>> Hi,
>>
>> On Mon, May 18, 2015 at 04:05:38PM +0100, Simon Vincent wrote:
>>> With your patch I get either a "bad paging request" or a NULL pointer
>>> dereference crash at startup. I have not had any problems with my patch.
>>>
>>> Here are two stack traces I get.
>>>
>>> [ 12.223057] [<c04da1b8>] (ieee802154_stop_queue) from [<c04d6d64>]
>>>
>>> or
>>>
>>> [ 12.548824] [<c04da1b8>] (ieee802154_stop_queue) from [<c04d6d64>]
>> Both crashes in ieee802154_stop_queue, but we don't changed anything
>> which should affect the ieee802154_stop_queue in my or your fix.
>>
> Ah, it could be that it failed in ieee802154_tx after calling
> ieee802154_stop_queue. Are you sure that you don't miss some & for
> handling with pointers and then we have some invalid address?
>
> - Alex
next prev parent reply other threads:[~2015-05-19 11:18 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
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 [this message]
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=555B1C00.20900@xsilon.com \
--to=simon.vincent@xsilon.com \
--cc=alex.aring@gmail.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