> > ah, right.  may i suggest adding MALLOC_DEBUG and KMEMSTATS to that
> > kernel so that you can see more accurately where the memory is being
> > consumed?
>
>well, it died _again_.  Nothing exciting in dmesg after the above
>kernel options were put in:

it died?  do you have a crash dump?  i would expect those options to
cause the kernel to consume some memory by keeping tracking of
statistics and usage patterns, etc, not to print things into the
message buffer.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
werdna@squooshy.com       * "information is power -- share the wealth."