Re: [OpenWrt-Devel] ath10k memory leak on 19.07 branch and mikrotik RB952Ui-5ac2nD?

2019-12-08 Thread Joe Ayers
On Sat, Dec 7, 2019 at 5:19 AM Hauke Mehrtens  wrote:
>
> On 12/6/19 7:02 PM, Ben Greear wrote:
> > On 12/6/19 9:44 AM, Joe Ayers wrote:
> >>>
> >>>
>  Possibly the same symptoms don't exist on 128MB RAM devices.
> >>>
> >>> Like there is some if condition, which is doing some nasty things on 64M
> >>> devices? I admit, that I don't have ath10k-ct source code under my
> >>> pillow, but
> >>> it doesn't make much sense to me.
> >>>
>  Comparable results between above and my 64MB device.   However, if the
>  sleep time is extended the consumption is more
> >>>
> >>> Ok, I'll let it run overnight with 120s sleep in between.
> >>>
>  I suspect this is not the intended behavior.
> >>>
> >>> No its not and it's even strange, that I'm not seeing it here if it
> >>> should
> >>> happen in the "default setup". Maybe its because:
> >>>
> >>> 1. You're using custom image (I'm using official prebuilt images)
> >>> 2. You're not providing all the steps needed to reproduce the issue
> >>> 3. I've way different hardware
> >>>
> >>> Every detail could make huge difference.
> >>>
> >>> -- ynezz
> >>
> >> On the device I am testing, it is both (2GHz) ath9k and (5GHz) ath10k.
> >>These look to be related patches to this issue:
> >>
> >> 960-0010-ath10k-limit-htt-rx-ring-size.patch
> >> 960-0011-ath10k-limit-pci-buffer-size.patch
> >>
> >> In the v19.07.0-rc2 build for the rb-nor-flash-16M-ac ar71xx image,
> >> these patches are applied to backports-4.19.85-1, but don't seem to be
> >> applied to ath10k-ct-2019-09-09-5e8cd86f.Should ath10k-ct have
> >> these and other patches?The device's installed packages do include
> >> ath10k-ct (from downloads.openwrt.org installed image).
> >
> > I think that if you need the patches for upstream ath10k, then you
> > should also apply
> > the patches to ath10k-ct.
> >
> > Platforms with more memory probably do not need or benefit from those
> > patches.
> >
> > Thanks,
> > Ben
> >
> Hi,
>
> I am fine with adding these patches to ath10k-ct if they solve problems.
>
> It would be nice if a description could be added to the patches so I
> know what kind of buffers are reduced there.
>
> Will someone send a patch?
>
> Hauke
>

I'm currently testing with the following patches with openwrt-19.07 on
RB952Ui-5ac2nD (hAP ac lite).   Sorry, I know enough to be dangerous
to  provide a description.I am seeing ~15M of RAM consumed, but
have not seen OOM kick in yet, like before.  These patches are an
improvement so far -- usable 64M device.

Joe

Index: 
openwrt/package/kernel/ath10k-ct/patches/960-0010-ath10k-limit-htt-rx-ring-size.patch
===
--- /dev/null
+++ 
openwrt/package/kernel/ath10k-ct/patches/960-0010-ath10k-limit-htt-rx-ring-size.patch
@@ -0,0 +1,11 @@
+--- a/ath10k-4.19/htt.h
 b/ath10k-4.19/htt.h
+@@ -238,7 +238,7 @@ enum htt_rx_ring_flags {
+ };
+
+ #define HTT_RX_RING_SIZE_MIN 128
+-#define HTT_RX_RING_SIZE_MAX 2048
++#define HTT_RX_RING_SIZE_MAX 512
+ #define HTT_RX_RING_SIZE HTT_RX_RING_SIZE_MAX
+ #define HTT_RX_RING_FILL_LEVEL (((HTT_RX_RING_SIZE) / 2) - 1)
+ #define HTT_RX_RING_FILL_LEVEL_DUAL_MAC (HTT_RX_RING_SIZE - 1)
Index: 
openwrt/package/kernel/ath10k-ct/patches/960-0011-ath10k-limit-pci-buffer-size.patch
===
--- /dev/null
+++ 
openwrt/package/kernel/ath10k-ct/patches/960-0011-ath10k-limit-pci-buffer-size.patch
@@ -0,0 +1,38 @@
+--- a/ath10k-4.19/pci.c
 b/ath10k-4.19/pci.c
+@@ -142,7 +142,7 @@ static struct ce_attr host_ce_config_wla
+   .flags = CE_ATTR_FLAGS,
+   .src_nentries = 0,
+   .src_sz_max = 2048,
+-  .dest_nentries = 512,
++  .dest_nentries = 128,
+   .recv_cb = ath10k_pci_htt_htc_rx_cb,
+   },
+
+@@ -151,7 +151,7 @@ static struct ce_attr host_ce_config_wla
+   .flags = CE_ATTR_FLAGS,
+   .src_nentries = 0,
+   .src_sz_max = 2048,
+-  .dest_nentries = 128,
++  .dest_nentries = 64,
+   .recv_cb = ath10k_pci_htc_rx_cb,
+   },
+
+@@ -178,7 +178,7 @@ static struct ce_attr host_ce_config_wla
+   .flags = CE_ATTR_FLAGS,
+   .src_nentries = 0,
+   .src_sz_max = 512,
+-  .dest_nentries = 512,
++  .dest_nentries = 128,
+   .recv_cb = ath10k_pci_htt_rx_cb,
+   },
+
+@@ -203,7 +203,7 @@ static struct ce_attr host_ce_config_wla
+   .flags = CE_ATTR_FLAGS,
+   .src_nentries = 0,
+   .src_sz_max = 2048,
+-  .dest_nentries = 128,
++  .dest_nentries = 96,
+   .recv_cb = ath10k_pci_pktlog_rx_cb,
+   },
+

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] ath10k memory leak on 19.07 branch and mikrotik RB952Ui-5ac2nD?

2019-12-07 Thread Lech Perczak

W dniu 2019-12-06 o 18:44, Joe Ayers pisze:



Possibly the same symptoms don't exist on 128MB RAM devices.

Like there is some if condition, which is doing some nasty things on 64M
devices? I admit, that I don't have ath10k-ct source code under my pillow, but
it doesn't make much sense to me.


Comparable results between above and my 64MB device.   However, if the
sleep time is extended the consumption is more

Ok, I'll let it run overnight with 120s sleep in between.


I suspect this is not the intended behavior.

No its not and it's even strange, that I'm not seeing it here if it should
happen in the "default setup". Maybe its because:

1. You're using custom image (I'm using official prebuilt images)
2. You're not providing all the steps needed to reproduce the issue
3. I've way different hardware

Every detail could make huge difference.

-- ynezz

On the device I am testing, it is both (2GHz) ath9k and (5GHz) ath10k.
   These look to be related patches to this issue:

960-0010-ath10k-limit-htt-rx-ring-size.patch
960-0011-ath10k-limit-pci-buffer-size.patch

In the v19.07.0-rc2 build for the rb-nor-flash-16M-ac ar71xx image,
these patches are applied to backports-4.19.85-1, but don't seem to be
applied to ath10k-ct-2019-09-09-5e8cd86f.Should ath10k-ct have
these and other patches?The device's installed packages do include
ath10k-ct (from downloads.openwrt.org installed image).

Joe AE6XE

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
.


I can only add that I got the same behaviour with my TL-WR902AC just 
ported to ath79 on master (based on 
f19e471f3206d0b5885490e52972085d2da2a10b). In about 20 minutes system 
was unusable - I couldn't fully copy a 4MB sysupgrade image to /tmp.
Branch used to build the image is here: 
https://github.com/Leo-PL/openwrt/commits/tl-wr902ac-v1_ath79


I can offer my help with testing the fixes, as it seems to me that it's 
not the first time I observe this issue, only now I got a device 
affected by it.


With kind regards,
Lech


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] ath10k memory leak on 19.07 branch and mikrotik RB952Ui-5ac2nD?

2019-12-07 Thread Joe Ayers
On Sat, Dec 7, 2019 at 5:19 AM Hauke Mehrtens  wrote:
>
> On 12/6/19 7:02 PM, Ben Greear wrote:
> > On 12/6/19 9:44 AM, Joe Ayers wrote:
> >>>
> >>>
>  Possibly the same symptoms don't exist on 128MB RAM devices.
> >>>
> >>> Like there is some if condition, which is doing some nasty things on 64M
> >>> devices? I admit, that I don't have ath10k-ct source code under my
> >>> pillow, but
> >>> it doesn't make much sense to me.
> >>>
>  Comparable results between above and my 64MB device.   However, if the
>  sleep time is extended the consumption is more
> >>>
> >>> Ok, I'll let it run overnight with 120s sleep in between.
> >>>
>  I suspect this is not the intended behavior.
> >>>
> >>> No its not and it's even strange, that I'm not seeing it here if it
> >>> should
> >>> happen in the "default setup". Maybe its because:
> >>>
> >>> 1. You're using custom image (I'm using official prebuilt images)
> >>> 2. You're not providing all the steps needed to reproduce the issue
> >>> 3. I've way different hardware
> >>>
> >>> Every detail could make huge difference.
> >>>
> >>> -- ynezz
> >>
> >> On the device I am testing, it is both (2GHz) ath9k and (5GHz) ath10k.
> >>These look to be related patches to this issue:
> >>
> >> 960-0010-ath10k-limit-htt-rx-ring-size.patch
> >> 960-0011-ath10k-limit-pci-buffer-size.patch
> >>
> >> In the v19.07.0-rc2 build for the rb-nor-flash-16M-ac ar71xx image,
> >> these patches are applied to backports-4.19.85-1, but don't seem to be
> >> applied to ath10k-ct-2019-09-09-5e8cd86f.Should ath10k-ct have
> >> these and other patches?The device's installed packages do include
> >> ath10k-ct (from downloads.openwrt.org installed image).
> >
> > I think that if you need the patches for upstream ath10k, then you
> > should also apply
> > the patches to ath10k-ct.
> >
> > Platforms with more memory probably do not need or benefit from those
> > patches.
> >
> > Thanks,
> > Ben
> >
> Hi,
>
> I am fine with adding these patches to ath10k-ct if they solve problems.
>
> It would be nice if a description could be added to the patches so I
> know what kind of buffers are reduced there.
>
> Will someone send a patch?
>
> Hauke
>

Are there other patches that should be applied?

package/kernel/mac80211/patches/ath:
080-ath10k_thermal_config.patch
921-ath10k_init_devices_synchronously.patch
930-ath10k_add_tpt_led_trigger.patch
960-0010-ath10k-limit-htt-rx-ring-size.patch
960-0011-ath10k-limit-pci-buffer-size.patch
972-ath10k_fix-crash-due-to-wrong-handling-of-peer_bw_rxnss_override-parameter.patch
973-ath10k_fix-band_center_freq-handling-for-VHT160-in-recent-firmwares.patch
974-ath10k_add-LED-and-GPIO-controlling-support-for-various-chipsets.patch
975-ath10k-use-tpt-trigger-by-default.patch
977-ath10k-add-support-for-configuring-management-packet.patch
978-ath10k-fix-possible-out-of-bound-access-of-ath10k_ra.patch
979-ath10k-fix-incorrect-multicast-broadcast-rate-settin.patch
980-ath10k-fix-max-antenna-gain-unit.patch
981-ath10k-adjust-tx-power-reduction-for-US-regulatory-d.patch

package/kernel/ath10k-ct/patches:
161-ath10k-add-support-for-configuring-management-packet.patch
162-ath10k-fix-possible-out-of-bound-access-of-ath10k_ra.patch
163-ath10k-fix-incorrect-multicast-broadcast-rate-settin.patch
164-ath10k-commit-rates-from-mac80211.patch
201-ath10k-4.16_add-LED-and-GPIO-controlling-support-for-various-chipsets.patch
202-ath10k-4.16-use-tpt-trigger-by-default.patch
203-ath10k-Limit-available-channels-via-DT-ieee80211-fre.patch

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] ath10k memory leak on 19.07 branch and mikrotik RB952Ui-5ac2nD?

2019-12-07 Thread Hauke Mehrtens
On 12/6/19 7:02 PM, Ben Greear wrote:
> On 12/6/19 9:44 AM, Joe Ayers wrote:
>>>
>>>
 Possibly the same symptoms don't exist on 128MB RAM devices.
>>>
>>> Like there is some if condition, which is doing some nasty things on 64M
>>> devices? I admit, that I don't have ath10k-ct source code under my
>>> pillow, but
>>> it doesn't make much sense to me.
>>>
 Comparable results between above and my 64MB device.   However, if the
 sleep time is extended the consumption is more
>>>
>>> Ok, I'll let it run overnight with 120s sleep in between.
>>>
 I suspect this is not the intended behavior.
>>>
>>> No its not and it's even strange, that I'm not seeing it here if it
>>> should
>>> happen in the "default setup". Maybe its because:
>>>
>>> 1. You're using custom image (I'm using official prebuilt images)
>>> 2. You're not providing all the steps needed to reproduce the issue
>>> 3. I've way different hardware
>>>
>>> Every detail could make huge difference.
>>>
>>> -- ynezz
>>
>> On the device I am testing, it is both (2GHz) ath9k and (5GHz) ath10k.
>>    These look to be related patches to this issue:
>>
>> 960-0010-ath10k-limit-htt-rx-ring-size.patch
>> 960-0011-ath10k-limit-pci-buffer-size.patch
>>
>> In the v19.07.0-rc2 build for the rb-nor-flash-16M-ac ar71xx image,
>> these patches are applied to backports-4.19.85-1, but don't seem to be
>> applied to ath10k-ct-2019-09-09-5e8cd86f.    Should ath10k-ct have
>> these and other patches?    The device's installed packages do include
>> ath10k-ct (from downloads.openwrt.org installed image).
> 
> I think that if you need the patches for upstream ath10k, then you
> should also apply
> the patches to ath10k-ct.
> 
> Platforms with more memory probably do not need or benefit from those
> patches.
> 
> Thanks,
> Ben
> 
Hi,

I am fine with adding these patches to ath10k-ct if they solve problems.

It would be nice if a description could be added to the patches so I
know what kind of buffers are reduced there.

Will someone send a patch?

Hauke



signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] ath10k memory leak on 19.07 branch and mikrotik RB952Ui-5ac2nD?

2019-12-06 Thread Ben Greear

On 12/6/19 9:44 AM, Joe Ayers wrote:




Possibly the same symptoms don't exist on 128MB RAM devices.


Like there is some if condition, which is doing some nasty things on 64M
devices? I admit, that I don't have ath10k-ct source code under my pillow, but
it doesn't make much sense to me.


Comparable results between above and my 64MB device.   However, if the
sleep time is extended the consumption is more


Ok, I'll let it run overnight with 120s sleep in between.


I suspect this is not the intended behavior.


No its not and it's even strange, that I'm not seeing it here if it should
happen in the "default setup". Maybe its because:

1. You're using custom image (I'm using official prebuilt images)
2. You're not providing all the steps needed to reproduce the issue
3. I've way different hardware

Every detail could make huge difference.

-- ynezz


On the device I am testing, it is both (2GHz) ath9k and (5GHz) ath10k.
   These look to be related patches to this issue:

960-0010-ath10k-limit-htt-rx-ring-size.patch
960-0011-ath10k-limit-pci-buffer-size.patch

In the v19.07.0-rc2 build for the rb-nor-flash-16M-ac ar71xx image,
these patches are applied to backports-4.19.85-1, but don't seem to be
applied to ath10k-ct-2019-09-09-5e8cd86f.Should ath10k-ct have
these and other patches?The device's installed packages do include
ath10k-ct (from downloads.openwrt.org installed image).


I think that if you need the patches for upstream ath10k, then you should also 
apply
the patches to ath10k-ct.

Platforms with more memory probably do not need or benefit from those patches.

Thanks,
Ben

--
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] ath10k memory leak on 19.07 branch and mikrotik RB952Ui-5ac2nD?

2019-12-06 Thread Joe Ayers
>
>
> > Possibly the same symptoms don't exist on 128MB RAM devices.
>
> Like there is some if condition, which is doing some nasty things on 64M
> devices? I admit, that I don't have ath10k-ct source code under my pillow, but
> it doesn't make much sense to me.
>
> > Comparable results between above and my 64MB device.   However, if the
> > sleep time is extended the consumption is more
>
> Ok, I'll let it run overnight with 120s sleep in between.
>
> > I suspect this is not the intended behavior.
>
> No its not and it's even strange, that I'm not seeing it here if it should
> happen in the "default setup". Maybe its because:
>
> 1. You're using custom image (I'm using official prebuilt images)
> 2. You're not providing all the steps needed to reproduce the issue
> 3. I've way different hardware
>
> Every detail could make huge difference.
>
> -- ynezz

On the device I am testing, it is both (2GHz) ath9k and (5GHz) ath10k.
  These look to be related patches to this issue:

960-0010-ath10k-limit-htt-rx-ring-size.patch
960-0011-ath10k-limit-pci-buffer-size.patch

In the v19.07.0-rc2 build for the rb-nor-flash-16M-ac ar71xx image,
these patches are applied to backports-4.19.85-1, but don't seem to be
applied to ath10k-ct-2019-09-09-5e8cd86f.Should ath10k-ct have
these and other patches?The device's installed packages do include
ath10k-ct (from downloads.openwrt.org installed image).

Joe AE6XE

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] ath10k memory leak on 19.07 branch and mikrotik RB952Ui-5ac2nD?

2019-12-05 Thread Petr Štetiar
Joe Ayers  [2019-12-05 10:17:22]:

> Possibly the same symptoms don't exist on 128MB RAM devices. 

Like there is some if condition, which is doing some nasty things on 64M
devices? I admit, that I don't have ath10k-ct source code under my pillow, but
it doesn't make much sense to me.

> Comparable results between above and my 64MB device.   However, if the
> sleep time is extended the consumption is more

Ok, I'll let it run overnight with 120s sleep in between.

> I suspect this is not the intended behavior.

No its not and it's even strange, that I'm not seeing it here if it should
happen in the "default setup". Maybe its because:

1. You're using custom image (I'm using official prebuilt images)
2. You're not providing all the steps needed to reproduce the issue
3. I've way different hardware

Every detail could make huge difference.

-- ynezz

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] ath10k memory leak on 19.07 branch and mikrotik RB952Ui-5ac2nD?

2019-12-05 Thread Joe Ayers
> I'm not able to reproduce it on TP-Link Archer C7 v5.
>
> > Attempting to use the hAP ac lite model RB952Ui-5ac2nD with the 5GHz
> > radio0 802.11ac seems to be unstable and consume available memory.
> > This is only enabling radio0 with no other changes and bringing wifi
> > up/down to reproduce.   Am I doing something silly, or should I submit
> > a bug?
>
> uptime > /tmp/wifi.log && \
> cat /etc/openwrt_release >> /tmp/wifi.log && \
> uci set wireless.radio0.disabled=0 && \
> uci commit wireless && \
> wifi up && \
> echo "up: $(free | grep Mem:)" >> /tmp/wifi.log && \
> sleep 120 && \
> wifi down && sleep 1 && \
> echo "dn: $(free | grep Mem:)" >> /tmp/wifi.log && \
> for i in $(seq 1 10); do \
> wifi up; sleep 15; echo "up: $(free | grep Mem:)" >> /tmp/wifi.log; \
> wifi down; sleep 15; wifi down; sleep 1; wifi down; sleep 1; \
> wifi down; sleep 1; echo "dn: $(free | grep Mem:)" >> /tmp/wifi.log; \
> done; cat /tmp/wifi.log
>
>  14:06:05 up 2 min,  load average: 0.24, 0.19, 0.08
> DISTRIB_ID='OpenWrt'
> DISTRIB_RELEASE='19.07.0-rc2'
> DISTRIB_REVISION='r10775-db8345d8e4'
> DISTRIB_TARGET='ath79/generic'
> DISTRIB_ARCH='mips_24kc'
> DISTRIB_DESCRIPTION='OpenWrt 19.07.0-rc2 r10775-db8345d8e4'
> DISTRIB_TAINTS=''
> up: Mem: 124528   15128   99536  769864   
> 80684
> dn: Mem: 124528   14860   99076  84   10592   
> 80596
> up: Mem: 124528   22592   91340  84   10596   
> 72872
> dn: Mem: 124528   14884   99048  84   10596   
> 80580
> up: Mem: 124528   22848   91084  84   10596   
> 72616
> dn: Mem: 124528   14884   99048  84   10596   
> 80576
> up: Mem: 124528   22848   91084  84   10596   
> 72612
> dn: Mem: 124528   14884   99048  84   10596   
> 80576
> up: Mem: 124528   22848   91084  84   10596   
> 72612
> dn: Mem: 124528   14884   99048  84   10596   
> 80576
> up: Mem: 124528   22940   90992  84   10596   
> 72520
> dn: Mem: 124528   14916   99016  84   10596   
> 80544
> up: Mem: 124528   22808   91124  84   10596   
> 72652
> dn: Mem: 124528   14868   99064  84   10596   
> 80592
> up: Mem: 124528   22900   91032  84   10596   
> 72560
> dn: Mem: 124528   14876   99056  84   10596   
> 80584
> up: Mem: 124528   22676   91256  84   10596   
> 72784
> dn: Mem: 124528   14904   99028  84   10596   
> 80556
> up: Mem: 124528   22712   91220  84   10596   
> 72748
> dn: Mem: 124528   14936   98996  84   10596   
> 80524
> up: Mem: 124528   22708   91224  84   10596   
> 72752
> dn: Mem: 124528   14936   98996  84   10596   
> 80524
>
>  15:53:35 up 1 min,  load average: 1.35, 0.41, 0.14
> DISTRIB_ID='OpenWrt'
> DISTRIB_RELEASE='19.07.0-rc2'
> DISTRIB_REVISION='r10775-db8345d8e4'
> DISTRIB_TARGET='ar71xx/generic'
> DISTRIB_ARCH='mips_24kc'
> DISTRIB_DESCRIPTION='OpenWrt 19.07.0-rc2 r10775-db8345d8e4'
> DISTRIB_TAINTS=''
> up: Mem: 124624   14068  100680 1209876   
> 81760
> dn: Mem: 124624   14368   99524 140   10732   
> 80996
> up: Mem: 124624   22072   91816 140   10736   
> 73296
> dn: Mem: 124624   14360   99528 140   10736   
> 81004
> up: Mem: 124624   22072   91816 140   10736   
> 73292
> dn: Mem: 124624   14360   99528 140   10736   
> 81004
> up: Mem: 124624   22068   91820 140   10736   
> 73296
> dn: Mem: 124624   14360   99528 140   10736   
> 81004
> up: Mem: 124624   22196   91692 140   10736   
> 73168
> dn: Mem: 124624   14360   99528 140   10736   
> 81004
> up: Mem: 124624   22356   91532 140   10736   
> 73008
> dn: Mem: 124624   14392   99496 140   10736   
> 80972
> up: Mem: 124624   22164   91724 140   10736   
> 73200
> dn: Mem: 124624   14344   99544 140   10736   
> 81020
> up: Mem: 124624   22956   90932 140   10736   
> 72408
> dn: Mem: 124624   14352   99536 140   10736   
> 81012
> up: Mem: 124624   22924   90964 140 

Re: [OpenWrt-Devel] ath10k memory leak on 19.07 branch and mikrotik RB952Ui-5ac2nD?

2019-12-03 Thread Petr Štetiar
Joe Ayers  [2019-11-28 18:40:23]:

Hi,

I'm not able to reproduce it on TP-Link Archer C7 v5.

> Attempting to use the hAP ac lite model RB952Ui-5ac2nD with the 5GHz
> radio0 802.11ac seems to be unstable and consume available memory.
> This is only enabling radio0 with no other changes and bringing wifi
> up/down to reproduce.   Am I doing something silly, or should I submit
> a bug?

uptime > /tmp/wifi.log && \
cat /etc/openwrt_release >> /tmp/wifi.log && \
uci set wireless.radio0.disabled=0 && \
uci commit wireless && \
wifi up && \
echo "up: $(free | grep Mem:)" >> /tmp/wifi.log && \
sleep 120 && \
wifi down && sleep 1 && \
echo "dn: $(free | grep Mem:)" >> /tmp/wifi.log && \
for i in $(seq 1 10); do \
wifi up; sleep 15; echo "up: $(free | grep Mem:)" >> /tmp/wifi.log; \
wifi down; sleep 15; wifi down; sleep 1; wifi down; sleep 1; \
wifi down; sleep 1; echo "dn: $(free | grep Mem:)" >> /tmp/wifi.log; \
done; cat /tmp/wifi.log

 14:06:05 up 2 min,  load average: 0.24, 0.19, 0.08
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='19.07.0-rc2'
DISTRIB_REVISION='r10775-db8345d8e4'
DISTRIB_TARGET='ath79/generic'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='OpenWrt 19.07.0-rc2 r10775-db8345d8e4'
DISTRIB_TAINTS=''
up: Mem: 124528   15128   99536  769864   
80684
dn: Mem: 124528   14860   99076  84   10592   
80596
up: Mem: 124528   22592   91340  84   10596   
72872
dn: Mem: 124528   14884   99048  84   10596   
80580
up: Mem: 124528   22848   91084  84   10596   
72616
dn: Mem: 124528   14884   99048  84   10596   
80576
up: Mem: 124528   22848   91084  84   10596   
72612
dn: Mem: 124528   14884   99048  84   10596   
80576
up: Mem: 124528   22848   91084  84   10596   
72612
dn: Mem: 124528   14884   99048  84   10596   
80576
up: Mem: 124528   22940   90992  84   10596   
72520
dn: Mem: 124528   14916   99016  84   10596   
80544
up: Mem: 124528   22808   91124  84   10596   
72652
dn: Mem: 124528   14868   99064  84   10596   
80592
up: Mem: 124528   22900   91032  84   10596   
72560
dn: Mem: 124528   14876   99056  84   10596   
80584
up: Mem: 124528   22676   91256  84   10596   
72784
dn: Mem: 124528   14904   99028  84   10596   
80556
up: Mem: 124528   22712   91220  84   10596   
72748
dn: Mem: 124528   14936   98996  84   10596   
80524
up: Mem: 124528   22708   91224  84   10596   
72752
dn: Mem: 124528   14936   98996  84   10596   
80524

 15:53:35 up 1 min,  load average: 1.35, 0.41, 0.14
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='19.07.0-rc2'
DISTRIB_REVISION='r10775-db8345d8e4'
DISTRIB_TARGET='ar71xx/generic'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='OpenWrt 19.07.0-rc2 r10775-db8345d8e4'
DISTRIB_TAINTS=''
up: Mem: 124624   14068  100680 1209876   
81760
dn: Mem: 124624   14368   99524 140   10732   
80996
up: Mem: 124624   22072   91816 140   10736   
73296
dn: Mem: 124624   14360   99528 140   10736   
81004
up: Mem: 124624   22072   91816 140   10736   
73292
dn: Mem: 124624   14360   99528 140   10736   
81004
up: Mem: 124624   22068   91820 140   10736   
73296
dn: Mem: 124624   14360   99528 140   10736   
81004
up: Mem: 124624   22196   91692 140   10736   
73168
dn: Mem: 124624   14360   99528 140   10736   
81004
up: Mem: 124624   22356   91532 140   10736   
73008
dn: Mem: 124624   14392   99496 140   10736   
80972
up: Mem: 124624   22164   91724 140   10736   
73200
dn: Mem: 124624   14344   99544 140   10736   
81020
up: Mem: 124624   22956   90932 140   10736   
72408
dn: Mem: 124624   14352   99536 140   10736   
81012
up: Mem: 124624   22924   90964 140   10736   
72440
dn: Mem: 124624   14352   99536 140   10736   
81012
up: Mem: 124624   22444   91444 140   10736   

Re: [OpenWrt-Devel] ath10k memory leak on 19.07 branch and mikrotik RB952Ui-5ac2nD?

2019-12-02 Thread Matthias Schiffer
On 11/29/19 3:40 AM, Joe Ayers wrote:
> Attempting to use the hAP ac lite model RB952Ui-5ac2nD with the 5GHz
> radio0 802.11ac seems to be unstable and consume available memory.
> This is only enabling radio0 with no other changes and bringing wifi
> up/down to reproduce.   Am I doing something silly, or should I submit
> a bug?

Sounds like the issue that this PR tried to work around:

https://github.com/openwrt/openwrt/pull/1077

Kind regards,
Matthias


> 
> root@OpenWrt:/tmp# cat /etc/openwrt_release
> DISTRIB_ID='OpenWrt'
> DISTRIB_RELEASE='19.07-SNAPSHOT'
> DISTRIB_REVISION='r10752-1859391e9e'
> DISTRIB_TARGET='ar71xx/mikrotik'
> DISTRIB_ARCH='mips_24kc'
> DISTRIB_DESCRIPTION='OpenWrt 19.07-SNAPSHOT r10752-1859391e9e'
> DISTRIB_TAINTS='no-all'
> root@OpenWrt:/tmp# free
>   totalusedfree  shared  buff/cache   
> available
> Mem:  59264   14104   332327804   11928   
> 23352
> Swap: 0   0   0
> root@OpenWrt:/tmp# wifi up
> 'radio1' is disabled
> 'radio1' is disabled
> root@OpenWrt:/tmp# free
>   totalusedfree  shared  buff/cache   
> available
> Mem:  59264   19556   242047804   15504   
> 16156
> Swap: 0   0   0
> root@OpenWrt:/tmp# date; free
> Tue Nov 26 23:32:37 UTC 2019
>   totalusedfree  shared  buff/cache   
> available
> Mem:  59264   29768   139847804   15512
> 5944
> Swap: 0   0   0
> root@OpenWrt:/tmp# date; free
> Tue Nov 26 23:32:55 UTC 2019
>   totalusedfree  shared  buff/cache   
> available
> Mem:  59264   33384   103687804   15512
> 2328
> Swap: 0   0   0
> root@OpenWrt:/tmp# date; free
> Tue Nov 26 23:33:14 UTC 2019
>   totalusedfree  shared  buff/cache   
> available
> Mem:  59264   37424   104527804   11388 
> 304
> Swap: 0   0   0
> root@OpenWrt:/tmp# wifi down
> -ash: can't fork: Out of memory
> root@OpenWrt:/tmp# wifi down
> -ash: can't fork: Out of memory
> root@OpenWrt:/tmp# wifi down
> /sbin/wifi: line 188: can't fork: Out of memory
> Failed to parse message data
> 'radio1' is disabled
> root@OpenWrt:/tmp# wifi down
> Segmentation fault
> Failed to parse message data
> 'radio1' is disabled
> root@OpenWrt:/tmp# free
>   totalusedfree  shared  buff/cache   
> available
> Mem:  59264   3943685087804   11320   > 0
> Swap: 0   0   0
> root@OpenWrt:/tmp# wifi down
> 'radio1' is disabled
> root@OpenWrt:/tmp# date; free
> Tue Nov 26 23:34:08 UTC 2019
>   totalusedfree  shared  buff/cache   
> available
> Mem:  59264   13716   339327804   11616   
> 23892
> Swap: 0   0   0
> root@OpenWrt:/tmp#
> 
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> 




signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] ath10k memory leak on 19.07 branch and mikrotik RB952Ui-5ac2nD?

2019-11-28 Thread Joe Ayers
Attempting to use the hAP ac lite model RB952Ui-5ac2nD with the 5GHz
radio0 802.11ac seems to be unstable and consume available memory.
This is only enabling radio0 with no other changes and bringing wifi
up/down to reproduce.   Am I doing something silly, or should I submit
a bug?

root@OpenWrt:/tmp# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='19.07-SNAPSHOT'
DISTRIB_REVISION='r10752-1859391e9e'
DISTRIB_TARGET='ar71xx/mikrotik'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='OpenWrt 19.07-SNAPSHOT r10752-1859391e9e'
DISTRIB_TAINTS='no-all'
root@OpenWrt:/tmp# free
  totalusedfree  shared  buff/cache   available
Mem:  59264   14104   332327804   11928   23352
Swap: 0   0   0
root@OpenWrt:/tmp# wifi up
'radio1' is disabled
'radio1' is disabled
root@OpenWrt:/tmp# free
  totalusedfree  shared  buff/cache   available
Mem:  59264   19556   242047804   15504   16156
Swap: 0   0   0
root@OpenWrt:/tmp# date; free
Tue Nov 26 23:32:37 UTC 2019
  totalusedfree  shared  buff/cache   available
Mem:  59264   29768   139847804   155125944
Swap: 0   0   0
root@OpenWrt:/tmp# date; free
Tue Nov 26 23:32:55 UTC 2019
  totalusedfree  shared  buff/cache   available
Mem:  59264   33384   103687804   155122328
Swap: 0   0   0
root@OpenWrt:/tmp# date; free
Tue Nov 26 23:33:14 UTC 2019
  totalusedfree  shared  buff/cache   available
Mem:  59264   37424   104527804   11388 304
Swap: 0   0   0
root@OpenWrt:/tmp# wifi down
-ash: can't fork: Out of memory
root@OpenWrt:/tmp# wifi down
-ash: can't fork: Out of memory
root@OpenWrt:/tmp# wifi down
/sbin/wifi: line 188: can't fork: Out of memory
Failed to parse message data
'radio1' is disabled
root@OpenWrt:/tmp# wifi down
Segmentation fault
Failed to parse message data
'radio1' is disabled
root@OpenWrt:/tmp# free
  totalusedfree  shared  buff/cache   available
Mem:  59264   3943685087804   11320   0
Swap: 0   0   0
root@OpenWrt:/tmp# wifi down
'radio1' is disabled
root@OpenWrt:/tmp# date; free
Tue Nov 26 23:34:08 UTC 2019
  totalusedfree  shared  buff/cache   available
Mem:  59264   13716   339327804   11616   23892
Swap: 0   0   0
root@OpenWrt:/tmp#

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel