Re: Fw: Re: 2.6.14-rc1 Critical bug: machine complete freeze

[Patrick McHardy <kaber@trash.net>]

[moved to netfilter-devel]

Patrizio Bassi wrote:
> Patrick McHardy ha scritto:
>> Please try if turning it off helps. The deadlock is pretty likely to
>> happen in other situations too, its best not to use event notifications
>> currently.
>>
> yes, i tested and it works now.
> as trivial and fast fix you can block both by config script.

Just turning off event notifications should be fine .. I want people
to use the netbios helper.

> i have some big problems with forwarding and bridge configuration too.
> i've been investigating to find the real problem, in order to report a
> valid bug-entry.
> 
> in few words:
> iptables works perfectly, apart for icmp forwarding.
> it's not a iptables wrong config, because if i destroy the chains and i
> reload them it works perfectly.
> 
> test situation:
> 
> Client -> Router with bridge
> 
> I start the Router, apply iptables rules, connect to internet, perfect.
> I start the Client, try to ping the router or google, nothing.
> Destroy iptables, reload rules in the Router.
> Client can ping google and router.
> 
> My iptables script was about 1 year old, and worked perfectly.
> New kernel (dunno which...2.6.1x) introduced this problem.

Try adding some logging rules to see why it gets dropped (-m state
--state INVALID for example).