From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Sid Hayn <sidhayn@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
lorenzo.bianconi@redhat.com, nbd@nbd.name,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 00/17] mt76 patches 2018-08-24 v2
Date: Wed, 29 Aug 2018 12:27:38 +0200 [thread overview]
Message-ID: <20180829102737.GA20763@redhat.com> (raw)
In-Reply-To: <CAM0KTbB5k54BvA2UOmoss-PuGtgHE_SGy2cG4n4ROxPH7kxYXA@mail.gmail.com>
Hi Sid
On Wed, Aug 29, 2018 at 02:26:44AM +0000, Sid Hayn wrote:
> Thanks for working on this, I have a small stack of different devices
> covered by this driver which I'm excited to test with.
>
> I'm running wireless-testing which may or may not be fully up to date
> on the patches you have sent (head is at
> c9cd161770dd1866207b70d41ec03c9a26eea94f from Aug 13th), so please
> tell me if this has already been fixed. I have a script that attempts
> to connect to 16 differently configured SSIDs using 33 different (yet
> compatible) wpa_supplicant.conf files and reports failures to me.
> It's hardly perfect, but it gives me an idea if something is obviously
> broken and needs a deeper dive. When I run this script against a
> device supported by mt76x2 or mt76x0 I get an unusual error.
> Everything goes fine, connect, dhcp, disconnect, connect, dhcp,
> disconnect, but after about 5 or 6 connections I start getting errors
> like this during wpa_supplicant:
>
> Could not set interface t2uh flags (UP): No space left on device
> nl80211: Could not set interface 't2uh' UP
> nl80211: deinit ifname=t2uh disabled_11b_rates=0
> t2uh: Failed to initialize driver interface
>
> and then this with dhcpcd:
>
> dhcpcd_prestartinterface: t2uh: No space left on device
> t2uh: waiting for carrier
>
> the same happens with just ifconfig up:
>
> SIOCSIFFLAGS: No space left on device
This looks like some memory leak, not sure where, but it quite probable
that is in the m76x{0,2} driver. You can check periodically using 'free'
command (or in more details by 'cat /proc/meminfo') if memory is
leaking. Then compile kernel with CONFIG_DEBUG_KMEMLEAK to see where
the leak happen.
Regards
Stanislaw
next prev parent reply other threads:[~2018-08-29 14:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 14:56 [PATCH v2 00/17] mt76 patches 2018-08-24 v2 Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 01/17] mt76: unify wait_for_mac Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 02/17] mt76: rename mt76x2_regs.h Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 03/17] mt76: merge mt76x0/regs.h into mt76x02_regs.h Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 04/17] mt76: create new mt76x02-lib module for common mt76x{0,2} code Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 05/17] mt76: fix mt76x02-lib module license Stanislaw Gruszka
2018-08-27 19:54 ` Felix Fietkau
2018-08-27 14:56 ` [PATCH v2 06/17] mt76: unify mac_get_key_info Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 07/17] mt76: add helpers for register access with mt76_dev struct Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 08/17] mt76: unify mac_shared_key_setup Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 09/17] mt76: unify mt76x02_mac_wcid_set_key Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 10/17] mt76: unify mac_wcid_setup Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 11/17] mt76: use mac_wcid_set_drop in mt76x0 Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 12/17] mt76x0: use mt76_wcid_free " Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 13/17] mt76: unify mt76x02_vif struct Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 14/17] mt76: unify sta structure part 1 Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 15/17] mt76: unify sta structure part 2 Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 16/17] mt76x0: initalize custom tx queues Stanislaw Gruszka
2018-08-27 14:56 ` [PATCH v2 17/17] mt76x0: use mt76x02_sta and mt76x02_tx_status Stanislaw Gruszka
2018-08-29 2:26 ` [PATCH v2 00/17] mt76 patches 2018-08-24 v2 Sid Hayn
2018-08-29 10:27 ` Stanislaw Gruszka [this message]
2018-08-29 18:10 ` Sid Hayn
2018-08-30 10:08 ` Stanislaw Gruszka
2018-09-01 7:47 ` Stanislaw Gruszka
2018-09-03 2:45 ` Sid Hayn
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=20180829102737.GA20763@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=sidhayn@gmail.com \
/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).