From owner-freebsd-stable Sun Apr 23 12:58:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 2511337B66F for ; Sun, 23 Apr 2000 12:58:48 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id MAA07004; Sun, 23 Apr 2000 12:58:46 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id MAA24527; Sun, 23 Apr 2000 12:58:46 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sun, 23 Apr 2000 12:58:46 -0700 (PDT) Message-Id: <200004231958.MAA24527@vashon.polstra.com> To: jeff@mountin.net Subject: Re: CVSup core dumping In-Reply-To: <4.3.2.20000422140024.0235c610@mixcom.com> References: <4.3.2.20000422140024.0235c610@mixcom.com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <4.3.2.20000422140024.0235c610@mixcom.com>, Jeffrey J. Mountin wrote: > > Running 4.0S as of 3/29 and CVSup has worked without a hitch up through > about 2 days back. Now it is core dumping with illegal instruction and > does this with cvsup7 or cvsup4. One recent change was the addition of > Samba, which was not running at the time. I removed it and rebooted with > the same results. The only other change was to remove the comment from > some categories that I do not bother to update very often. Long shot, but > it was another variable and CVSup then completed. > > Alright, comment out my usual ports and once again remove the comments from > the additional categories I wanted to update. Once again completed. > > Then when trying once more after adding the usual ports ended up with > another core dump for a total of 6 now, which I saved. > > Had no problems with doc, web, and system sources. I haven't seen any other reports of this problem. I'm not sure I follow all the intricacies of your supfile modifications. If you can narrow it down to one collection that is definitely tied to the problem, I might be able to help track it down. Illegal instruction is a pretty strange error to have. Aside from HW or kernel problems, the only semi-likely explanation for that would be an overflowed thread stack. If you have time, please grab the appropriate unstripped binary from http://people.freebsd.org/~jdp/ These correspond exactly with the cvsup-bin and cvsupd-bin ports, so if you're using those ports you will be able to use the unstripped binaries with your existing core dumps to get a stack trace. > Also cvsup6 was refusing connections today, which I haven't seen and > would not expect for early Saturday afternoon. Ping indicated that was caused by network problems. It seems to be OK now. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message