linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Mark Symonds <mark@symonds.net>
Cc: linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@redhat.com>,
	William Lee Irwin III <wli@holomorphy.com>,
	Harald Welte <laforge@netfilter.org>
Subject: Re: 2.4.23 hard lock, 100% reproducible.
Date: Mon, 8 Dec 2003 08:17:30 -0200 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0312080815460.30140-100000@logos.cnet> (raw)
In-Reply-To: <008501c3bd18$697361e0$7a01a8c0@gandalf>



On Sun, 7 Dec 2003, Mark Symonds wrote:

> 
> Hi,
> 
> > 
> > The first oops looks like:
> > 
> > Unable to handle kernel NULL pointer
> > dereference at virtual address: 00000000
> > 
> [...]
> > 
> > 
> > Isnt it a bit weird that the full backtrace is not reported ? 
> > 
> > wli suggests that might stack corruption.
> > 
> 
> My bad - wrote it down by hand originally since 
> it was locked hard.  
> 
> > 
> > I dont see any suspicious change around tcp_print_conntrack().
> > 
> > Any clues? 
> > 
> 
> I'm using ipchains compatability in there, looks like 
> this is a possible cause - getting a patch right now,
> will test and let y'all know (and then switch to 
> iptables, finally). 

Mark,

Please try the latest BK tree. There was a known bug in the netfilter code 
which could cause the lockups. 

 




  parent reply	other threads:[~2003-12-08 10:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-07  6:50 2.4.23 hard lock, 100% reproducible Alex Davis
2003-12-07  6:55 ` William Lee Irwin III
     [not found]   ` <046a01c3bca1$267ba5e0$7a01a8c0@gandalf>
2003-12-07  9:07     ` William Lee Irwin III
2003-12-07  9:16       ` Keith Owens
2003-12-07  9:36         ` William Lee Irwin III
2003-12-08 16:34           ` Oliver Teuber
2003-12-07 10:01         ` Mark Symonds
2003-12-07 11:34           ` Martin Josefsson
2003-12-07 14:40           ` Marcelo Tosatti
2003-12-07 23:18             ` Mark Symonds
2003-12-08  4:53               ` William Lee Irwin III
2003-12-08  7:12               ` Tim Timmerman
2003-12-08 11:06                 ` Marcelo Tosatti
2003-12-09  6:29                   ` Tim Timmerman
2003-12-08 10:17               ` Marcelo Tosatti [this message]
2003-12-08 15:54                 ` Stephan von Krawczynski
2003-12-08 16:15                   ` Marcelo Tosatti
2003-12-08 16:31                     ` Jeff Garzik
2003-12-08 16:55                     ` Stephan von Krawczynski
2003-12-08 19:56                 ` Mark Symonds
2003-12-07  7:33 ` Mark Symonds
2003-12-07 16:24   ` Alex Davis
  -- strict thread matches above, loose matches on Subject: below --
2003-12-08 17:06 Xose Vazquez Perez
2003-12-07  2:36 Mark Symonds
2003-12-07  3:30 ` Philippe Troin
2003-12-07  4:34   ` Mark Symonds
2003-12-07 18:32     ` Chris Frey
2003-12-07 18:49       ` James Bourne
2003-12-07 19:21         ` David Rees
2003-12-07 20:19           ` James Bourne

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=Pine.LNX.4.44.0312080815460.30140-100000@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=davem@redhat.com \
    --cc=laforge@netfilter.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@symonds.net \
    --cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).