From: Nick Piggin <nickpiggin@yahoo.com.au>
To: lista4@comhem.se
Cc: mr@ramendik.ru, linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc3: kswapd eats CPU on start of memory-eating task
Date: Thu, 16 Dec 2004 19:03:45 +1100 [thread overview]
Message-ID: <41C14161.7020300@yahoo.com.au> (raw)
In-Reply-To: <14380712.1103150975468.JavaMail.tomcat@pne-ps3-sn1>
Voluspa wrote:
> Earlier today I wrote:
>
>
>>I find no problem when blender is the sole (large) application, but when a
>>distributed computing client is running in the background the reported
>
> problems
>
>>surface. I use http://folding.stanford.edu for protein folding. It runs
>>with a default of nice 19 and sucks up every free CPU cycle. I've never
>>seen it interfere with anything prior to this swap issue - been running
>>it since 2000.
>
>
> More testing done to find the breaking point. Running the folding client and
> blender:
>
> 2.6.8.1-bk2 is the last kernel without _any_ swapping problem (no screen freezes
> etc)
> |
> | 2.6.9-rc1 and three -bk forward have oopses and loss of keyboard in X.
> Can't test them.
> |
> 2.6.9-rc1-bk4 is the first functional kernel where the freezes show up.
>
> So it is a real regression.
>
Can you turn on magic sysrq in the kernel hacking menu, and press
alt+sysrq+m a few times while kswapd is using lots of memory, please?
Then run `dmesg -s 1000000 > dmesg.out`, and send the dmesg over,
please?
Thanks,
Nick
next prev parent reply other threads:[~2004-12-16 8:03 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 22:49 2.6.10-rc3: kswapd eats CPU on start of memory-eating task Voluspa
2004-12-16 8:03 ` Nick Piggin [this message]
2004-12-16 8:14 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2004-12-23 0:26 Zou, Nanhai
2004-12-23 13:26 ` Rik van Riel
2004-12-23 13:28 ` Rik van Riel
2004-12-22 8:45 Zou, Nanhai
2004-12-22 14:23 ` Rik van Riel
2004-12-20 12:59 Voluspa
2004-12-21 1:46 ` Mikhail Ramendik
2004-12-20 9:22 Zou, Nanhai
2004-12-20 15:08 ` Rik van Riel
2004-12-20 6:51 Voluspa
2004-12-20 7:12 ` Andrew Morton
2004-12-20 7:44 ` Nick Piggin
2004-12-20 8:03 ` Con Kolivas
2004-12-20 8:58 ` Con Kolivas
2004-12-20 12:55 ` Andrea Arcangeli
2004-12-20 12:06 ` Ed Tomlinson
2004-12-20 12:29 ` Con Kolivas
2004-12-20 17:49 ` Hideo AOKI
2004-12-20 23:51 ` Nick Piggin
2004-12-20 9:07 ` mr
2004-12-20 15:06 ` Rik van Riel
2004-12-19 23:12 Voluspa
2004-12-19 22:40 Voluspa
2004-12-19 22:56 ` Nick Piggin
2004-12-19 23:08 ` Mikhail Ramendik
2004-12-19 23:57 ` Andrew Morton
2004-12-20 0:03 ` Mikhail Ramendik
2004-12-20 3:02 ` Con Kolivas
2004-12-20 3:21 ` Rik van Riel
2004-12-20 4:13 ` Con Kolivas
2004-12-20 4:18 ` Rik van Riel
2004-12-20 4:21 ` Con Kolivas
2004-12-20 4:33 ` Nick Piggin
2004-12-20 7:07 ` Andrew Morton
2004-12-19 14:08 Voluspa
2004-12-17 10:45 Voluspa
2004-12-18 23:02 ` Con Kolivas
2004-12-15 14:02 Voluspa
2004-12-17 0:41 ` Andrew Morton
2004-12-14 7:24 Voluspa
2004-12-12 14:28 Mikhail Ramendik
2004-12-14 0:51 ` Nick Piggin
2004-12-14 2:28 ` Mikhail Ramendik
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=41C14161.7020300@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lista4@comhem.se \
--cc=mr@ramendik.ru \
/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