From: Richard Farina <sidhayn@gmail.com>
To: reinette chatre <reinette.chatre@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: intel 5100/iwlagn bug in 2.6.35-rc2 during large file transfer
Date: Thu, 24 Jun 2010 12:12:18 -0400 [thread overview]
Message-ID: <4C2383E2.8000909@gmail.com> (raw)
In-Reply-To: <1277225293.25793.2257.camel@rchatre-DESK>
reinette chatre wrote:
> On Wed, 2010-06-16 at 19:56 -0700, Richard Farina wrote:
>
>> The repeated line appears ad infinitum filling my dmesg buffer. This of
>> hangcheck timer seem to trigger with every large file transfer on my
>> intel 5100. What would you like me to do to provide a more useful
>> output as this is currently extremely easy to reproduce. Kernel 2.6.34
>> using compat-wireless stable 2.6.35-rc2
>>
>> Thanks,
>> Rick Farina
>>
>> phy0: failed to reallocate TX buffer
>> phy0: failed to reallocate TX buffer
>> phy0: failed to reallocate TX buffer
>> phy0: failed to reallocate TX buffer
>> phy0: failed to reallocate TX buffer
>> phy0: failed to reallocate TX buffer
>> phy0: failed to reallocate TX buffer
>>
>
> First mac80211 runs out of memory ... it cannot even allocate enough
> memory for a skb header.
>
>
>> net_ratelimit: 22 callbacks suppressed
>> __alloc_pages_slowpath: 3799 callbacks suppressed
>> swapper: page allocation failure. order:1, mode:0x4020
>> Pid: 0, comm: swapper Not tainted 2.6.34-pentoo #5
>> Call Trace:
>> <IRQ> [<ffffffff8109cb74>] __alloc_pages_nodemask+0x571/0x5b9
>> [<ffffffff816732e9>] ? skb_release_data+0xc4/0xc9
>> [<ffffffffa04701e4>] iwlagn_rx_allocate+0x98/0x25a [iwlagn]
>>
>
> Next driver runs out of memory.
>
> Note that the above are all atomic allocations that fail and should be
> able to recover.
>
> Is your system low on memory? Are you running applications that take a
> lot of memory? Does your wifi connection drop or otherwise suffer at the
> time you see these messages?
>
>
I have 4GB of RAM on this system, I often run a VM which wastes like
half that but that still leaves 2GB for linux and I'm running XFCE4 so
not exactly a memory hog. It's possible that firefox leaks ram until I'm
out but that would be a LOT of leak, much more than I usually see.
Yeah, as you may guess these errors cause my wifi connection to slow
drastically. If I had to guess, since this happens when I make a large
file transfer it is likely that something related is leaking RAM. I'm
using wget or axel to download and NFS to dump the files on a NAS. I'll
try to trigger this again and watch memory usage to see if I can find
something other than the driver that could be leaking. Failing that,
what do I need to enable to find a leak in the driver?
Thanks,
Rick Farina
> Reinette
>
>
>
>
>
next prev parent reply other threads:[~2010-06-24 16:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 2:56 intel 5100/iwlagn bug in 2.6.35-rc2 during large file transfer Richard Farina
2010-06-17 23:35 ` Richard Farina
2010-06-22 16:48 ` reinette chatre
2010-06-24 16:12 ` Richard Farina [this message]
2010-06-24 17:13 ` reinette chatre
2010-06-24 17:30 ` Richard Farina
2010-06-24 17:48 ` reinette chatre
2010-06-25 16:28 ` Richard Farina
2010-06-25 18:57 ` reinette chatre
2010-06-27 17:14 ` Richard Farina
2010-06-28 16:27 ` reinette chatre
2010-06-28 17:01 ` Richard Farina
2010-06-28 20:39 ` reinette chatre
2010-06-29 3:57 ` Richard Farina
2010-06-30 23:32 ` reinette chatre
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=4C2383E2.8000909@gmail.com \
--to=sidhayn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.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).