From: Javier Marcet <jmarcet@pobox.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Nuno Monteiro <nuno@itsari.org>,
linux-kernel@vger.kernel.org, andrew@sol-1.demon.co.uk,
jamagallon@able.es, khromy@lnuxlab.ath.cx, conman@kolivas.net
Subject: Re: Exaggerated swap usage
Date: Mon, 2 Dec 2002 05:55:12 +0100 [thread overview]
Message-ID: <20021202045512.GA2479@jerry.marcet.dyndns.org> (raw)
In-Reply-To: <20021202002108.GQ28164@dualathlon.random>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
* Andrea Arcangeli <andrea@suse.de> [021202 01:24]:
>> Pid: 2, comm: keventd
>> EIP: 0010:[<c0142ae3>] CPU: 0 EFLAGS: 00000206 Not tainted
>> EAX: c10ec45c EBX: 00000033 ECX: c11f8838 EDX: 40000000
>> ESI: c2fed680 EDI: c10ec400 EBP: 00000033 DS: 0018 ES: 0018
>[..]
>> >>EIP; c0142ae3 <try_to_sync_unused_inodes+1f/1f8> <=====
>> >>EAX; c10ec45c <_end+e521e4/13c9de8>
>> >>ECX; c11f8838 <_end+f5e5c0/13c9de8>
>> >>ESI; c2fed680 <[sb].data.end+a7ffd/25a9dd>
>> >>EDI; c10ec400 <_end+e52188/13c9de8>
>> Trace; c0117114 <__run_task_queue+4c/60>
>> Trace; c011e0e9 <context_thread+11d/19c>
>> Trace; c010588c <kernel_thread+28/38>
>ok, now it's clear what the problem is. there are inuse-dirty inodes
>that triggers a deadlock in the schedule-capable
>Can you give a spin to this untested incremental fix?
This appears to do the trick. I've tried some tests which always locked
it up before and now it's still rock stable.
It's also the 2.4 kernel which works more smoothly here, under heavy io
et all. Not yet 100% as well as 2.5 but quite near.
Very good work :)
Thanks for fixing the damn bug.
--
Javier Marcet <jmarcet@pobox.com>
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2002-12-02 4:47 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 11:54 Javier Marcet
2002-11-29 12:20 ` Christer Nilsson
2002-11-29 16:31 ` Rik van Riel
2002-11-30 1:38 ` Javier Marcet
2002-11-30 1:55 ` Rik van Riel
2002-11-30 2:47 ` Zwane Mwaikambo
2002-11-30 5:17 ` Javier Marcet
2002-11-30 14:02 ` Exaggerated swap usage && -aa lockup Javier Marcet
2002-11-30 2:42 ` Exaggerated swap usage Zwane Mwaikambo
2002-11-30 3:02 ` Andrew Morton
2002-11-30 4:12 ` Zwane Mwaikambo
2002-11-30 6:48 ` khromy
2002-11-30 6:49 ` Javier Marcet
2002-11-30 7:08 ` Dmitri
2002-11-30 14:05 ` Javier Marcet
2002-11-30 18:23 ` khromy
2002-11-30 18:43 ` Andrea Arcangeli
2002-12-01 7:39 ` Javier Marcet
2002-12-01 7:53 ` Javier Marcet
2002-12-01 10:34 ` Andrea Arcangeli
2002-12-01 7:59 ` Javier Marcet
2002-12-01 10:36 ` Andrea Arcangeli
2002-12-01 14:37 ` Nuno Monteiro
2002-12-02 0:21 ` Andrea Arcangeli
2002-12-02 1:01 ` Nuno Monteiro
2002-12-02 4:55 ` Javier Marcet [this message]
2002-12-02 21:24 ` Andrew Clayton
2002-11-30 14:05 ` Steffen Moser
2002-11-30 18:22 ` Rik van Riel
2002-12-01 7:57 ` Javier Marcet
2002-12-01 19:27 ` Rik van Riel
2002-11-29 15:28 Randal, Phil
2002-11-29 16:28 ` Rik van Riel
2002-12-02 23:59 Marc-Christian Petersen
2002-12-03 0:59 ` Andrea Arcangeli
2002-12-03 10:13 ` Marc-Christian Petersen
2002-12-03 13:59 ` Andrea Arcangeli
2002-12-03 18:43 ` Marc-Christian Petersen
2002-12-05 23:14 ` Marc-Christian Petersen
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=20021202045512.GA2479@jerry.marcet.dyndns.org \
--to=jmarcet@pobox.com \
--cc=andrea@suse.de \
--cc=andrew@sol-1.demon.co.uk \
--cc=conman@kolivas.net \
--cc=jamagallon@able.es \
--cc=khromy@lnuxlab.ath.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno@itsari.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
all inboxes | Powered by JetHome®