I don't use the -mm from the arch repo, I roll my own, and can tell you that it is fixed for me with -mm2.

good news ... i will check it myself, thanx for info!

]]>https://bbs.archlinux.org/profile.php?id=2452005-05-17T21:16:25Zhttps://bbs.archlinux.org/viewtopic.php?pid=88265#p88265Woo-hoo! Back to the wild side of computing I go...]]>https://bbs.archlinux.org/profile.php?id=26722005-05-17T19:45:10Zhttps://bbs.archlinux.org/viewtopic.php?pid=88259#p88259I don't use the -mm from the arch repo, I roll my own, and can tell you that it is fixed for me with -mm2.]]>https://bbs.archlinux.org/profile.php?id=37092005-05-17T18:51:10Zhttps://bbs.archlinux.org/viewtopic.php?pid=88254#p88254Gullible Jones wrote:

What about 2.6.12-rc4-mm2?

will be up, as soon my cpu is free to compile it (university is more important than arch, sorry) ... if you want to try it, use ABS (my PKGBUILD should work by simply changing rc and mm versions)

if you ask about cachefs and kswapd0: i don't know and as cachefs is not essential to me, i don't want to spend time to know that it is still broken. if someone reports that it is fixed, i can enable cachefs back again ;-)

the cause of this 100% is kswapd0 that do not go idle but stays running. i already posted this to the kernel ML and the devs are investigating the issue. funny, but enabling some minimal debug-options, it seems to solve this issue (i will upload -2 as soon as it is ready solving this mystery)

I had this problem too, but it is fixed in the newer rc's.

yes, because cachefs i disabled for now up untill we know for sure it is fixed

the cause of this 100% is kswapd0 that do not go idle but stays running. i already posted this to the kernel ML and the devs are investigating the issue. funny, but enabling some minimal debug-options, it seems to solve this issue (i will upload -2 as soon as it is ready solving this mystery)

but i don't know how long it is in linux enabled (i only know that i almost always use it because it makes dirsync much faster for NFS shares ;-) )

]]>https://bbs.archlinux.org/profile.php?id=2452005-05-06T20:32:25Zhttps://bbs.archlinux.org/viewtopic.php?pid=86406#p86406What's this cachefs? Is this your standard HD caching in RAM, or is it a new feature?]]>https://bbs.archlinux.org/profile.php?id=26722005-05-06T19:17:56Zhttps://bbs.archlinux.org/viewtopic.php?pid=86380#p86380update:

it's cachefs that is causing kswapd0 this sleepless nights .... therefore i disabled cachefs in rc3-mm3-2 and since then didn't get this issue

]]>https://bbs.archlinux.org/profile.php?id=2452005-05-06T18:06:32Zhttps://bbs.archlinux.org/viewtopic.php?pid=86358#p86358i was wrong: it does not solve this issue, but it makes it appear less frequent (no idea why)

i'm uploading a -2 release of the kernel26mm package that has magic keys enabled. if you see kswapd0 running without idling,press [ALT]-[SysRq]-[p] (SysRq is same as PrtScrn (print screen button) - maybe you will need to go to VC first, if you WM catches such combinations) and then do dmesg and see the last part that was added. if it is different to the one i get here:http://www.ussg.iu.edu/hypermail/linux/ … /0233.htmlfeel free to report to me or directly to the kernel ML to the thread about it to help the devs find out what's happening.

]]>https://bbs.archlinux.org/profile.php?id=2452005-05-02T10:23:45Zhttps://bbs.archlinux.org/viewtopic.php?pid=85386#p85386the cause of this 100% is kswapd0 that do not go idle but stays running. i already posted this to the kernel ML and the devs are investigating the issue. funny, but enabling some minimal debug-options, it seems to solve this issue (i will upload -2 as soon as it is ready solving this mystery)]]>https://bbs.archlinux.org/profile.php?id=2452005-05-02T10:21:14Zhttps://bbs.archlinux.org/viewtopic.php?pid=85385#p85385point it out on the mailing list not here.]]>https://bbs.archlinux.org/profile.php?id=22042005-05-02T03:47:47Zhttps://bbs.archlinux.org/viewtopic.php?pid=85362#p85362I just installed the latest MM kernel, and discovered that, after half an hour of uptime or so, the CPU usage jumps to 100% and refuses to come back down. Listing the running processes shows me that none of them are eating up that much CPU time.

(Yes, I know that the MM kernel isn't stable. I'm just pointing out what I'm guessing is a bug.)