linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: Steven Cole <elenstev@mesatop.com>,
	Andrew Morton <akpm@zip.com.au>,
	linux-mm@kvack.org
Subject: Re: 2.5.33-mm3 dbench hang and 2.5.33 page allocation failures
Date: Fri, 6 Sep 2002 02:02:57 +0200	[thread overview]
Message-ID: <E17n6aP-0006Cw-00@starship> (raw)
In-Reply-To: <1031269130.5760.318.camel@tux>

On Friday 06 September 2002 01:38, Martin Josefsson wrote:
> On Thu, 2002-09-05 at 21:15, Daniel Phillips wrote:
> > On Thursday 05 September 2002 19:23, Steven Cole wrote:
> > > I booted 2.5.33-mm3 and ran dbench with increasing
> > > numbers of clients: 1,2,3,4,6,8,10,12,16,etc. while
> > > running vmstat -n 1 600 from another terminal.
> > > 
> > > After about 3 minutes, the output from vmstat stopped,
> > > and the dbench 16 output stopped.  The machine would
> > > respond to pings, but not to anything else. I had to 
> > > hard-reset the box. Nothing interesting was saved in 
> > > /var/log/messages. I have the output from vmstat if needed.
> > 
> > That happened to me yesterday while hacking 2.4 and the reason was
> > failed oom detection.  Memory leak?
> 
> I've seen this on 6 diffrent machines (master.kernel.org is one of
> them). I have a fileserver here that hits this all the time, sometimes
> as much as a few times a day.
> 
> If anyone has any ideas or patches for 2.4 I'll happily test them.

I'd like to be able to say "just enable kdb under kernel debugging
and we'll see where it's stuck next time it's stuck".  Unfortunately,
I'm going to have to replace that with "go get the patch from sgi
if there is a current one and figure out how to install it".

Or maybe, "let's mess around with Alt-SysRq and write down funny
numbers on a piece of paper, type them into a file and run ksymoops
on them."  Nope, sorry, life is too short for that.

-- 
Daniel
--
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/

      parent reply	other threads:[~2002-09-06  0:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05 17:23 Steven Cole
2002-09-05 18:03 ` Andrew Morton
2002-09-05 18:22   ` Steven Cole
2002-09-05 19:21     ` Steven Cole
2002-09-05 19:37       ` Andrew Morton
2002-09-06 14:14         ` Steven Cole
2002-09-05 19:15 ` Daniel Phillips
2002-09-05 23:38   ` Martin Josefsson
2002-09-05 23:48     ` Andrew Morton
2002-09-06  0:09       ` Martin Josefsson
2002-09-06  0:02     ` Daniel Phillips [this message]

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=E17n6aP-0006Cw-00@starship \
    --to=phillips@arcor.de \
    --cc=akpm@zip.com.au \
    --cc=elenstev@mesatop.com \
    --cc=gandalf@wlug.westbo.se \
    --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