mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: Hugh Dickins <hughd@google.com>
Cc: David Madore <david+ml@madore.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: kernel 3.2.27 on arm: WARNING: at mm/page_alloc.c:2109 __alloc_pages_nodemask+0x1d4/0x68c()
Date: Sat, 1 Sep 2012 10:20:18 +0200	[thread overview]
Message-ID: <20120901082018.GA16762@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <alpine.LSU.2.00.1208311900330.1936@eggly.anvils>

Hugh Dickins <hughd@google.com> :
> [ Cc'ing original mail to netdev as the problem may be recognized there ]
[...]
> Francois is right that a GFP_ATOMIC allocation from pskb_expand_head()
> is failing, which can easily happen, and cause your "failed to reallocate
> TX buffer" errors; but it's well worth looking up what's actually on
> lines 2108 and 2109 of mm/page_alloc.c in 3.2.27:
> 
> 	if (order >= MAX_ORDER) {
> 		WARN_ON_ONCE(!(gfp_mask & __GFP_NOWARN));

You are right. The wifi Tx path error is not related.

I overlooked it was using SLUB btw.

> That was probably not a sane allocation request, it has gone out of range:
> maybe the skb header is even corrupted.  If you're lucky, it might be
> something that netdev will recognize as already fixed.

Afaics nothing related to mv643xx_eth.c, nor pskb_expand_head nor
ip6_forward, at least nothing trivially close. Eric may provide a
better answer.

-- 
Ueimor

  reply	other threads:[~2012-09-01  8:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29  0:25 David Madore
2012-08-29 19:32 ` Francois Romieu
2012-08-31 10:59   ` David Madore
2012-08-31 13:57     ` David Madore
2012-08-31 18:12       ` Francois Romieu
2012-09-01  2:21 ` Hugh Dickins
2012-09-01  8:20   ` Francois Romieu [this message]
2012-09-02 22:51     ` David Madore
2012-10-04 16:02   ` Maxime Bizon
2012-10-04 16:29     ` Eric Dumazet
2012-10-05  7:41       ` Eric Dumazet
2012-10-05 10:49         ` Maxime Bizon
2012-10-05 12:22           ` Eric Dumazet
2012-10-05 12:37             ` Eric Dumazet
2012-10-05 12:39               ` Eric Dumazet
2012-10-05 12:51             ` Maxime Bizon
2012-10-05 13:02               ` Eric Dumazet
2012-10-05 14:50                 ` Maxime Bizon
2012-10-05 15:04                   ` Eric Dumazet
2012-10-05 15:15                     ` Maxime Bizon
2012-10-05 15:37                       ` Eric Dumazet
2012-10-04 16:50     ` Eric Dumazet
2012-10-04 17:09       ` Maxime Bizon
2012-10-04 17:17         ` Eric Dumazet
2012-10-04 17:34           ` Maxime Bizon
2012-10-04 21:27             ` Eric Dumazet

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=20120901082018.GA16762@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=david+ml@madore.org \
    --cc=eric.dumazet@gmail.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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

all inboxes | Powered by JetHome®