Re: [PATCH] oom killer (Core)

[Thomas Gleixner]

On Thu, 2004-12-02 at 11:22 -0800, Andrew Morton wrote:
> Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:
> >
> > On Thu, 2004-12-02 at 11:07 -0800, Andrew Morton wrote:
> > > Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:
> > > >
> > > > FYI, I tried with 2.6 UP and PREEMPT=n. The result is more horrible. The
> > > > box just gets stuck in an endless swap in/swap out and does not respond
> > > > to anything else than SysRq-T and the reset button.
> > > 
> > > There's a patch in -mm which causes the oom-killer to be invoked each time
> > > you hit sysrq-F, which sounds like a fine idea to me.
> > 
> > Can you please explain, how I can hit sysrq-F when I can't log into the
> > remote machine ?
> > 
> 
> umm, in the same way you're using "SysRq-T and the reset button"?
> 
> You can issue sysrq commands over serial consoles too.

I know, but the console and the reset button are 150km away. When I dial
into the machine or try to connect via the network, I cannot connect
with the current kernels. Neither 2.4, because the fork fails, nor 2.6
because oom killed sshd. So I cannot send anything except a service man,
who drives 150km to hit sysrq-F or the reset button.

If this happens the kernel just should make sure to make the machine
accessible and let me repair the problem. Nothing else.

tglx


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/