All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, ak@suse.de, axboe@suse.de
Subject: Re: Hang on x86-64, 2.6.9-rc3-bk4
Date: Sun, 17 Oct 2004 09:31:09 -0400	[thread overview]
Message-ID: <4172741D.1090800@pobox.com> (raw)
In-Reply-To: <20041016182116.33b3b788.akpm@osdl.org>

Andrew Morton wrote:
> Jeff Garzik <jgarzik@pobox.com> wrote:
> 
>>>Can we get a sysrq-M dump from that machine please?
>>
>> alas, for the 'hang' case, my during-initscripts console is going to 
>> strange place.  here's sysrq-m from 2.6.9-rc3-bk4 with the mm/vmscan.c 
>> patch reverted (the its-fixed version).
> 
> 
> Is cool - I was wondering if you had the same funny NUMA zone layout.  You
> do not.
> 
> So there's some new non-terminating condition in there.  It's definitely
> the case that we're still failing to throttle kswapd as we should be doing,
> but I left it as-is due to lack of reported problems (hah) and because the
> fix does cause less reclaim via kswapd and more reclaim via direct reclaim.
> 
> Still.  The relevant patches, in order, are at
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.9-rc4/2.6.9-rc4-mm1/broken-out:
> 
> vmscan-total_scanned-fix.patch
> revert-vm-no-wild-kswapd.patch
> balance_pgdat-cleanup.patch
> no-wild-kswapd-2.patch
> no-wild-kswapd-kswapd-continue.patch
> 
> I expect the first one will fix this up.   Can you confirm?


FWIW, I verified that "vmscan-total_scanned-fix.patch" fixes the hang on 
both 2.6.9-rc3-bk4 and 2.6.9-final.

	Jeff



  parent reply	other threads:[~2004-10-17 13:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-16 21:40 Hang on x86-64, 2.6.9-rc3-bk4 Jeff Garzik
2004-10-16 21:46 ` Jeff Garzik
2004-10-16 22:48   ` Andrew Morton
2004-10-16 23:43     ` Jeff Garzik
2004-10-17  0:14       ` Andrew Morton
2004-10-17  0:25         ` Jeff Garzik
2004-10-17  0:28           ` Andrew Morton
2004-10-17  0:51         ` Jeff Garzik
2004-10-17  1:21           ` Andrew Morton
2004-10-17  3:39             ` Jeff Garzik
2004-10-17  5:46               ` Nick Piggin
2004-10-17 13:30                 ` Jeff Garzik
2004-10-17 13:49                   ` Nick Piggin
2004-10-17 14:00                     ` Jeff Garzik
2004-10-17 14:19                       ` Nick Piggin
2004-10-17 13:31             ` Jeff Garzik [this message]
2004-10-17  1:24           ` Nick Piggin
2004-10-17  2:16             ` Jeff Garzik
2004-10-17  2:19               ` Nick Piggin
2004-10-17  2:31                 ` Nick Piggin
2004-10-17  3:10                   ` Jeff Garzik
2004-10-17  3:20                     ` Nick Piggin
2004-10-17  3:05                 ` Jeff Garzik
2004-10-17  3:07                   ` Nick Piggin
2004-10-17  3:13                     ` Jeff Garzik
2004-10-18 18:45               ` Jeff Garzik

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=4172741D.1090800@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --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 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.