From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Andrew Morton <akpm@osdl.org>
Cc: axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: loop/highmem related 2.4.26 lockup
Date: Sun, 13 Jun 2004 20:38:26 -0300 [thread overview]
Message-ID: <20040613233826.GA5222@logos.cnet> (raw)
In-Reply-To: <20040531151505.54f18f4a.akpm@osdl.org>
On Mon, May 31, 2004 at 03:15:05PM -0700, Andrew Morton wrote:
> Marcelo Tosatti <marcelo.tosatti@cyclades.com> wrote:
> >
> > Proc; loop2
> > >>EIP; e5d145c0 <END_OF_CODE+2597a348/????> <=====
> > Trace; c0189ec8 <journal_alloc_journal_head+18/80>
> > Trace; c0189fa2 <journal_add_journal_head+52/140>
> > Trace; c0107b92 <__down+82/d0>
> > Trace; c0107d2c <__down_failed+8/c>
> > Trace; c01845fe <.text.lock.transaction+4/246>
> > Trace; c018204a <new_handle+4a/70>
> > Trace; c0182114 <journal_start+a4/c0>
> > Trace; c017bc3c <ext3_writepage_trans_blocks+1c/a0>
> > Trace; c01795ec <ext3_prepare_write+24c/260>
> > Trace; c013349e <find_or_create_page+5e/150>
> > Trace; c01d6f84 <lo_send+124/2e0>
> > Trace; c01d7408 <do_bh_filebacked+b8/c0>
> > Trace; c01d7b84 <loop_thread+224/250>
> > Trace; c0109172 <ret_from_fork+6/20>
> > Trace; c01d7960 <loop_thread+0/250>
> > Trace; c010740e <arch_kernel_thread+2e/40>
> > Trace; c01d7960 <loop_thread+0/250>
>
> You've run out of memory and the loop thread is looping in
> journal_alloc_journal_head(), waiting for memory to come free.
>
> Meanwhile, kswapd and bdflush are blocked waiting for I/O which requires
> loop thread services to complete. Deadlock.
>
> A proper fix for this might be fairly complex. A kludgey fix like the
> below might work though.
This didnt seem to make it yet. We applied, and it locked up again after
a few days. I'll get you the traces tomorrow.
I'm running v2.6.7-rc3 on a similar SMP buildbox (with similar heavy
loop usage). Thanks anyway.
> diff -puN fs/jbd/journal.c~a fs/jbd/journal.c
> --- 24/fs/jbd/journal.c~a 2004-05-31 15:12:47.479649360 -0700
> +++ 24-akpm/fs/jbd/journal.c 2004-05-31 15:13:15.908327544 -0700
> @@ -1728,6 +1728,9 @@ static struct journal_head *journal_allo
> while (ret == 0) {
> yield();
> ret = kmem_cache_alloc(journal_head_cache, GFP_NOFS);
> + if (!ret)
> + ret = kmem_cache_alloc(journal_head_cache,
> + GFP_ATOMIC);
> }
> }
> return ret;
> _
next prev parent reply other threads:[~2004-06-13 23:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-31 14:39 loop/highmem related 2.4.26 lockup Marcelo Tosatti
2004-05-31 22:15 ` Andrew Morton
2004-06-13 23:38 ` Marcelo Tosatti [this message]
2004-06-15 1:59 ` Marcelo Tosatti
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=20040613233826.GA5222@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox