https://bugzilla.novell.com/show_bug.cgi?id=211860 Summary: keep display alive after oom Product: openSUSE 10.2 Version: Alpha 5 Platform: PowerPC OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers@suse.de ReportedBy: olh@novell.com QAContact: jsrain@novell.com the kernel tends to kill processes that dont behave and use too much memory. see bug #209424 Unfortunatelty, the kernel kills also Xorg, which can not restore the graphics card state. If Xorg is killed, the system appears to be frozen. echo -n '-17' > /proc/$XORG_PID/oom_adj In theory the line above should keep X alive, bug #211859 talks about the practice. Either way, the yast startup scripts in the inst-sys have to make sure that Xorg is not killed. Documentation/filesystems/proc.txt: ... 2.12 /proc/<pid>/oom_adj - Adjust the oom-killer score ------------------------------------------------------ This file can be used to adjust the score used to select which processes should be killed in an out-of-memory situation. Giving it a high score will increase the likelihood of this process being killed by the oom-killer. Valid values are in the range -16 to +15, plus the special value -17, which disables oom-killing altogether for this process. 2.13 /proc/<pid>/oom_score - Display current oom-killer score ------------------------------------------------------------- ------------------------------------------------------------------------------ This file can be used to check the current score used by the oom-killer is for any given <pid>. Use it together with /proc/<pid>/oom_adj to tune which process should be killed in an out-of-memory situation. .. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.