https://bugzilla.novell.com/show_bug.cgi?id=253968 npiggin@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrea@novell.com ------- Comment #10 from npiggin@novell.com 2007-03-29 20:45 MST ------- So it looks like the correct process does get targetted for OOM-kill, however for some reason the system isn't recovering afterwards. Andrea is looking at a similar problem, and it can get quite difficult if network filesystems are involved, but it sounds like you're just running on local filesystems, which should be much less prone to deadlock. Can you get a sysrq+t trace after the OOM killer gets invoked, and the system gets stuck? -- 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.