From owner-freebsd-stable Tue Nov 28 6:48: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id CBDB237B400 for ; Tue, 28 Nov 2000 06:48:03 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id vhbsaaaa for ; Wed, 29 Nov 2000 01:53:53 +1100 Message-ID: <3A23C5AB.C15DFA2B@quake.com.au> Date: Wed, 29 Nov 2000 01:48:11 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Adrian Penisoara Cc: Michael , "Corey G." , freebsd-stable@FreeBSD.ORG Subject: Re: ata0 problems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adrian Penisoara wrote: > > Hi, > > Just to be sure: please post the dmesg part refering to ATA probes. > Also please post the result of "sysctl hw.atamodes'; if it has a "dma" in > the list then try a "sysctl -w hw.atamodes=pio,---,---,---" under root and > check if the error appear again. > > I seem to remember I had this kind of problems myself too and I believe > this is because of some issues when operating in DMA mode (either hardware > configuration issues, like bad cable, eiher a driver problem). I solved my > problem by forcing the controller into PIO mode ("hw=pio,---,---,---" in > /etc/sysctl.conf). > > Ady (@warpnet.ro) > > On Fri, 24 Nov 2000, Michael wrote: > > > FreeBSD 4.2 > > Cyrix-166 > > ATA-66- WD 7200 2Mb cache > > > > On Thu, 23 Nov 2000, Corey G. wrote: > > > > > I saw the same error tonight. (if it is an error). > > > > > > FreeBSD 4.2 > > > AMD K62-450 > > > ATA-66 - Maxtor Drive > > > > > > ad0: WRITE command timeout tag=0 serv=0 - resetting > > > ata0: resetting devices .. done > > > ad0: WRITE command timeout tag=0 serv=0 - resetting > > > ata0: resetting devices .. done > > > > > > On Thu, Nov 23, 2000 at 06:30:11PM +0000, Michael wrote: > > > > Hello > > > > I have problems in FreeBSD 4.2-STABLE > > > > > > > > > > > > Nov 23 09:49:53 lucky /kernel: ata0: resetting devices .. done > > > > Nov 23 09:50:44 lucky /kernel: ad0: WRITE command timeout tag=0 serv=0 - > > > > resetting > > > > > > > > regards, Michael > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-stable" in the body of the message > > > ---end quoted text--- > > > > > > -- > > > Best Regards, > > > Corey I have this exact same problem as well, it goes away in PIO mode, but what if we want to use DMA or UDMA? I think the ata driver needs some fixing because DMA mode worked fine in previouse version of FreeBSD... 4.1R I use UDMA33 without any errors, yet once upgraded to 4.2S I have to use PIO mode or I cant access the drive. It would seem to be that a controler and a drive that support DMA transfers are not the problem but the driver that cant use them properly is... I dont see how you can blame it on faulty hardware or cables when the EXACT same system using 4.0R and 4.1R was able to use DMA mode with no problems... People have said that after getting this error there drives have been totaly hosed, unable to even boot, I find it hard to put this down to the driver, but somehow I doubt every haivng this problem is using dodgey equipment... So while its possible to get around the problems using PIO mode it seems silly to not fix a bug just because you can get around it... We have the workaround... now lets have the fix?! Cheers everyone, Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message