From: Matt Ayres <matta@tektonic.net>
To: Matt Ayres <matta@tektonic.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
James Morris <jmorris@namei.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: Re: Panic in ipt_do_table with 2.6.16.13-xen
Date: Thu, 18 May 2006 20:45:17 -0400 [thread overview]
Message-ID: <446D151D.6030307@tektonic.net> (raw)
In-Reply-To: <446D0E6D.2080600@tektonic.net>
Matt Ayres wrote:
>
>
> James Morris wrote:
>> On Thu, 18 May 2006, Matt Ayres wrote:
>>
>>>> I'm trying to suggest eliminating this driver & possible interaction
>>>> with
>>>> Xen network changes as a cause. If you can find a different type of
>>>> NIC to
>>>> plug in and use, or even try and change all of the params for the
>>>> tg3 with
>>>> ethtool, it'll help.
>>>>
>>> Hi,
>>>
>>> Thank you for the assistance. Which parameters do you suggest changing?
>>> TSO/flow control off?
>>
>> Yep, anything.
>
> Ok, "ethtool -K eth0 rx off tx off sg off tso off" should have turned it
> all off.
>
I think I confirmed the NIC is not the source of the problem. A few of
my servers have e100/tulip NIC's due to a bug with the chipset of the
on-board TG3 cards firmware and TSO. These servers that use the
e100/tulip drivers also experience the ipt_do_table bug.
Thanks,
Matt
WARNING: multiple messages have this Message-ID (diff)
From: Matt Ayres <matta@tektonic.net>
To: Matt Ayres <matta@tektonic.net>
Cc: James Morris <jmorris@namei.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Patrick McHardy <kaber@trash.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] Re: Panic in ipt_do_table with 2.6.16.13-xen
Date: Thu, 18 May 2006 20:45:17 -0400 [thread overview]
Message-ID: <446D151D.6030307@tektonic.net> (raw)
In-Reply-To: <446D0E6D.2080600@tektonic.net>
Matt Ayres wrote:
>
>
> James Morris wrote:
>> On Thu, 18 May 2006, Matt Ayres wrote:
>>
>>>> I'm trying to suggest eliminating this driver & possible interaction
>>>> with
>>>> Xen network changes as a cause. If you can find a different type of
>>>> NIC to
>>>> plug in and use, or even try and change all of the params for the
>>>> tg3 with
>>>> ethtool, it'll help.
>>>>
>>> Hi,
>>>
>>> Thank you for the assistance. Which parameters do you suggest changing?
>>> TSO/flow control off?
>>
>> Yep, anything.
>
> Ok, "ethtool -K eth0 rx off tx off sg off tso off" should have turned it
> all off.
>
I think I confirmed the NIC is not the source of the problem. A few of
my servers have e100/tulip NIC's due to a bug with the chipset of the
on-board TG3 cards firmware and TSO. These servers that use the
e100/tulip drivers also experience the ipt_do_table bug.
Thanks,
Matt
next prev parent reply other threads:[~2006-05-19 0:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 17:46 Panic in ipt_do_table with 2.6.16.13-xen Matt Ayres
2006-05-15 19:27 ` Patrick McHardy
2006-05-15 19:27 ` Patrick McHardy
2006-05-16 0:01 ` Matt Ayres
2006-05-16 0:01 ` Matt Ayres
2006-05-16 3:31 ` James Morris
2006-05-16 13:49 ` Matt Ayres
2006-05-16 13:49 ` [Xen-devel] " Matt Ayres
2006-05-16 15:28 ` James Morris
2006-05-18 23:58 ` Matt Ayres
2006-05-18 23:58 ` [Xen-devel] " Matt Ayres
2006-05-19 0:05 ` James Morris
2006-05-19 0:16 ` Matt Ayres
2006-05-19 0:16 ` [Xen-devel] " Matt Ayres
2006-05-19 0:45 ` Matt Ayres [this message]
2006-05-19 0:45 ` Matt Ayres
2006-05-21 17:43 ` Patrick McHardy
2006-05-21 17:43 ` Patrick McHardy
2006-05-22 14:31 ` Matt Ayres
2006-05-22 14:31 ` [Xen-devel] " Matt Ayres
2006-05-22 14:42 ` Keir Fraser
2006-05-22 14:43 ` Patrick McHardy
2006-05-22 14:43 ` Patrick McHardy
2006-05-23 9:54 ` Keir Fraser
2006-05-23 9:54 ` [Xen-devel] " Keir Fraser
2006-05-23 12:03 ` Matt Ayres
2006-05-23 12:03 ` [Xen-devel] " Matt Ayres
2006-05-23 21:15 ` Keir Fraser
2006-05-23 21:15 ` [Xen-devel] " Keir Fraser
2006-05-23 21:23 ` Matt Ayres
2006-05-23 21:23 ` [Xen-devel] " Matt Ayres
2006-05-23 21:27 ` Keir Fraser
2006-05-23 21:27 ` [Xen-devel] " Keir Fraser
2006-05-24 7:16 ` Gerd Hoffmann
2006-05-24 7:16 ` [Xen-devel] " Gerd Hoffmann
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=446D151D.6030307@tektonic.net \
--to=matta@tektonic.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--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.