From owner-freebsd-stable Tue May 22 14:30:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 392DF37B43C for ; Tue, 22 May 2001 14:30:51 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f4MLUog10802; Tue, 22 May 2001 14:30:50 -0700 (PDT) (envelope-from dillon) Date: Tue, 22 May 2001 14:30:50 -0700 (PDT) From: Matt Dillon Message-Id: <200105222130.f4MLUog10802@earth.backplane.com> To: Sean Chittenden Cc: stable@freebsd.org Subject: Re: Continuing ahc problems - also cause fxp failure References: <200105220925.f4M9Paf00409@earth.backplane.com> <20010522022905.Z72878@rand.tgd.net> <200105222118.f4MLI2S10482@earth.backplane.com> <20010522142237.I72878@rand.tgd.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : : :--E0LdhqWfziiBVv4P :Content-Type: text/plain; charset=us-ascii :Content-Disposition: inline :Content-Transfer-Encoding: quoted-printable : : Try this: rewind back in time and install a copy of 4.1 or :something like that. If the problem is less frequent, then you may be :right. If the crashing doesn't change, then suspect hardware. I push :_tons_ of traffic over almost the exact hardware and haven't had any :troubles, that's why I'm a skeptic of the hardware. ;~) -sc I can't do that to a production machine. It would also be a huge waste of time given the unlikelihood that the hardware was damaged at the exact point I upgraded the OS. It's possible that the hardware was damaged from day one, but, again, unlikely. Normal use of the machine doesn't seem to trigger a problem... the machine has only died in the early morning while network backups were being run. This makes it even less likely to be heat-related. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message