On Thu, 16 Aug 2001, Justin A wrote:
> case 'f': /* F -- oom handlder _f_ree memory */
> printk("Run OOM Handler\n");
> oom_kill();
> break;
This causes a nasty ass BUG() to get asserted. I can trigger the OOM
killer normally, but if I trigger it using SysRq, it'll complain rather
loudly and kill the interrupt handler. It appears to kill the proper
process first, however.
If I get some time later on, I'll boot up my devel machine at home and get
this thing all squared away. It looks as though some sort of lock or
something is being held when it shouldnt be, and it's causing Bad
Things(tm) to happen. Either way, I'll figure it out at home (or when I
get back from vacation on Monday).
LMK what you think.
Kelsey Hudson khudson@ctica.com
Software Engineer
Compendium Technologies, Inc (619) 725-0771
---------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 21:00:20 EST