From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Oester Subject: Re: Deadlocks Date: Thu, 10 Jun 2004 08:02:25 -0700 Sender: netfilter-devel-admin@lists.netfilter.org Message-ID: <20040610150225.GA2682@linuxace.com> References: <20040609180909.GA11445@linuxace.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netfilter-devel@lists.netfilter.org Return-path: To: Jozsef Kadlecsik Content-Disposition: inline In-Reply-To: Errors-To: netfilter-devel-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Id: netfilter-devel.vger.kernel.org I always apply the orphaned expectations patch (I'm the one who tracked that one down and submitted the original patch ;-) That is not the problem here -- this is a locking bug as shown by the SysRq output. I'm temporarily running 2.6.6 without SMP support to work around it. Phil On Thu, Jun 10, 2004 at 10:07:16AM +0200, Jozsef Kadlecsik wrote: > On Wed, 9 Jun 2004, Phil Oester wrote: > > > For the past 3 months I've been experiencing deadlocks on some heavily > > used gateway/firewall boxes which started after upgrading from 2.4.20. > > > > I can confirm that moving back to 2.4.20 stops the hangs, moving to 2.4.21 > > (or any kernel after that) makes them return. I am in the process of testing > > out each individual 2.4.21-pre to find out where exactly the problem is. > > > > In the interim, I've collected some SysRq output which may help in the > > analysis. Below are two separate lockups on a 2.6.6 kernel. Anyone have > > any bright ideas? > > Could you try out the 05_linux-2.4.26-orphaned_expect.patch or > 05_linux-2.6.6-orphaned_expect.patch depending on the kernel > from pom-ng/updates? I think that is the fix for your lockups.