From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Out of memory problem with newer firmware
Date: Sun, 10 Apr 2011 22:12:52 +0200 [thread overview]
Message-ID: <BANLkTin0-MWxJV=7cNnOhiSKbieuo7OAfQ@mail.gmail.com> (raw)
Summary:
1) Chris has ASUS WL500pv2 with OpenWRT
2) This is router with Broadcom 5354 SoC and LP-PHY card
3) Firmware 410.2160 (broadcom-wl-4.150.10.5.tar.bz2) works OK
4) Firmware 478.104 (broadcom-wl-4.178.10.4.tar.bz2) causes OOM
Larry was testing his LP-PHY with kmemleak but didn't find anything.
Chris traced a lot of skbs being allocated before OOM (500+).
I suspect that with new firmware we provide slightly different RX
packets to mac80211 and there is sth wrong with mac80211 causing SKBs
not being freed. I don't have any other idea how changing firmware
could cause out of memory problems.
The alloc code is question is dma.c::~585
skb = __dev_alloc_skb(ring->rx_buffersize, gfp_flags);
I've written patch to dump data we provide mac80211. My hope is to
notice differences in that data between older vs. newer firmware.
Chris: could you try attached patch and provide dmesg from older and
newer firmware with this patch applied?
--
Rafa?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xmit.rx_count2.patch
Type: application/octet-stream
Size: 1676 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20110410/d2f241a2/attachment.obj>
next reply other threads:[~2011-04-10 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 20:12 Rafał Miłecki [this message]
2011-04-11 9:59 ` Out of memory problem with newer firmware chris at martin.cc
2011-04-11 11:01 ` Rafał Miłecki
2011-04-11 12:46 ` chris at martin.cc
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='BANLkTin0-MWxJV=7cNnOhiSKbieuo7OAfQ@mail.gmail.com' \
--to=zajec5@gmail.com \
--cc=b43-dev@lists.infradead.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 NNTP newsgroup(s).