linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 28 Jun 2010 13:01:06 -0400	[thread overview]
Message-ID: <4C28D552.30000@gmail.com> (raw)
In-Reply-To: <1277742425.13673.1376.camel@rchatre-DESK>

reinette chatre wrote:
> On Sun, 2010-06-27 at 10:14 -0700, Richard Farina wrote:
>   
>>> ---
>>>  drivers/net/wireless/iwlwifi/iwl-agn-lib.c |    5 +++--
>>>  drivers/net/wireless/iwlwifi/iwl-fh.h      |    2 +-
>>>  2 files changed, 4 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/net/wireless/iwlwifi/iwl-agn-lib.c b/drivers/net/wireless/iwlwifi/iwl-agn-lib.c
>>> index 0f292a2..2815ee7 100644
>>> --- a/drivers/net/wireless/iwlwifi/iwl-agn-lib.c
>>> +++ b/drivers/net/wireless/iwlwifi/iwl-agn-lib.c
>>> @@ -613,7 +613,8 @@ void iwlagn_rx_allocate(struct iwl_priv *priv, gfp_t priority)
>>>               }
>>>               spin_unlock_irqrestore(&rxq->lock, flags);
>>>
>>> -             if (rxq->free_count > RX_LOW_WATERMARK)
>>> +             if ((priority == GFP_ATOMIC) ||
>>> +                 (rxq->free_count > RX_LOW_WATERMARK / 4))
>>>                       gfp_mask |= __GFP_NOWARN;
>>>
>>>       
>
> Here I set the allocation mask to not print _any_ warnings when
> allocation is atomic ...
>
>
>   
>> [180257.090410] swapper: page allocation failure. order:1, mode:0x4020
>> [180257.090414] Pid: 0, comm: swapper Not tainted 2.6.34-pentoo-r2 #2
>> [180257.090416] Call Trace:
>>     
>
> ... clearly this is an allocation warning ...
>
>   
>> [180257.090418]  <IRQ>  [<ffffffff810984c0>]
>> __alloc_pages_nodemask+0x571/0x5b9
>> [180257.090437]  [<ffffffffa05162f3>] iwlagn_rx_allocate+0x98/0x2e0 [iwlagn]
>> [180257.090445]  [<ffffffffa051668c>] iwlagn_rx_replenish_now+0x16/0x23
>> [iwlagn]
>>     
>
> ... but it is an atomic one, which after the patch should not be
> printing _any_ warning ...
>
>   
I dunno, I really don't. but I did just verify the patch and it is 
correct and applied.

Thanks,
Rick
> I am very confused now.
>
> Reinette
>
>
>
>   


  reply	other threads:[~2010-06-28 17:00 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
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 [this message]
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=4C28D552.30000@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).