Date: Sun, 14 Mar 1999 15:52:30 -0500 From: Jim Durham <durham@w2xo.pgh.pa.us> To: freebsd hackers <freebsd-hackers@FreeBSD.ORG> Subject: VM changes 3.0 to 3.1 RELEASES ? Message-ID: <36EC218E.AD43242B@w2xo.pgh.pa.us>
next in thread | raw e-mail | index | archive | help
I posted this to questions, but got no replies. I am having problems since upgrading from 3.0-SNAP- 981225 to 3.0 and 3.1 RELEASES. The machine is very modest, a 5X86, 40 mb of RAM and 1.5 gb of disk, 75 mb of swap. It is a firewall for a small LAN and also runs apache and RealAudio servers as well as an amateur radio ax.25 networking userland process. It also runs X on the console with Netscape 4.5 used a lot and uses ghostscript/apsfilter for printing, both of which are resource hogs. The worst symptom is natd either core-dumping or getting into a state where it is using about 95% of the CPU and network throughput is almost zero. I began to recompile natd and the alias library with symbolsto run a core dump trace with gdb, when I realized that sendmail and inetd were also having problems (core dumps, eating CPU cycles). During these episodes, I noticed that swap space was down to a few mb. When 3.1 came out, I upgraded and things are much better, but ghostscript/apsfilter has gone into the CPU-cycle-eating mode twice on a big print job. natd , sendmail and inetd have had no problems on 3.1 . I have spoken to several people who had the problem with natd. The stack trace showed that it was trying to execute the address of the packet buffer as a function from the alias stuff. It was hopelessly confused, apparently. I didn't get to do any tracing on sendmail or inetd. I also saw the "pointer too low to make sense" error message. I have searched through RELNOTES, etc and can't find any mention of any VM changes from 3.0 to 3.1. Can anyone shed any light on this? Is this something that is being worked on? Should I upgrade to -STABLE? What was suspicious to me was that the old 3.0-SNAP never showed these problems and , I believe, shut down processes gracefully when system resources became scarce. -- Thanks, Jim Durham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36EC218E.AD43242B>