From owner-freebsd-stable Wed Mar 13 19: 2:29 2002 Delivered-To: freebsd-stable@freebsd.org Received: from fep6.cogeco.net (smtp.cogeco.net [216.221.81.25]) by hub.freebsd.org (Postfix) with ESMTP id 3902337B402 for ; Wed, 13 Mar 2002 19:02:23 -0800 (PST) Received: from nyip.net (d141-99-70.home.cgocable.net [24.141.99.70]) by fep6.cogeco.net (Postfix) with ESMTP id 966DC2B34; Wed, 13 Mar 2002 22:02:18 -0500 (EST) Message-ID: <3C9012A7.1020600@nyip.net> Date: Wed, 13 Mar 2002 22:01:59 -0500 From: Jeff Evans User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Dejan Kastelic , freebsd-stable@freebsd.org Subject: Re: DMA problem fallback to PIO mode References: <20020312174219.N40700-100000@titanic.medinet.si> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dejan Kastelic wrote: >>I have a problem with hdd: >> >>ad4s1f: hard error reading fsbn 86162431 of 40472032-40472063 (ad4s1 bn >>86162431; cn 5363 tn 92 sn 40)ad4s1f: hard error readi >>ng fsbn 86162431 of 40472032-40472063 (ad4s1 bn 86162431; cn 5363 tn 92 sn >>40) status=59 error=40 >>ad4: DMA problem fallback to PIO mode >>ad4s1f: hard error reading fsbn 86162431 of 40472032-40472063 (ad4s1 bn >>86162431; cn 5363 tn 92 sn 40) status=59 error=40 >>ad4s1f: hard error reading fsbn 86162431 of 40472032-40472063 (ad4s1 bn >>86162431; cn 5363 tn 92 sn 40) status=59 error=40 >>ad4s1f: hard error reading fsbn 86162431 of 40472032-40472063 (ad4s1 bn >>86162431; cn 5363 tn 92 sn 40) status=59 error=40 >> > > Does it produce same errors when disk is under pressure (du -h on /) ? > > > I had same problem few months ago and i had to replace the disk. I have the exact same problem and although I don't know why it's happening, perhaps my situation will be able to shed some light. I was feeling adventurous and decided to change my FreeBSD machine to a more powerful one. I put the HD in a brand new machine, with all different hardware expecting it to just barf and I'd have to reinstall, or at least reconfigure. But it worked. Works fine now, but from the first boot it has been giving me that exact error. Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message