From owner-freebsd-hubs@FreeBSD.ORG Thu Dec 17 17:49:20 2009 Return-Path: Delivered-To: hubs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C63A81065695 for ; Thu, 17 Dec 2009 17:49:20 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 347938FC18 for ; Thu, 17 Dec 2009 17:49:19 +0000 (UTC) Received: by ewy26 with SMTP id 26so1503407ewy.3 for ; Thu, 17 Dec 2009 09:49:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=cAZwWZ4P40CMenMIMkWXtL+Y0wJ8y1MRBJKbMBSz7M4=; b=dcmqKvp9P9HNZD1HoZ094cFslNwhzJadlEQY9VsaC3sF9dvYvTzFq1b0SSna1U3vdo x8WaJAX801obApZwsxb1l1ml9B8n8mFfx9tPqKk/3gqy/34y4cVkh/YV2ODVauMW+zju 2KNIkcHooQ1q6Y9T9D8CgIy+cr6dy/S19lWhA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Rfs+gcYwlYPKO8uuzB1DNJW4fSl0eGvq7ZAUxDMosdhQ03dXSer5rBERTspon+Zjhm f55cyJHQtuxJJ5yhFs3N5+IwVX0hHXm3c6ylii4F0AmRmKnUo3/Vki+QtPHvMgRaVeUA pHteHgf/pQvY2nNEnfPqs0Mu72ydIyXf+V2C8= MIME-Version: 1.0 Received: by 10.213.44.134 with SMTP id a6mr8935131ebf.70.1261072158242; Thu, 17 Dec 2009 09:49:18 -0800 (PST) In-Reply-To: <4B2A3BE3.6050309@FreeBSD.org> References: <4B2A3BE3.6050309@FreeBSD.org> Date: Thu, 17 Dec 2009 19:49:18 +0200 Message-ID: <59adc1a0912170949i5a04963ah20104e4b2bc9e274@mail.gmail.com> From: Dimitar Vasilev To: Sergey Matveychuk Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: hubs@freebsd.org Subject: Re: cvsupd problem on amd64 X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD Distributions Hubs: mail sup ftp" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 17:49:20 -0000 I had such experience on amd64 bit fbsd 7-stable - cvsup.bg. After replacing a bad motherboard and having a new power supply along with fbsd 8 no more worries. Check a) hw b) current cvsupd version and upgrade if needed c) try to duplicate the current cvsup on a test box and see how it goes there. Regards, Dimitar 2009/12/17 Sergey Matveychuk > Hello. > > I have two cvsup boxes (cvsup2.ru and cvsup7.ru). Both are on > 7.2-RELEASE-p5. > One of them is on i386 with a repository on UFS, and next one is on amd64 > with a repository on md(4) disk. > > On amd64 box I have cvsupd crashed from time to time: > Dec 17 03:49:57 prophet kernel: pid 77828 (cvsupd), uid 1002: exited on > signal 10 > Dec 17 07:21:41 prophet kernel: pid 18789 (cvsupd), uid 1002: exited on > signal 10 > Dec 17 07:28:02 prophet kernel: pid 20018 (cvsupd), uid 1002: exited on > signal 10 > Dec 17 09:24:15 prophet kernel: pid 40506 (cvsupd), uid 1002: exited on > signal 10 > Dec 17 09:25:27 prophet kernel: pid 40556 (cvsupd), uid 1002: exited on > signal 10 > Dec 17 09:29:23 prophet kernel: pid 41329 (cvsupd), uid 1002: exited on > signal 10 > > but I see no core file afterwards. > > Anybody experienced it? What culprit may be? amd64 or md disk? Any more > ideas? > > -- > Dixi. > Sem. > _______________________________________________ > freebsd-hubs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hubs > To unsubscribe, send any mail to "freebsd-hubs-unsubscribe@freebsd.org" >