Ok I've narrowed down my problem with the SF tree's 2.4.18 kernel and with the OSS 2.4.18 tree (tag linux_2_4, from about 3 weeks ago). I'm running on an NEC Osprey board. I've confirmed that XIP in ROM isn't causing this problem. I have a module that kmallocs almost all of the free memory in the system on insmod, and kfrees the memory on rmmod. Then, when I try to run a program that needs a lot of memory it page faults somewhere in the __wake_up function trying to wake up kswapd. kswapd actually does wake up and runs after the page fault, but doesn't find any slabs to reap. In my working kernel with all the slab debug stuff turned on, I'll see that slabs from the 131072 slab size (my kmallocs were 90000 bytes each) will get reaped as needed. This doesn't happen with the SF kernel. In fact, kmem_cache_reap gets to the comment that says /* couldn't find anything to reap */ I don't know if it isn't finding anything because of the page fault in __wake_up (which oddly enough doesn't crash the system..it just kills the process that was running, ie the memory hog) My working kernel is the 2.4.0-test9 kernel that Brad did a lot of work on. I really would like to get the later and greater kernel up and running. If anybody can offer some advice please let me know. I figure I'll figure this problem out before messing with the execve problem in the OSS 2.5.2 and 2.4.19 kernel since for all I know if I get those booting I'll run into this problem here. :) If anybody can point me in the right direction I'd appreciate it. Steve ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Got root? We do. http://thinkgeek.com/sf _______________________________________________ Linux-mips-kernel mailing list Linux-mips-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-mips-kernel
