public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: balance_dirty_pages broken
Date: Thu, 17 Oct 2002 01:41:10 -0400	[thread overview]
Message-ID: <20021017054110.GC10276@redhat.com> (raw)
In-Reply-To: <20021017052246.GB10276@redhat.com>

On Thu, Oct 17, 2002 at 01:22:46AM -0400, Doug Ledford wrote:
> Sure, coming under separate cover.

Actually, this isn't needed now I assume ;-)

> > err.  ramdisk?   initrd? If so, does this fix?
> 
> initrd.  Will try booting without initrd and see if memcounts go back to 
> normal.  On the current setup, when the thing locks up, Shift-ScrollLock 
> dumps the meminfo.  Of interest here is the line right after the 
> Zone:HighMem line which reads:
> 
> ( Active:1634 inactive:1603 dirty:4294966795 writeback:0 free:59222 )
> 
> Booting without initrd solves the lockup issue.  It also clears up the 
> dirty count.  So, initrd is what's corrupting things.  I'll try the patch 
> and let you know if it solves the initrd corruption here in a sec.

Patch solves the problem.  Writes don't hang and Shift-ScrollLock shows a 
reasonable number for dirty now.

-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606
  

  reply	other threads:[~2002-10-17  5:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17  4:36 balance_dirty_pages broken Doug Ledford
2002-10-17  5:09 ` Andrew Morton
2002-10-17  5:22   ` Doug Ledford
2002-10-17  5:41     ` Doug Ledford [this message]
2002-10-17  5:54       ` Andrew Morton
2002-10-17  6:01         ` Doug Ledford
2002-10-17  6:09           ` Andrew Morton

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=20021017054110.GC10276@redhat.com \
    --to=dledford@redhat.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.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