Date: Tue, 04 Aug 2009 09:10:28 +0200 From: Joel Dahl <joel@vnode.se> To: Glen Barber <glen.j.barber@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Weird networking issue Message-ID: <4A77DEE4.607@vnode.se> In-Reply-To: <4ad871310908031616w15b8a16fw29a52f5b5168f713@mail.gmail.com> References: <4A7753A0.7040006@vnode.se> <4ad871310908031553i7c69708fv9d162514816c3e10@mail.gmail.com> <4ad871310908031616w15b8a16fw29a52f5b5168f713@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Glen Barber skrev: > On Mon, Aug 3, 2009 at 6:53 PM, Glen Barber<glen.j.barber@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A77DEE4.607>