mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Brandeburg <jesse.brandeburg@gmail.com>
To: Richard Hartmann <richih.mailinglist@gmail.com>
Cc: e1000-devel@lists.sf.net, linux-kernel@vger.kernel.org,
	Andrew Pochinsky <avp@mit.edu>
Subject: Re: New thread: page allocation failure with E1000 (seems to be  reproducible)
Date: Mon, 1 Mar 2010 09:37:24 -0800	[thread overview]
Message-ID: <4807377b1003010937x8cea2c8hf1518eafb230cd88@mail.gmail.com> (raw)
In-Reply-To: <2d460de71003010934m76594f4fk2e0b505b1867538c@mail.gmail.com>

in the future please copy netdev@vger.kernel.org on networking issues.

On Mon, Mar 1, 2010 at 9:34 AM, Richard Hartmann
<richih.mailinglist@gmail.com> wrote:
> Hi Jesse,
>
>> the memory allocation (order:0), while unexpected, are not fatal, and
>> the e1000 driver is written to handle the failures during allocation.
>>
>> Does something else happen to the system after this or does operation continue?
>
> I can not be sure, but I _think_ some bogus data made it into userspace.
> I did have some binary in a text string I received & logged, which is a
> tad unusual.

hm, if that did occur it would be bad.  But it does sound like
operation continued, which is good.

>> You might be able to try the sysctl tweak to reserve a little more
>> memory for driver allocations.
>> # sysctl vm.min_free_kbytes
>> # sysctl -e vm.min_free_kbytes=<double what you have>
>
> I will try that, thanks.
>
>
>> have you increased the number of rx/tx descriptors in use by e1000?
>
> No. Should I?

I wouldn't recommend it if you're already having issues getting
order:0 allocations, it would just make the problem worse.  I wanted
to make sure you were not.

Jesse

  reply	other threads:[~2010-03-01 17:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 10:42 Richard Hartmann
2010-02-26 11:18 ` Richard Hartmann
2010-02-26 19:52 ` Jesse Brandeburg
2010-03-01 17:34   ` Richard Hartmann
2010-03-01 17:37     ` Jesse Brandeburg [this message]
2010-03-08 17:14     ` Richard Hartmann
2010-03-01 18:53 ` [E1000-devel] " Tantilov, Emil S
2010-03-08 17:09   ` Richard Hartmann

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=4807377b1003010937x8cea2c8hf1518eafb230cd88@mail.gmail.com \
    --to=jesse.brandeburg@gmail.com \
    --cc=avp@mit.edu \
    --cc=e1000-devel@lists.sf.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richih.mailinglist@gmail.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

all inboxes | Powered by JetHome®