From: Johannes Berg <johannes@sipsolutions.net>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] P2P setup timeout
Date: Mon, 16 Dec 2013 14:45:28 +0100 [thread overview]
Message-ID: <1387201528.2057.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CANq1E4TAt_Pw-V5_2LtJjY3LRcuwsxr1mBkcHjmX+MJUxc=zPQ@mail.gmail.com> (sfid-20131216_143914_205158_56AAC54B)
On Mon, 2013-12-16 at 14:39 +0100, David Herrmann wrote:
> > Can you check in a sniffer what the frame bitrates are that go out? This
> > seems suspicious:
> >
> > nl80211: Set TX rates failed: ret=-100 (Network is down)
>
> I looked at the sniffer data and all I see is a huge amount of p2p
> probe requests from my local device, the successful p2p-invitation and
> invitation response and then lots of go-negotiation requests that
> never get any response.
Right, and I suspect they don't get a response because (as the sniffer
trace tells me) they're sent with 1 Mbps (a CCK rate), which is invalid
in the P2P spec (must use OFDM).
Thus something is wrong with the TX bitrates stuff, but I can't tell you
where that would be ...
johannes
next prev parent reply other threads:[~2013-12-16 13:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 10:18 [BUG] P2P setup timeout David Herrmann
2013-12-09 14:03 ` Oleksij Rempel
2013-12-09 14:30 ` David Herrmann
2013-12-16 12:00 ` David Herrmann
2013-12-16 12:36 ` Johannes Berg
2013-12-16 13:39 ` David Herrmann
2013-12-16 13:45 ` Johannes Berg [this message]
2013-12-16 13:51 ` David Herrmann
2013-12-16 14:57 ` Oleksij Rempel
2013-12-16 15:09 ` David Herrmann
2013-12-16 15:15 ` Johannes Berg
2013-12-16 15:26 ` Oleksij Rempel
2013-12-16 15:29 ` Johannes Berg
2013-12-16 15:37 ` Oleksij Rempel
2013-12-16 15:53 ` David Herrmann
2013-12-17 5:50 ` Ujjal Roy
2013-12-17 7:19 ` 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=1387201528.2057.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dh.herrmann@gmail.com \
--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).