From: Valdis.Kletnieks@vt.edu
To: linux-kernel@vger.kernel.org
Subject: Re: scheduler went mad?
Date: Thu, 12 Apr 2001 10:57:08 -0400 [thread overview]
Message-ID: <200104121457.f3CEv8o09656@foo-bar-baz.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]
I've seen the same scenario about 2-3 times a week. kswapd and one or
more processes all CPU bound, totalling to 100%. I've had 'esdplay' hung
on several occasions, and 2-3 times it's been xscreensaver (3.29) hung.
The 'hung' processes are consistently immune to kill -9, even as root, which
indicates to me that they're hung inside a kernel call or something.
Sometimes, something *else* will exit, and everything will 'break loose'
and return to normal after a minute or so.
It *may* not be related, but I also have a lot of this in 'dmesg':
__alloc_pages: 4-order allocation failed.
__alloc_pages: 3-order allocation failed.
i810_audio: DMA overrun on send
There was a recent posting re: the i810_audio driver amounting to "I've got
one bug to fix and then I'll put up a patch" for the 'dma overrun' message.
__alloc_pages doesn't give much information on who its caller was, so
that's somewhat of a dead end...
In page_alloc.c, __alloc_pages() has a 'goto try_again;' which will
cause it to loop around and try to get more memory. I'm wondering if
the "hung" process is entering __alloc_pages(), and gets wedged in the
'try_again' loop - which has a call to wakeup_kswapd() inside it, which
would explain the high context-switch rate. I'm not clear on how kswapd
can end up getting stuck and failing to free up something - unless it ends
up calling __alloc_pages itself indirectly and the PF_MEMALLOC bit isn't
enough to get it the memory it needs, causing a deadlock/loop between
kswapd and __alloc_pages/wakeup_kswapd().
Unfortunately, I've just exhausted my ability to debug this one here.. ;)
I'm running the 2.4.3 kernel, with the following patches:
Reiserfs: 2.4.3-3.6.25.quota.bz2
linux-2.4.3-knfsd-6.g.patch.gz
linux-2.4.3-reiserfs-20010327.patch.bz2
IPv6: linux24-2.4.3-usagi-20010406.patch.gz
Crypto: patch-int-2.4.3.1
am using ReiserFS-on-LVM for basically all filesystems, if that matters...
--
Valdis Kletnieks
Operating Systems Analyst
Virginia Tech
[-- Attachment #2: Type: application/pgp-signature, Size: 211 bytes --]
next reply other threads:[~2001-04-12 14:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 14:57 Valdis.Kletnieks [this message]
2001-04-12 15:12 ` Alan Cox
2001-04-12 15:44 ` Valdis.Kletnieks
2001-04-12 18:31 ` Valdis.Kletnieks
2001-04-12 15:43 ` Hugh Dickins
2001-04-12 16:02 ` Alan Cox
2001-04-12 16:29 ` Rik van Riel
2001-04-12 15:08 ` Marcelo Tosatti
2001-04-12 15:10 ` Marcelo Tosatti
2001-04-12 18:18 ` Szabolcs Szakacsits
2001-04-12 17:56 ` Rik van Riel
2001-04-12 20:12 ` Szabolcs Szakacsits
2001-04-12 20:18 ` Rik van Riel
2001-04-12 23:02 ` Szabolcs Szakacsits
2001-04-12 22:24 ` Valdis.Kletnieks
2001-04-12 16:53 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2001-04-11 14:24 Priit Randla
2001-04-11 18:46 ` Josh McKinney
2001-04-12 15:46 ` Jens Axboe
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=200104121457.f3CEv8o09656@foo-bar-baz.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--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
all inboxes | Powered by JetHome®