From owner-freebsd-stable@FreeBSD.ORG Tue Oct 7 10:05:46 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4EDA716A4C2 for ; Tue, 7 Oct 2003 10:05:46 -0700 (PDT) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id C774943FFB for ; Tue, 7 Oct 2003 10:05:20 -0700 (PDT) (envelope-from mike@sentex.net) Received: from avscan1.sentex.ca (avscan1.sentex.ca [199.212.134.11]) by smtp3.sentex.ca (8.12.9p2/8.12.9) with ESMTP id h97H5GHr040327; Tue, 7 Oct 2003 13:05:16 -0400 (EDT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by avscan1.sentex.ca (8.12.9p2/8.12.9) with ESMTP id h97H5J7w042379; Tue, 7 Oct 2003 13:05:19 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.9p1/8.12.9) with ESMTP id h97H5JdK098273; Tue, 7 Oct 2003 13:05:19 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.0.0.22.0.20031007121509.08247788@209.112.4.2> X-Sender: mdtpop@209.112.4.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Tue, 07 Oct 2003 13:08:37 -0400 To: moron , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <200310051342.04864.moron@industrial.org> References: <200310051342.04864.moron@industrial.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by Sentex Communications (avscan1/20021227) Subject: Re: DMA related disc issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Oct 2003 17:05:46 -0000 At 04:42 PM 05/10/2003, moron wrote: >Up until quite recently the machine has had a single drive in it and been >performing flawlessly, no disk problems or anything of that nature (nothing >untoward in messages, not spontaneous reboots, etc.). I have performed a few >CVSups and make worlds over the last month to deal with security issues and >such and about two weeks ago I added the second Seagate drive to the system. > >Shortly after adding the new drive (but also around the time of a CVSup), the Ok, it took me a while, but now I remember why this was dejavu. I saw the same thing on a similar setup. The one maxtor ata 133 was working fine. I added a slave, and all of a sudden errors on both. Not sure if its the maxtor or issue with ATA133. But I fixed the problem by forcing everything down to ATA100. I have this run at startup time /sbin/atacontrol mode 3 udma100 udma100 where 3 is the channel on which I have # atacontrol info 3 Master: ad6 ATA/ATAPI rev 6 Slave: ad7 ATA/ATAPI rev 6 and all has been happy for months. Also, double check that the jumpers are correctly set on all your IDE devices. ---Mike