mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Herz - Profihost AG <p.herz@profihost.ag>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Rientjes <rientjes@google.com>,
	Andi Kleen <andi@firstfloor.org>,
	s.priebe@profihost.ag, linux-kernel@vger.kernel.org
Subject: Re: Vanilla-Kernel 3 - page allocation failure
Date: Mon, 24 Oct 2011 10:19:39 +0200	[thread overview]
Message-ID: <4EA51F9B.7090806@profihost.ag> (raw)
In-Reply-To: <1319443278.2381.2.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>

Am 24.10.2011 10:01, schrieb Eric Dumazet:
> Le lundi 24 octobre 2011 à 09:21 +0200, Philipp Herz - Profihost AG a
> écrit :
>
>> does that mean that there was no firmware limitation with kernel 2.6.32
>> or that the tg3 module has any "disable warnings" flag matching
>> __GFP_NOWARN?
>>
>
> There is no __GFP_NOWARN trick on tg3.
>
> We tend to prefer to be notified of a memory problem, instead of
> hide ...
yes,
that's exactly what would like to understand in comparison to the 
behavior of kernel 2.6.32.

why does this notification show up now and never did before...

>
> By the way, apparently this driver drops the frame and doesnt increase
> tx_dropped device counter. A patch will follow.
fine

>
> Could you post your full dmesg ?
>
>
Currently i can not provide any further information, 'cause server has 
been restarted.

What exactly are you looking for?

  reply	other threads:[~2011-10-24  8:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 10:25 Philipp Herz - Profihost AG
2011-10-18 11:32 ` Thadeu Lima de Souza Cascardo
2011-10-18 12:07   ` Philipp Herz - Profihost AG
2011-10-18 12:38     ` Thadeu Lima de Souza Cascardo
2011-10-18 13:24       ` Philipp Herz - Profihost AG
2011-10-18 14:35         ` Thadeu Lima de Souza Cascardo
2011-10-19  6:45           ` Philipp Herz - Profihost AG
2011-10-18 15:51 ` Andi Kleen
2011-10-18 17:02   ` Dave Jones
2011-10-18 18:59     ` Andi Kleen
2011-10-19  1:58   ` David Rientjes
2011-10-24  6:33     ` Philipp Herz - Profihost AG
2011-10-24  7:03       ` Eric Dumazet
2011-10-24  7:21         ` Philipp Herz - Profihost AG
2011-10-24  8:01           ` Eric Dumazet
2011-10-24  8:19             ` Philipp Herz - Profihost AG [this message]
2011-10-24  8:29               ` Eric Dumazet
2011-10-24  8:36                 ` Stefan Priebe - Profihost AG
2011-10-26 20:26       ` David Rientjes
2011-10-27  7:13         ` Philipp Herz - Profihost AG
2011-10-27 20:08           ` David Rientjes
2011-10-20 21:11   ` Valdis.Kletnieks
2011-10-21  6:36     ` Philipp Herz - Profihost AG

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=4EA51F9B.7090806@profihost.ag \
    --to=p.herz@profihost.ag \
    --cc=andi@firstfloor.org \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rientjes@google.com \
    --cc=s.priebe@profihost.ag \
    /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

Powered by JetHome