From: Andrew Morton <akpm@zip.com.au>
To: FORT David <popo.enlighted@free.fr>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.16 deadlock in kswapd
Date: Mon, 17 Dec 2001 09:23:37 -0800 [thread overview]
Message-ID: <3C1E2A19.BC654FF0@zip.com.au> (raw)
In-Reply-To: <3C1DF93E.80907@free.fr>
FORT David wrote:
>
> Hi,
> today i was transfering some files between two drives(reiserfs->ext3) and
> suddenly everything locked up. I sys-rqed to show the executed IP and
> every five times i've tryed it was showing the following stack trace:
>
> ...
>
> >>EIP; c0111657 <flush_tlb_others+e7/110> <=====
> Trace; c01117b5 <flush_tlb_page+75/80>
> Trace; c012f052 <swap_out+312/4b0>
> ...
Dodgy hardware, I'm afraid - it looks like a cross-CPU interrupt
was sent but not received. Not uncommon.
> The interesting thing is that i don't have any swap, so i'm really
> interested
> in knowing why kswapd is envolved here.
Look at the swapout code: it calls flush_tlb_page() in preparation
for swapping a page out. It then tries to allocate swap space,
finds there is none and bales out. This can comsume quite a lot
of CPU under some circumstances.
-
next prev parent reply other threads:[~2001-12-17 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 13:55 2.4.16 deadlock in kswapd FORT David
2001-12-17 17:23 ` Andrew Morton [this message]
2001-12-18 15:13 ` Alan Cox
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=3C1E2A19.BC654FF0@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=popo.enlighted@free.fr \
/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