From owner-freebsd-stable Fri Apr 14 23: 4:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from corinth.bossig.com (mail.dohboys.com [208.26.253.10]) by hub.freebsd.org (Postfix) with ESMTP id 80AC637B799 for ; Fri, 14 Apr 2000 23:04:13 -0700 (PDT) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (unverified [208.26.241.81]) by corinth.bossig.com (Rockliffe SMTPRA 4.2.1) with ESMTP id ; Fri, 14 Apr 2000 23:14:57 -0700 Message-ID: <38F8063B.D0035F81@3-cities.com> Date: Fri, 14 Apr 2000 23:03:39 -0700 From: Kent Stewart Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Troy Cc: stable@freebsd.org Subject: Re: ad0: WRITE command timeout References: <38F7F6F9.AC29F4AA@prodigy.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Troy wrote: > > The subject line shows the error message that I have been having. From > searching the newsgroups, archives, and the web I have discovered what > in my mind is a temporary fix, ie... sysctl -w hw.atamodes=pio,etc..... > The drive I have in my system is a Samsung SV0844D, which is an UDMA66 > drive, the controller is a PIIX4 which only supports UDMA33 and > supposedly is supported properly under FBSD. I began receiving this > error after upgrading to 4-stable using cvs from the 3-stable line I was > using. Unfortunately it has caused some data corruption, but I think > I've caught most of that. My question is, is there a way to fix it > without having to use pio modes and suffer that performance hit, or need > I just wait until the driver is fixed and when will that happen? > On a seperate note, since my switch to 4-stable some of my system > monitoring tools, ie.. top, vmstat, wmmon, etc have stopped functioning > properly, the output of top and vmstat are below, wiser individuals then > me hopefully will know where I went wrong. > ad0: 8063MB [16383/16/63] at ata0-master using UDMA33 > acd0: DVD-ROM at ata1-master using WDMA2 > Mounting root from ufs:wd0s1a It looks like you used an old kernel config. My dmesg shows ad0: 12427MB [25249/16/63] at ata0-master using UDMA33 ad1: 3020MB [6136/16/63] at ata0-slave using WDMA2 ad3: 13029MB [26473/16/63] at ata1-slave using UDMA33 acd0: CDROM at ata1-master using PIO4 Waiting 5 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) pass2 at ahc0 bus 0 target 6 lun 1 pass2: Removable Changer SCSI-2 device pass2: 5.000MB/s transfers (5.000MHz, offset 15) Mounting root from ufs:/dev/ad0s1a da0 at ahc0 bus 0 target 4 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) The mounting root is from ufs:/dev/ad0s1a where yours is still from wd0s1a, which is the old way. Kent > ad0: WRITE command timeout - resetting > ata0: resetting devices .. done > ad0: WRITE command timeout - resetting > ata0: resetting devices .. done > > > > top: nlist failed > > > > vmstat: undefined symbols: > _cp_time _kmemstatistics _bucket _zlist > > > Thanks for any and all assistance you can be with these issues. > > Troy Lubbers > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message