From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [BUG] P2P setup timeout
Date: Mon, 16 Dec 2013 15:57:48 +0100 [thread overview]
Message-ID: <52AF14EC.9010803@rempel-privat.de> (raw)
In-Reply-To: <CANq1E4TJWCgM4yCFC25b3ssQEvFv+hEhW6jP3_mQKxQCw-QtUQ@mail.gmail.com>
Am 16.12.2013 14:51, schrieb David Herrmann:
> Hi
>
> On Mon, Dec 16, 2013 at 2:45 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
>> 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 ...
>
> Ok, I will try hooking into the ath9k driver then and see why setting
> TX rates fails. Thanks a lot! Maybe Oleksij has some more ideas on
> that.
ath9k_htc has it own rate controller insight of firmware. We wont to
move this functionality to the host and use minstreal-rt, but currently
this project is not started and currently there is no clear start time
:( Beside, there are more problems with FWs rate controller.
David, if you need to fix this bug, i would you suggest you to
investigate in firmware. I will help you as match as i can.
--
Regards,
Oleksij
WARNING: multiple messages have this Message-ID (diff)
From: Oleksij Rempel <linux@rempel-privat.de>
To: David Herrmann <dh.herrmann@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Subject: Re: [BUG] P2P setup timeout
Date: Mon, 16 Dec 2013 15:57:48 +0100 [thread overview]
Message-ID: <52AF14EC.9010803@rempel-privat.de> (raw)
In-Reply-To: <CANq1E4TJWCgM4yCFC25b3ssQEvFv+hEhW6jP3_mQKxQCw-QtUQ@mail.gmail.com>
Am 16.12.2013 14:51, schrieb David Herrmann:
> Hi
>
> On Mon, Dec 16, 2013 at 2:45 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
>> 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 ...
>
> Ok, I will try hooking into the ath9k driver then and see why setting
> TX rates fails. Thanks a lot! Maybe Oleksij has some more ideas on
> that.
ath9k_htc has it own rate controller insight of firmware. We wont to
move this functionality to the host and use minstreal-rt, but currently
this project is not started and currently there is no clear start time
:( Beside, there are more problems with FWs rate controller.
David, if you need to fix this bug, i would you suggest you to
investigate in firmware. I will help you as match as i can.
--
Regards,
Oleksij
next prev parent reply other threads:[~2013-12-16 14:57 UTC|newest]
Thread overview: 24+ 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
2013-12-16 13:51 ` David Herrmann
2013-12-16 14:57 ` Oleksij Rempel [this message]
2013-12-16 14:57 ` Oleksij Rempel
2013-12-16 15:09 ` [ath9k-devel] " David Herrmann
2013-12-16 15:09 ` David Herrmann
2013-12-16 15:15 ` [ath9k-devel] " Johannes Berg
2013-12-16 15:15 ` Johannes Berg
2013-12-16 15:26 ` [ath9k-devel] " Oleksij Rempel
2013-12-16 15:26 ` Oleksij Rempel
2013-12-16 15:29 ` [ath9k-devel] " Johannes Berg
2013-12-16 15:29 ` Johannes Berg
2013-12-16 15:37 ` [ath9k-devel] " Oleksij Rempel
2013-12-16 15:37 ` Oleksij Rempel
2013-12-16 15:53 ` [ath9k-devel] " David Herrmann
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=52AF14EC.9010803@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.