From: Nathan Stratton <nathan@robotics.net>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: kernel BUG at mm/page_alloc.c:424!
Date: Thu, 6 Aug 2009 18:31:28 -0500 (CDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0908061830480.6111@bart.robotics.net> (raw)
In-Reply-To: <4A7B4A9B.7060407@goop.org>
On Thu, 6 Aug 2009, Jeremy Fitzhardinge wrote:
> On 08/06/09 14:22, Nathan Stratton wrote:
>> On Thu, 6 Aug 2009, Jeremy Fitzhardinge wrote:
>>
>>> Does disabling GRO/LRO and/or checksumming change anything?
>>
>> I am sorry, how would I do that?
>
> Using ethtool. Something like "ethtool --offload eth0 gro off lro off",
> I think.
They both were already off:
[root@cbridge1 ~]# ethtool -k eth0
Offload parameters for eth0:
Cannot get device rx csum settings: Operation not supported
Cannot get device flags: Operation not supported
rx-checksumming: off
tx-checksumming: on
scatter-gather: on
tcp-segmentation-offload: on
udp-fragmentation-offload: off
generic-segmentation-offload: off
generic-receive-offload: off
large-receive-offload: off
-Nathan
next prev parent reply other threads:[~2009-08-06 23:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 0:38 kernel BUG at mm/page_alloc.c:424! Nathan Stratton
2009-08-05 13:54 ` Konrad Rzeszutek Wilk
2009-08-05 13:50 ` Nathan Stratton
2009-08-06 19:26 ` Jeremy Fitzhardinge
2009-08-06 21:22 ` Nathan Stratton
2009-08-06 21:26 ` Jeremy Fitzhardinge
2009-08-06 23:31 ` Nathan Stratton [this message]
2009-08-06 23:38 ` Jeremy Fitzhardinge
2009-08-07 0:03 ` Nathan Stratton
2009-08-07 0:20 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2009-08-04 18:36 main.c:674: undefined reference to `xen_init_mtrr' Nathan Stratton
2009-08-04 19:04 ` kernel BUG at mm/page_alloc.c:424! Nathan Stratton
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=alpine.LFD.2.00.0908061830480.6111@bart.robotics.net \
--to=nathan@robotics.net \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.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 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.