hello again, unfortunately i've hit OOM again, this time with "#define DEBUG" enabled in mm/oom_kill.c:
http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.3.txt by "Mar 16 18:32" pppd died again and OOM kicked in 30min later. (there are a *lot* messages of a shell script named "check-route.sh". it's a little script which runs every minute or so to check if my default route is still ok and if ping to the outside world are possible. definitely not a memory hog, but noisy) since tracking the "most memory consuming applications" did not reveal any hints [1], i have monitored /proc/slabinfo and /proc/meminfo this time: http://nerdbynature.de/bits/sheep/2.6.11/oom/daily_stats-2.6.11.3.gz as stated before, i was suspecting pppd to be the bad guy here, and yes: i downgraded pppd to an earlier version and pppd (and the system) survived 2 terminations of my dial-up ISP. yesterday i've upgraded back again to current pppd (debian/unstable) and the OOM problem returned. yes, i'll bug the debian people now (hello!), but grepping for "ppp" in daily_stats-2.6.11.3.gz gives no hits. so "pppd" does not get *any* points from mm/oom_kill.c and thus no attempts are made to kill it (it is always only kill'able with "-9"). furthermore, i thought /proc/slabinfo coud give me some hints about *where* all the memory went in. scrolling down this file to the bottom, where "SwapFree" shows "0 kB" i don't see any alarming numbers in the "slabinfo" right above "meminfo". could someone give me a hint, please? thanks, Christian. [1] http://lkml.org/lkml/2005/3/12/88 more info for this recent OOM issue: http://nerdbynature.de/bits/sheep/2.6.11/oom/dmesg.2.6.11.3 http://nerdbynature.de/bits/sheep/2.6.11/oom/lsmod_2.6.11.3 http://nerdbynature.de/bits/sheep/2.6.11/oom/config-2.6.11.3.gz -- BOFH excuse #62: need to wrap system in aluminum foil to fix problem - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
