From owner-freebsd-stable Fri Jan 19 20:51:51 2001 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 2F7CA37B6A4 for ; Fri, 19 Jan 2001 20:51:32 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id batsaaaa for ; Sat, 20 Jan 2001 16:00:03 +1100 Message-ID: <3A691942.8D655973@quake.com.au> Date: Sat, 20 Jan 2001 15:51:14 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Conlen , freebsd-stable@freebsd.org Subject: Re: Problem with -stable and ata drives References: <3A691823.A999C66D@quake.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually it looks like he just MFC'd the patch in yesterday.. Modified files: (Branch: RELENG_4) sys/dev/ata ata-dma.c Log: MFC: Properly backspeed DMA on the ACER chips. Revision Changes Path 1.35.2.8 +3 -3 src/sys/dev/ata/ata-dma.c Get the new ata-dma.c and recompile your kernel, that should fix the problem unless this is a new one... Good Luck! Kal. Kal Torak wrote: > > Mike Conlen wrote: > > > > I've got a problem that, because of the nature of the problem and the > > environment I can't give better details on. > > > > When I cvsup'ed to -stable last week, (I was at 4.2 stable as of sometime > > in December at that point) I rebooted after installing the new kernel and > > when attempting to mount the filesystems it would time out on read. After > > a few such attempts it would fall back to PIO mode (which happens anyway > > eventually on my machine) and it could read, but then it would timeout on > > write while (I'm guessing here) fsck was running. I could boot the old > > kernel just fine. For some reason the new ipfw did not like diverting to > > natd and my networking was a bit of a mess. In any case, I could get the > > machine back to 4.2-release, which is where I sit for now. I didn't find > > anything about this type of a problem in the research I did. I'm curious > > if this is a known issue before I try to take my router apart to get chip > > set and drive information to debug. > > Yes, this is a know problem with some ata controllers... What chip set is > your controller? I had this happen with an Aladdin ata controller a few months > back, I got a patch from Soren that fixed it up... I dont think he has MFC'd > in the patch yet, maybe it still needs more testing... > > Anyway if you searched the stable archives I am sure you would find some posts > about this... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message