From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC v4] cfg80211: Android P2P-Device workaround
Date: Thu, 2 May 2013 21:17:40 +0200 [thread overview]
Message-ID: <5182BBD4.9010701@broadcom.com> (raw)
In-Reply-To: <1367489163.8298.2.camel@jlt4.sipsolutions.net>
On 05/02/2013 12:06 PM, Johannes Berg wrote:
> On Thu, 2013-05-02 at 12:03 +0200, Arend van Spriel wrote:
>
>> I tested the patch on x86 platform and was successful executing a
>> p2p_find, p2p_connect, and able to ping my peer. But....
>>
>> When I tried this a second time I got a lockdep warning about annotation
>> as brcmfmac tried to take a mutex during scan (p2p_find). Two minutes
>> later I got warning about rcu stalls. Not sure where to look.
>
> Me neither? :) What does it say?
crap. One time I get the lockdep warning/rcu stall and the next a null
pointer access, but the stack trace is the same. Afraid this is a
brcmfmac issue that I will have to look into it.
Gr. AvS
next prev parent reply other threads:[~2013-05-02 19:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 12:26 [RFC v4] cfg80211: Android P2P-Device workaround Johannes Berg
2013-04-29 13:50 ` Arend van Spriel
2013-04-29 13:53 ` Johannes Berg
2013-04-29 16:32 ` Marcel Holtmann
2013-04-30 13:38 ` Sreenath
2013-04-30 13:43 ` Johannes Berg
2013-05-02 10:03 ` Arend van Spriel
2013-05-02 10:06 ` Johannes Berg
2013-05-02 19:17 ` Arend van Spriel [this message]
2013-05-07 10:20 ` Johannes Berg
2013-05-23 3:18 ` YanBo
2013-05-23 9:40 ` Johannes Berg
2013-05-23 14:40 ` YanBo
2013-05-23 16:08 ` Johannes Berg
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=5182BBD4.9010701@broadcom.com \
--to=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).