All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Oester <kernel@linuxace.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Deadlocks
Date: Thu, 10 Jun 2004 08:02:25 -0700	[thread overview]
Message-ID: <20040610150225.GA2682@linuxace.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0406101002170.1962-100000@blackhole.kfki.hu>

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.

  reply	other threads:[~2004-06-10 15:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 18:09 Deadlocks Phil Oester
2004-06-10  8:07 ` Deadlocks Jozsef Kadlecsik
2004-06-10 15:02   ` Phil Oester [this message]
2004-06-13 19:58 ` Deadlocks Patrick McHardy
2004-06-15  4:47   ` Deadlocks Phil Oester
2004-06-15  6:23     ` Deadlocks Patrick McHardy
2004-06-17 15:59       ` Deadlocks Phil Oester
2004-06-17 16:20         ` Deadlocks Patrick McHardy
2004-06-18 17:12           ` Deadlocks Phil Oester
2004-06-21  0:46             ` Deadlocks Patrick McHardy
2004-06-22  4:31               ` Deadlocks Phil Oester
2004-06-22  9:52                 ` Deadlocks Patrick McHardy
2004-06-29 17:54               ` Deadlocks Phil Oester
2004-06-29 18:00                 ` Deadlocks Patrick McHardy
2004-06-29 20:09                   ` Deadlocks Phil Oester
2004-06-30  9:50                     ` Deadlocks Patrick McHardy
2004-07-01 16:12                       ` Deadlocks Phil Oester

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=20040610150225.GA2682@linuxace.com \
    --to=kernel@linuxace.com \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter-devel@lists.netfilter.org \
    /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.