From owner-freebsd-hackers@FreeBSD.ORG  Wed Oct 13 13:02:36 2004
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9086E16A4CE
	for <freebsd-hackers@freebsd.org>;
	Wed, 13 Oct 2004 13:02:36 +0000 (GMT)
Received: from beer.ux6.net (beer.ux6.net [64.62.253.29])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 53E2B43D31
	for <freebsd-hackers@freebsd.org>;
	Wed, 13 Oct 2004 13:02:36 +0000 (GMT)	(envelope-from miha@ghuug.org)
Received: from [64.62.253.84] (helo=miha.netstream-gh.com)
	by beer.ux6.net with esmtpa (Exim 4.42 (FreeBSD))
	id 1CHim1-0003b1-Fg
	for freebsd-hackers@freebsd.org; Wed, 13 Oct 2004 06:02:34 -0700
From: "Mikhail P." <miha@ghuug.org>
To: freebsd-hackers@freebsd.org
Date: Wed, 13 Oct 2004 13:03:35 +0000
User-Agent: KMail/1.7
References: <200410081937.15068.miha@ghuug.org>
	<200410091701.01987.miha@ghuug.org> <200410102330.26228.miha@ghuug.org>
In-Reply-To: <200410102330.26228.miha@ghuug.org>
Organization: Ghana Unix Users Group
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200410131303.35695.miha@ghuug.org>
X-Spam-Score: -4.9 (----)
X-Spam-Report: Spam detection software, running on the system "beer.ux6.net",
	hasmessageblock	similar future email.  If you have any questions, see
	the administrator of that system for details.> On
	Saturday 09 October 2004 17:01, Mikhail P. wrote: > > I also gotUDMA
	values. I switched from UDMA100 to UDMA66. System's uptime is 12 > >
	hours, and no timeouts so far.. but I'm quite sure they will get back
	in > > few days. > > 1.5 days of uptime, running in UDMA66 changes
	nothing. Still getting [...] 
	Content analysis details:   (-4.9 points, 6.0 required)
	pts rule name              description
	--------------------------------------------------1%	[score: 0.0000]
Subject: Re: ad0: FAILURE - WRITE_DMA
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: miha@ghuug.org
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2004 13:02:36 -0000

On Sunday 10 October 2004 23:30, Mikhail P. wrote:
> On Saturday 09 October 2004 17:01, Mikhail P. wrote:
> > I also got another message off-list, where author suggested to play with
> > UDMA values. I switched from UDMA100 to UDMA66. System's uptime is 12
> > hours, and no timeouts so far.. but I'm quite sure they will get back in
> > few days.
>
> 1.5 days of uptime, running in UDMA66 changes nothing. Still getting

Well, now those timeouts popped up on 5.3-BETA7 system with 4 IDE drives.. 
They start appearing with high disk activity.
System had FreeBSD-4.7 prior to that, and has been rock solid for almost a 
year. Drives have no problems, that's for sure (4.7 did not show up any 
timeouts, with uptime for months)..

I don't know what to think - is ATA driver horribly broken in 5.x?

regards,
M.