On Wed, Feb 15, 2006 at 01:09:33PM -0800, Anthony Brock wrote:
> I'm assuming that the segmentation fault was due to the same bug we
> were trying to fix by upgrading to the bs2 patches. We really don't
> have any development servers with a heavy load. *sigh*
For the segfaults, the fpregs patch might help if it's not already in
-bs2. It's at
http://user-mode-linux.sourceforge.net/work/current/2.6/2.6.16-rc2/patches/tcsh
Also, this is x86_64, correct? If so, try
echo 0 > /proc/sys/kernel/vsyscall64
This makes the host's vsyscall area unavailable to UML processes.
This has had mixed results for me - the tcsh thing which I chased
(and which resulted in the patch above) stopped segfaulting on i386,
but still segfaulted on x86_64, and I tracked it down to a UML process
using the host's vsyscall area. Turning that off converts the
segfaults into SIGUSR1 deaths for reasons unknown. The process still
dies, but not from a segfault.
As for the OOM cases, the data that BB asked for would still be
helpful in diagnosing them.
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
User-mode-linux-user mailing list
User-mode-linux-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
