Kernel 2.4.18 and strange OOM Killer behaveness
Hi there,
i just opened an 800mb movie file with pico/nano, waited for the OOM, and here it is, have a look:
Apr 26 16:10:45 codeman kernel: Out of Memory: Killed process 19789 (apache). Apr 26 16:10:46 codeman kernel: Out of Memory: Killed process 27828 (apache). Apr 26 16:10:48 codeman kernel: Out of Memory: Killed process 14554 (apache). Apr 26 16:10:50 codeman kernel: Out of Memory: Killed process 19893 (apache). Apr 26 16:10:52 codeman kernel: Out of Memory: Killed process 32036 (apache). Apr 26 16:10:54 codeman kernel: Out of Memory: Killed process 8370 (apache). Apr 26 16:10:56 codeman kernel: Out of Memory: Killed process 680 (mysqld). Apr 26 16:10:56 codeman kernel: Out of Memory: Killed process 7638 (mysqld). Apr 26 16:10:56 codeman kernel: Out of Memory: Killed process 26780 (mysqld). Apr 26 16:10:56 codeman kernel: Out of Memory: Killed process 26038 (mysqld). Apr 26 16:11:01 codeman kernel: Out of Memory: Killed process 3914 (pico). Apr 26 16:11:01 codeman kernel: VM: killing process pico Apr 26 16:11:04 codeman kernel: Out of Memory: Killed process 20471 (squid).
So, you guess, apache, mysqld, squid and the causer pico are killed, but NO, ONLY, and i mean ONLY pico was killed, all the other Processes listed above are running fine, accepting connections, short: works fine!!
And yes, its reproduceable !!
The above is a kernel without rmap!
I also tried this with rmap enabled kernel, no OOM Messages appears, but the system freezes. It does NOT accept any input on keyboard, mouse or via the network (e.g ping, traceroute, telnet to smtp port etc.). Also, if the system does not accept any input, the harddisk is doing something, i've waited ~ 45 minutes, system was still not accepting anything, harddisk was doing anything. This was rmap12h with 2.4.18.
Kinda strange, isn't it?! :-)
I like it, cause only the causer get killed, but why those syslog messages?! Syslogd lies like a trooper ;)
Signature · 8 lines
Kind regards Marc-Christian Petersen http://sourceforge.net/projects/wolk PGP/GnuPG Key: 1024D/569DE2E3DB441A16 Fingerprint: 3469 0CF8 CA7E 0042 7824 080A 569D E2E3 DB44 1A16 Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.
Quoted 6 lines · On Fri, 26 Apr 2002 16:38:08 +0200 Marc-Christian Petersen…
I also tried this with rmap enabled kernel, no OOM Messages appears, but the system freezes. It does NOT accept any input on keyboard, mouse or via the network (e.g ping, traceroute, telnet to smtp port etc.). Also, if the system does not accept any input, the harddisk is doing something, i've waited ~ 45 minutes, system was still not accepting anything, harddisk was doing anything. This was rmap12h with 2.4.18.
I guess it should be better to OOM here...?
Quoted 14 lines
Signature · 13 lines
Kind regards Marc-Christian Petersen http://sourceforge.net/projects/wolk PGP/GnuPG Key: 1024D/569DE2E3DB441A16 Fingerprint: 3469 0CF8 CA7E 0042 7824 080A 569D E2E3 DB44 1A16 Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. - 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/
Quoted 3 lines
So, you guess, apache, mysqld, squid and the causer pico are killed, but NO, ONLY, and i mean ONLY pico was killed, all the other Processes listed above are running fine, accepting connections, short: works fine!!
I'm probably talking nonsense here, but apache, mysql and squid; all of them run there services with several processes. Could it be that the OOM Killer only killed a couple of childs and not the parent of them all?
Signature · 1 line
Alvaro Figueroa