lkml.org 
[lkml]   [2006]   [May]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Xen-devel] Re: Panic in ipt_do_table with 2.6.16.13-xen


James Morris wrote:
> On Tue, 16 May 2006, Matt Ayres wrote:
>
>>>> My ruleset is pretty bland. 2 rules in the raw table to tell the system
>>>> to
>>>> only track my forwarded ports, 2 rules in the nat table for forwarding
>>>> (intercepting) 2 ports, and then in the FORWARD tables 2 rules per VM to
>>>> just
>>>> account traffic.
>>> Can you try using a different NIC?
>>>
>> This happens on 30 different hosts. Using the same kernel I get varying
>> uptime of "hasn't crashed since the upgrade to 2.6.16" to "crashes every day".
>> All are Tyan S2882D boards w/ integrated Tigon3. The trace I posted to this
>> thread indicate tg3, but in many other traces I have the trace doesn't include
>> any driver calls. They all panic in ipt_do_table. I would have pasted the
>> others, but I didn't save the System.map for either of them and they are all
>> pretty similar.
>
> 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?

Here is my ruleset for those interested:

# iptables -t raw -L -v
Chain OUTPUT (policy ACCEPT 27441 packets, 4832K bytes)
pkts bytes target prot opt in out source
destination

Chain PREROUTING (policy ACCEPT 195M packets, 156G bytes)
pkts bytes target prot opt in out source
destination
1332K 144M NOTRACK !tcp -- any any anywhere
anywhere
54 5293 ACCEPT tcp -- any any anywhere
anywhere tcp dpt:7373
4564 223K ACCEPT tcp -- any any anywhere
anywhere tcp dpt:7322
194M 156G NOTRACK tcp -- any any anywhere
anywhere tcp dpt:!7373
194M 156G NOTRACK tcp -- any any anywhere
anywhere tcp dpt:!7322

# iptables -t nat -L -v
Chain OUTPUT (policy ACCEPT 2114 packets, 155K bytes)
pkts bytes target prot opt in out source
destination

Chain POSTROUTING (policy ACCEPT 2114 packets, 155K bytes)
pkts bytes target prot opt in out source
destination

Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
6 344 DNAT tcp -- eth0 any anywhere
anywhere tcp dpt:7373 to:host.ip.address:443
8 408 DNAT tcp -- eth0 any anywhere
anywhere tcp dpt:7322 to:host.ip.address:22


iptables -L -v just shows 2 rules per Virtual Machine for accounting.
This averages about 100 rules in the FORWARD chain. Example:

# iptables -L -v
Chain FORWARD (policy ACCEPT 195M packets, 156G bytes)
pkts bytes target prot opt in out source
destination
0 0 all -- any any xx.xx.xx.xx
anywhere
0 0 all -- any any anywhere
xx.xx.xx.xx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-05-19 02:01    [W:0.038 / U:16.772 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site