From: Mathieu Slabbinck <matty.slabbinck@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] tx99 memory allocate failure
Date: Tue, 17 May 2016 16:23:07 +0200 [thread overview]
Message-ID: <CAOFH_kHTVxzEJzesuHFtEYqqqVXdAAw0vkOmzsL1XJJsbOXgdA@mail.gmail.com> (raw)
In-Reply-To: <B55DA282FD16424BB8D58FC600198C2D9B8FB2@sfo1exc-mbxp08.nbttech.com>
Solved!
Thanks a bunch!!!
Kr
Mathieu
On Tue, May 17, 2016 at 4:16 PM, Eduardo Abinader <
Eduardo.Abinader@riverbed.com> wrote:
> Hi Mathieu,
>
> Add the monitor interface like this:
>
> #iw phy phy0 interface add moni0 type monitor flags active
>
>
> BR,
> Eduardo Abinader
> ------------------------------
> *From:* Mathieu Slabbinck [matty.slabbinck at gmail.com]
> *Sent:* Tuesday, May 17, 2016 4:11 PM
> *To:* Eduardo Abinader
> *Cc:* ath9k-devel at lists.ath9k.org
> *Subject:* Re: [ath9k-devel] tx99 memory allocate failure
>
> Hi Eduardo,
>
> I'm using this:
> #!/bin/bash
> mount -t debugfs nodev /sys/kernel/debug
>
> echo "Prep for tx99"
> iw phy phy0 interface add moni0 type monitor
> ip link set dev moni0 up
>
> echo "Activating tx99"
> echo 15 > /sys/kernel/debug/ieee80211/phy0/ath9k/tx99_power
> echo 1 > /sys/kernel/debug/ieee80211/phy0/ath9k/tx99
>
> Is that not enough?
> Ifconfig lists moni0 as follows:
> moni0 Link encap:UNSPEC HWaddr
> BC-30-7E-BC-59-98-35-65-00-00-00-00-00-00-00-00
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B
>
> Kr
>
> On Tue, May 17, 2016 at 4:07 PM, Eduardo Abinader <
> Eduardo.Abinader at riverbed.com> wrote:
>
>> Hi,
>>
>> Create the monitor interface with active flag set.
>>
>> BR.
>> ------------------------------
>> *From:* ath9k-devel-bounces at lists.ath9k.org [
>> ath9k-devel-bounces at lists.ath9k.org] on behalf of Mathieu Slabbinck [
>> matty.slabbinck at gmail.com]
>> *Sent:* Tuesday, May 17, 2016 3:52 PM
>> *To:* ath9k-devel at lists.ath9k.org
>> *Subject:* [ath9k-devel] tx99 memory allocate failure
>>
>> Hi,
>>
>> I'm having some issues running the tx99 features of the ath9k driver.
>> Seems like every time I try to run it, I get this:
>> sh: write error: cannot allocate memory.
>>
>> After some poking, I found it's returning -ENOMEN in tx99.c.
>> Which is due to !sc-tx99_skb
>> Which on it's turn is due to an empty value for sc->tx99_vif.
>>
>> So essentially, it's going wrong in ath9k_build_tx99_skb and returns NULL
>> when checking:
>> if (!sc->tx99_vif) {
>> return NULL;
>> }
>>
>> Anybody some ideas on what the actual root cause can be of this and/or
>> how to solve it?
>>
>> Kernel version: 4.1.0
>>
>> Thanks & Kr
>>
>> Mathieu
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20160517/e73dfd12/attachment.htm
prev parent reply other threads:[~2016-05-17 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 13:52 [ath9k-devel] tx99 memory allocate failure Mathieu Slabbinck
2016-05-17 14:07 ` Eduardo Abinader
2016-05-17 14:11 ` Mathieu Slabbinck
2016-05-17 14:16 ` Eduardo Abinader
2016-05-17 14:23 ` Mathieu Slabbinck [this message]
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=CAOFH_kHTVxzEJzesuHFtEYqqqVXdAAw0vkOmzsL1XJJsbOXgdA@mail.gmail.com \
--to=matty.slabbinck@gmail.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).