Hi, I find my SuSe 9.2 installation hangs when I run an application that uses lots of memory. examples are: 1. Kooka and OCR on a large scan file 2. Digikam with several photos open with many photos then run a print job Is there some switch or parameter that I can set to have the Kernel kill the last started process when it runs out of RAM and SWAP space? Does it display a message like "Insufficient memory trying to run application XXXXXX " ? Thanks, -- Bruce Samhaber Senior Hardware Design Consultant Tel: 613-724-5987 112 Kenora St. Fax: 613-724-5987 Ottawa, Ontario Cel: 613-297-6961 K1Y 3L1 mailto: bsamhaber@sympatico.ca http://www3.sympatico.ca/marypat/
On Friday 15 April 2005 05:05, Bruce Samhaber wrote:
Hi,
I find my SuSe 9.2 installation hangs when I run an application that uses lots of memory.
examples are:
1. Kooka and OCR on a large scan file
2. Digikam with several photos open with many photos then run a print job
Is there some switch or parameter that I can set to have the Kernel kill the last started process when it runs out of RAM and SWAP space? Does it display a message like "Insufficient memory trying to run application XXXXXX " ?
You could try turning off memory overcommitting. echo "2" > /proc/sys/vm/overcommit_memory This will force the system to return an out of memory error when a process tries to allocate memory the system doesn't have
Anders: El Jue 14 Abr 2005 22:17, Anders Johansson escribió:
You could try turning off memory overcommitting.
echo "2" > /proc/sys/vm/overcommit_memory
This will force the system to return an out of memory error when a process tries to allocate memory the system doesn't have
Since my last kernel update (2.4.20-131 on 8.2, installed 2005-03-26) I have been experimenting almost daily system hangs during high memory commitment. One week ago I did as you recommended to Bruce and my current system uptime is 7 days. Thank you very much for your helpful advice, I would never have found out on my own. -- Andreas Philipp Noema Ltda. Bogotá, D.C. - Colombia http://www.noemasol.com
On Thursday 21 April 2005 03:12 pm, Andreas Philipp wrote:
Anders:
El Jue 14 Abr 2005 22:17, Anders Johansson escribió:
You could try turning off memory overcommitting.
echo "2" > /proc/sys/vm/overcommit_memory
This will force the system to return an out of memory error when a process tries to allocate memory the system doesn't have
Since my last kernel update (2.4.20-131 on 8.2, installed 2005-03-26) I have been experimenting almost daily system hangs during high memory commitment. One week ago I did as you recommended to Bruce and my current system uptime is 7 days.
Thank you very much for your helpful advice, I would never have found out on my own. -- Dear Andreas ,
I would also suggest that you test your physical memory using the memory testing app that is shipped on your SUSE install CD or DVD called MEMTEST86. Shutdown the sys and boot from CD or DVD 1 and choose MEMTEST. You may have to let it run several hours. MEMTEST had found bad memory for me many times and the vendors trust it's reports. PeterB -- -- Proud to use SuSE Linux, since 5.2 Loving using SuSE Linux 9.1 MyBlog http://vancampen.org/blog/ Currently listening to Joseph Campbell http://www.jcf.org/ Free D/Ls after free registration --
Peter, El Jue 21 Abr 2005 16:14, Peter B Van Campen escribió:
I would also suggest that you test your physical memory using the memory testing app that is shipped on your SUSE install CD or DVD called MEMTEST86.
Thanks for your tip. I did check my memory after the first hangs, but I didn't get any errors. I was cluelessly googling around until I came across Anders' post from last week. Hopefully this did the job ... no hangs for the last seven days. Best regards, -- Andreas Philipp Noema Ltda. Bogotá, D.C. - Colombia http://www.noemasol.com
Hi, You probably want put it to /etc/sysctl.conf file, vm.overcommit_memory = 2 if you only leave it in /proc, the reboot will take it away, and you have to manually do it again. Hope this help. Lisa Andreas Philipp wrote:
Peter,
El Jue 21 Abr 2005 16:14, Peter B Van Campen escribió:
I would also suggest that you test your physical memory using the memory testing app that is shipped on your SUSE install CD or DVD called MEMTEST86.
Thanks for your tip. I did check my memory after the first hangs, but I didn't get any errors. I was cluelessly googling around until I came across Anders' post from last week. Hopefully this did the job ... no hangs for the last seven days.
Best regards,
Lisa, El Jue 21 Abr 2005 16:42, Lisa Dong escribió:
You probably want put it to /etc/sysctl.conf file,
vm.overcommit_memory = 2
Thanks, that sounds like a good idea :-) I didn't find /etc/sysctl.conf, but there is a /etc/sysconfig/sysctl file. Should I create /etc/sysctl.conf or does it go into /etc/sysconf/sysctl ? Best regards, -- Andreas Philipp Noema Ltda. Bogotá, D.C. - Colombia http://www.noemasol.com
'man sysctl' states the configuration file is /etc/sysctl.con. you can create the file. please correct me if I am wrong. Lisa Andreas Philipp wrote:
Lisa,
El Jue 21 Abr 2005 16:42, Lisa Dong escribió:
You probably want put it to /etc/sysctl.conf file,
vm.overcommit_memory = 2
Thanks, that sounds like a good idea :-) I didn't find /etc/sysctl.conf, but there is a /etc/sysconfig/sysctl file. Should I create /etc/sysctl.conf or does it go into /etc/sysconf/sysctl ?
Best regards,
El Jue 21 Abr 2005 17:28, Lisa Dong escribió:
'man sysctl' states the configuration file is /etc/sysctl.con. you can create the file.
Thanks both Lisa and Anders for your advice. Regards, -- Andreas Philipp Noema Ltda. Bogotá, D.C. - Colombia http://www.noemasol.com
On Thursday 21 April 2005 22:12, Andreas Philipp wrote:
Anders:
El Jue 14 Abr 2005 22:17, Anders Johansson escribió:
You could try turning off memory overcommitting.
echo "2" > /proc/sys/vm/overcommit_memory
This will force the system to return an out of memory error when a process tries to allocate memory the system doesn't have
Since my last kernel update (2.4.20-131 on 8.2, installed 2005-03-26) I have been experimenting almost daily system hangs during high memory commitment. One week ago I did as you recommended to Bruce and my current system uptime is 7 days.
Thank you very much for your helpful advice, I would never have found out on my own.
No problem, glad to help. And yes, Lisa's suggestion to put it in sysctl.conf is a good idea, when you're sure you want to keep it across reboots Just create /etc/sysctl.conf and put it in there /etc/sysconfig/sysctl can override some settings in /etc/sysctl.conf, but only the ones it already mentions. The scripts in /etc/init.d reads it and for those specific settings it can override, but if you want to add another setting, you need to create sysctl.conf
participants (5)
-
Anders Johansson -
Andreas Philipp -
Bruce Samhaber -
Lisa Dong -
Peter B Van Campen