From owner-freebsd-questions Mon Apr 12 14:25:17 1999 Delivered-To: freebsd-questions@freebsd.org Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179]) by hub.freebsd.org (Postfix) with ESMTP id 45BE714E95 for ; Mon, 12 Apr 1999 14:25:13 -0700 (PDT) (envelope-from root@eyelab.psy.msu.edu) Received: from devel-eyelab (dhcp109.baker.ssc.msu.edu [35.8.194.109]) by eyelab.psy.msu.edu (8.9.2/8.9.2) with ESMTP id RAA58232; Mon, 12 Apr 1999 17:22:16 -0400 (EDT) (envelope-from root@eyelab.psy.msu.edu) Message-Id: <4.2.0.32.19990412172412.00ab73b0@eyelab.msu.edu> X-Sender: root@eyelab.msu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.32 (Beta) Date: Mon, 12 Apr 1999 17:26:01 -0400 To: Patrick Seal From: Gary Schrock Subject: Re: wdtimeout() DMA status 4 Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:17 PM 4/12/99 -0700, Doug White wrote: >On Mon, 12 Apr 1999, Patrick Seal wrote: > >> It's a new disk. I just replaced the old disk that was giving similar >> behavior. Could it be the disk controller or just a coincidence? >> > >Bad cable? I've just had seagate suggest to me for a similar problem that it could just be that the cable I'm using is too noisy and that their drives are very sensitive to interference in ultra dma modes. Basically they're saying I might have to go to a ATAS cable for things to work properly. I had been seeing similar errors to that (and managed to wipe out my freebsd installation no less too). Gary Schrock root@eyelab.msu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message