From: Patrick McHardy <kaber@trash.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>,
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: Sun, 21 May 2006 19:43:41 +0200 [thread overview]
Message-ID: <4470A6CD.5010501@trash.net> (raw)
In-Reply-To: <446D151D.6030307@tektonic.net>
Matt Ayres wrote:
> 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.
There is an identical report in the netfilter bugzilla, also crashes
(on x86_64) in ipt_do_table with Xen. I haven't heard anything of
similar crashes without Xen, so I doubt that the bug is in the
netfilter code.
https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=478
next prev parent reply other threads:[~2006-05-21 17:43 UTC|newest]
Thread overview: 20+ 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-16 0:01 ` Matt Ayres
2006-05-16 3:31 ` James Morris
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-19 0:05 ` James Morris
2006-05-19 0:16 ` Matt Ayres
2006-05-19 0:45 ` Matt Ayres
2006-05-21 17:43 ` Patrick McHardy [this message]
2006-05-22 14:31 ` Matt Ayres
2006-05-22 14:42 ` Keir Fraser
2006-05-22 14:43 ` Patrick McHardy
2006-05-23 9:54 ` Keir Fraser
2006-05-23 12:03 ` Matt Ayres
2006-05-23 21:15 ` Keir Fraser
2006-05-23 21:23 ` Matt Ayres
2006-05-23 21:27 ` Keir Fraser
2006-05-24 7:16 ` 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=4470A6CD.5010501@trash.net \
--to=kaber@trash.net \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matta@tektonic.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox