Date: Sun, 12 Jul 1998 06:21:52 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: archer@lucky.net (Alexander Litvin) Cc: current@FreeBSD.ORG Subject: Re: Arrgh ! resubscribing again again again.... Message-ID: <199807120621.XAA29796@usr07.primenet.com> In-Reply-To: <199807120536.IAA07205@grape.carrier.kiev.ua> from "Alexander Litvin" at Jul 12, 98 08:36:31 am
next in thread | previous in thread | raw e-mail | index | archive | help
> TL> You don't *have* to do that. You *could* shutdown your X server and > TL> restart it. You simply choose to have your demons die, instead of > TL> doing this and/or limiting the amount of VM available to the X server > TL> and Netscape, or disabling the X shm extensions. > > Terry, your explanation is ok. But what X-server should I shutdown? > For I don't have any X's. And yesterday I repeated 'make -j64 buildworld', > and as always: sendmail childs die with SIGSEGV, cron seems to be in > memory, but no cron jobs run. And all that after makeworld has finished, > system is _absolutely_ idle. Interesting. Clearly, you're not the person running Netscape to cause a similar problem. 8-). Do you have any zombie processes? Have you looked at the vmstat output? If you kill -HUP cron, what happens? If you kill -HUP sendmail, what happens? Did you get any errors in the buildworld, or did it complete without damaging itself (only damaging sendmail and cron)? Are you overclocking your CPU? How much memory do you have -- is it enough that if you missed a refresh cycle or two (say, because you did something silly, like a buildworld with -j64 and you have an Adaptec controller with a high bus-on time, or you are using a PIO IDE controller, etc...), that the upper memory contents might degrade and cause these problems? Does -j32 have the same problem? -j16? etc.? It would be nice to know if this problem was the result of running out of VM, or if you can cause it by load without actually exhasting the VM... Makeworld takes a while; have you tried putting a crontab entry that spits the time out to the console once a minute, and bracketing the buildworld with "date"? Maybe it's a particular section of the tree, and not the load, that's getting you? Perhaps that region of the disk is corrupt? Obviously, I don't expect you to answer all of these to the list, or even to me, if the answer to the questions is "no impact". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807120621.XAA29796>