Petersson, Mats [EMAIL PROTECTED] wrote:
Looks like the GSO is involved?
It's certainly what crashed your machine :) It's probably not the
guilty party though. Someone is passing through a TSO packet with
checksum set to something other than CHECKSUM_HW.
I bet it's netfilter and we just never
I got the exact same thing when attempting to use BOINC on a single node
supporting a 5 node open SSI cluster, (5 guests) and yes the problem
went away when I flushed the rules.
I attributed this to a quirk with the cluster CVIP, because I had also
assigned each node its own outbound IP in
-Original Message-
From: Tim Post [mailto:[EMAIL PROTECTED]
Sent: 07 July 2006 16:06
To: Herbert Xu
Cc: Petersson, Mats; netdev@vger.kernel.org;
[EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [Xen-devel] kernel BUG at net/core/dev.c:1133!
I got the exact
-Original Message-
From: Herbert Xu [mailto:[EMAIL PROTECTED]
Sent: 07 July 2006 15:40
To: Petersson, Mats
Cc: [EMAIL PROTECTED]; netdev@vger.kernel.org;
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [Xen-devel] kernel BUG at net/core/dev.c:1133!
Petersson, Mats [EMAIL
Herbert Xu wrote:
Petersson, Mats [EMAIL PROTECTED] wrote:
Looks like the GSO is involved?
It's certainly what crashed your machine :) It's probably not the
guilty party though. Someone is passing through a TSO packet with
checksum set to something other than CHECKSUM_HW.
I bet it's
On Fri, Jul 07, 2006 at 05:03:36PM +0200, Petersson, Mats wrote:
So, nothing going on there... I certainly haven't got NAT on my machine,
as my machine is within the AMD network, and doesn't need NAT. AMD
probably uses NAT as part of it's external communications, but I doubt
it's used at all
