Re: Linux behaviour in low memory situations.

Linus Torvalds (torvalds@transmeta.com)
19 Jul 1998 20:30:56 GMT

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Donald Chan: "ensoniq 1370 soundcard compiling probs."
Previous message: Martin Mares: "Re: 2.1.109+l-con90 breaks my APM blanking"
Maybe in reply to: Marc Lehmann: "Linux behaviour in low memory situations."

In article <19980719213937.08230@cerebro.laendle>,
Marc Lehmann <pcg@goof.com> wrote:
>I can remember sometime in the 80's or 90's (2.1.8x/9x), linux just killed a
>more-or-less random process when there was no memory left. That, while
>sometimes sub-optimal (the X-server), saved me from a long filesystem check.
>
>All the newer kernels, though, just _stop_ (not even sysrq works) without an
>oops, when there is no memory left (all 2.1.10x for example). Increasing
>sys/vm/freepages does not help at all..

Please tell me more about what you're doing.. I certainly see different
behaviour (but again, because of mm changes in 2.1.109, please use that
and tell me how you make it stop, along with info on what kind of swap
situation you have etc).

Linus

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html

Next message: Donald Chan: "ensoniq 1370 soundcard compiling probs."
Previous message: Martin Mares: "Re: 2.1.109+l-con90 breaks my APM blanking"
Maybe in reply to: Marc Lehmann: "Linux behaviour in low memory situations."