linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	"Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
	linux-mm@kvack.org
Subject: Re: [RFC][PATCH]  4KB stack + irq stack for x86
Date: Wed, 02 Oct 2002 15:13:18 -0700	[thread overview]
Message-ID: <3D9B6F7E.1060004@us.ibm.com> (raw)
In-Reply-To: <20021002174320.J28857@redhat.com>

Benjamin LaHaise wrote:
> On Wed, Oct 02, 2002 at 02:18:36PM -0700, Dave Hansen wrote:
> 
>>I've resynced Ben's patch against 2.5.40.  However, I'm getting some 
>>strange failures.  The patch is good enough to pass LTP, but 
>>consistently freezes when I run tcpdump on it.
> 
> Try running tcpdump with the stack checking patch applied.  That should 
> give you a decent backtrace for the problem.

My first suspicion was that it was just overflowing, but not getting 
the message out.  I just realized that my latest testing (the last 24 
hours) was on the original patch, not the updated one that you posted 
later, which included the stack checking.  I'm sure that I was having 
the same problem with the overflow checking enabled and _not_ getting 
any errors from it, but I'll redo the testing for my sanity's sake.

-- 
Dave Hansen
haveblue@us.ibm.com

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-10-02 22:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02 21:18 Dave Hansen
2002-10-02 21:43 ` Benjamin LaHaise
2002-10-02 22:13   ` Dave Hansen [this message]
2002-10-02 21:56 ` Andreas Dilger
2002-10-02 22:02   ` Martin J. Bligh
2002-10-03 11:10   ` Denis Vlasenko

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=3D9B6F7E.1060004@us.ibm.com \
    --to=haveblue@us.ibm.com \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox