From owner-freebsd-questions@FreeBSD.ORG Tue Aug 4 07:10:34 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCE15106564A for ; Tue, 4 Aug 2009 07:10:34 +0000 (UTC) (envelope-from joel@vnode.se) Received: from mail.vnode.se (mail.vnode.se [62.119.52.82]) by mx1.freebsd.org (Postfix) with ESMTP id 771AE8FC15 for ; Tue, 4 Aug 2009 07:10:34 +0000 (UTC) (envelope-from joel@vnode.se) Received: from iMac.local (pgw.vnode.se [77.110.37.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.vnode.se (Postfix) with ESMTPSA id BD1E3E9F42C; Tue, 4 Aug 2009 09:10:32 +0200 (CEST) Message-ID: <4A77DEE4.607@vnode.se> Date: Tue, 04 Aug 2009 09:10:28 +0200 From: Joel Dahl User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) MIME-Version: 1.0 To: Glen Barber References: <4A7753A0.7040006@vnode.se> <4ad871310908031553i7c69708fv9d162514816c3e10@mail.gmail.com> <4ad871310908031616w15b8a16fw29a52f5b5168f713@mail.gmail.com> In-Reply-To: <4ad871310908031616w15b8a16fw29a52f5b5168f713@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Weird networking issue X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2009 07:10:35 -0000 Glen Barber skrev: > On Mon, Aug 3, 2009 at 6:53 PM, Glen Barber wrote: >> I have 2: >> 1.) Bad NIC >> 2.) Bad CPU >> >> A while back, I found out I had a bad CPU after replacing everything >> else on the machine -- I would still receive CRC mismatch errors with >> portsnap(8). >> >> The NIC is more probable IMHO, but both should be suspect here. >> > > Now that I think about it... Do you do regular builds? Can you try to > 'buildworld' (assuming you can get csup to pull the source tree? > > If CPU is the problem, you may experience random SIGSEGV errors when > running the buildworld. If it fails in different areas of the build, > this is most likely (from my experience) the problem. I've been doing buildworld -j4 for 8 hours without problems now. I'll see if I can get someone onsite to try another cable and switch port. -- Joel