![]() | |||||||||||||
Messages in this thread |
On Sunday 23 February 2003 21:18, Rik van Riel wrote: Hi Rik, > It'd be interesting to know where these processes are spending > their CPU time and why they're not catching their signals. I'll look into it again when I do the next run. > > Sysrq-i gave me the chance to get out of the OOM killing process and > > only kernel threads were left + getty's so I was able to log in again. > Strange, so sysrq-i manages to kill the processes, but the OOM > killer doesn't kill the processes ? yep, so it is. > This is very suspect because the OOM killer uses force_sig in > the same way the sysrq-i handler does... indeed. Well, sysrq-i need about 5 seconds to give me my getty back. Anyway, your patch should go into -BK. Your patch does _not_ introduce this behaviour, it's present even w/o your patch but your approach makes things better :) ciao, Marc - 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/ | ||||||||||||
| Last update: 2005-03-22 13:33 [from the cache] ©2003-2008 | |||||||||||||