It applied cleanly with no mods needed and had been running fine untill this
decided to happen. Seems like slocate's updatedb decided to jack the load up
which triggered oom? However, the chosen process was unkillable since its the
same process listed in the oom report over and over again?
--- William Lee Irwin III <firstname.lastname@example.org> wrote:
> On Tue, May 21, 2002 at 12:43:49PM -0700, Erik McKee wrote:
> > Hello
> > This output...
> > kernel BUG at /usr/src/linux-2.2.13/include/linux/mm_inline.h:78!
> Can I see the patch you used to merge preempt?
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/