Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Robert Bradley <robert.bradley1@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Fwd:  3.3.6-2
Date: Thu, 24 May 2012 09:18:00 -0700	[thread overview]
Message-ID: <4D0F5C65-2401-470F-A6D8-BE18E8BA25C7@gmx.de> (raw)
In-Reply-To: <4FBE5767.6080704@gmail.com>

Hi Robert,

On May 24, 2012, at 8:44 AM, Robert Bradley wrote:

> On 24/05/12 04:48, Sebastian Moeller wrote:
>> A) under moderate wireless stress I get a lot of allocation failures from slub, like:
>> [ 1221.664062] ath: skbuff alloc of size 1926 failed
>> In the routers dmesg. And every now and then the router crashes and reboots (I have not yet found a way to make this happen reliably, it seems to require some uptime)
> 
> This looks to me like a possible memory leak somewhere, but I'm no expert.

	Not being an expert I concur.

>  (Unless cerowrt is using tmpfs and filling up memory with logs, of course.)  

	I tried to check that, but since I can nor reproduce the crashes easily yet I have not been able to test that hypothesis (when I checked "df -h"  on the router there always was some room left, but heck for all I know it might be the log entries for the allocation failures that quickly eat up all the remaining memory) I will try to test this hypothesis. Currently I tried to check dmesg and free in rapid succession during the test runs that are prone to cause the crash free memory fluctuates some but I never saw it reach 0 just before crashing.

> Is UDP from the wired side to the Internet also OK?  I'm assuming it is, but it would be nice to prove that it is actually a leak in ath9k and/or the wireless stack first!

	Actually I have not tested that yet (again with the crash somewhat hard to reproduce I will have to take the wireless out of use for 24 to 48 hours to be reasonably sure that the issue does not occur under wired connections). That said, I will go and work on that. So I have my testing work charted out and will post again once I have more data.

Best
	Sebastian




> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


  reply	other threads:[~2012-05-24 16:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00404BC8-3761-409D-A1C8-9213D7D9A3DF@gmx.de>
2012-05-24  3:48 ` Sebastian Moeller
2012-05-24 15:44   ` Robert Bradley
2012-05-24 16:18     ` Sebastian Moeller [this message]
2012-05-24 16:32       ` Jim Gettys
2012-05-24 18:12         ` Sebastian Moeller
2012-05-24 18:15           ` Jim Gettys
2012-05-24 18:58             ` Robert Bradley
2012-05-25  6:41               ` [Cerowrt-devel] 3.3.6-2 Sebastian Moeller
2012-05-25  7:02                 ` Dave Taht
2012-05-25 11:11                 ` Robert Bradley
2012-05-25 18:25                   ` Sebastian Moeller
2012-05-25 22:38                     ` Robert Bradley
2012-06-02  7:03                       ` Sebastian Moeller
2012-06-03 22:24                         ` Robert Bradley
2012-06-06 23:03                           ` Sebastian Moeller
2012-05-25  0:04             ` [Cerowrt-devel] Fwd: 3.3.6-2 Sebastian Moeller

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D0F5C65-2401-470F-A6D8-BE18E8BA25C7@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=robert.bradley1@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