From owner-freebsd-questions Sun Mar 3 9:34:17 2002 Delivered-To: freebsd-questions@freebsd.org Received: from nycsmtp2out.rdc-nyc.rr.com (nycsmtp2out.rdc-nyc.rr.com [24.29.99.227]) by hub.freebsd.org (Postfix) with ESMTP id 4E40837B404 for ; Sun, 3 Mar 2002 09:34:15 -0800 (PST) Received: from scott1.nyc.rr.com (24-168-24-239.nyc.rr.com [24.168.24.239]) by nycsmtp2out.rdc-nyc.rr.com (8.12.1/Road Runner SMTP Server 1.0) with ESMTP id g23HWalu024475 for ; Sun, 3 Mar 2002 12:32:36 -0500 (EST) Message-Id: <5.1.0.14.0.20020303123056.049473f8@pop-server.nyc.rr.com> X-Sender: scottro@pop-server.nyc.rr.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 03 Mar 2002 12:32:58 -0500 To: freebsd-questions@FreeBSD.ORG From: Scott Subject: Re: FBSD 4.4 UDMA ICRC error In-Reply-To: <200203031729.g23HSx107845@lv.raad.tartu.ee> References: <5.1.0.14.0.20020303104354.00bb3de0@pop-server.nyc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 19:28 2002/03/03 +0200, Toomas Aas wrote: >An idle thought just hit me - maybe 3.2 simply doesn't report the >error? That makes sense actually. When I first began getting the errors, I thought, "Shucks, FreeBSD is more susceptible to bad hardware than Linux, I guess, as I don't get errors booting in Linux." Then, I took a closer look at my Linux bootup messages--and saw that I was getting CRC errors. :) Changing the cable fixed both O/S's. Or, perhaps 3.2 has an error that simply flashes by as it did with my Linux installation. FWIW Scott Robbins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message