From: Ben Hutchings <bhutchings@solarflare.com>
To: cpwu@tnsoft.com.cn
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [OOPS]e1000e .ko 1.0.2-k2
Date: Wed, 15 Dec 2010 13:52:34 +0000 [thread overview]
Message-ID: <1292421154.3136.642.camel@localhost> (raw)
In-Reply-To: <1292402583.2484.25.camel@cephhost>
On Wed, 2010-12-15 at 16:43 +0800, Jeff Wu wrote:
> Hi ,
>
> iozone test for our distributed file system ,
> we detect a oops(see below ,logs).
This is not an oops.
[...]
> [181174.967056] SLUB: Unable to allocate memory on node -1 (gfp=0x20)
[...]
Read that line again.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2010-12-15 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 8:43 [OOPS]e1000e .ko 1.0.2-k2 Jeff Wu
2010-12-15 13:52 ` Ben Hutchings [this message]
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=1292421154.3136.642.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=cpwu@tnsoft.com.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.