From owner-freebsd-current@FreeBSD.ORG Sat Nov 13 10:01:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C02C16A4CE; Sat, 13 Nov 2004 10:01:20 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id C855843D49; Sat, 13 Nov 2004 10:01:19 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id iADA1FL4089699; Sat, 13 Nov 2004 11:01:17 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <4195DB3E.2040807@DeepCore.dk> Date: Sat, 13 Nov 2004 11:00:30 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <25539.1100339599@critter.freebsd.dk> In-Reply-To: <25539.1100339599@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: Garance A Drosihn cc: Zoltan Frombach cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Nov 2004 10:01:20 -0000 Poul-Henning Kamp wrote: > In message <4195D903.2090801@DeepCore.dk>, =3D?ISO-8859-1?Q?S=3DF8ren_S= chmidt?=3D wri > tes: >=20 >>Zoltan Frombach wrote: >> >>>This is still an issue for me. Please read this post of mine: >>>http://lists.freebsd.org/pipermail/freebsd-stable/2004-November/009420= =2Ehtml >>> >>>Can anyone help? I would gladely install test patches to track this=20 >>>problem down. My system is 5.3-R. And the WRITE_DMA warning happens at= =20 >>>least twice a day, it is so predictable. With thanks, >> >>Hmmm, that warning is issued from ATA when requests has been returned t= o=20 >>the systems bio_taskqueue but the system hasn't finished them within th= e=20 >>timeout. Now this is an indication of the system being unresponsive=20 >>already at that point, or at least that was the idea. >>It has nothing to do with a bad drive, since the interrupt was seen the= =20 >>drive has finished the request it was asked, its the layers above ATA=20 >>that doesn't respond to the request beeing returned as finished. >=20 > It is not really the task of the ata driver to fail requests at that > time. How long is the timeout anyway ? Oh, ATA doesn't fail them, it just yells that the request hasn't been=20 finished yet by the upper layers, it doesn't do anything to the request. Timeout is 5 secs, which is a pretty long time in this context IMHO.. However, if it can take that long time to get data pushed up the chain,=20 it might also explain some of the reduced I/O performance reported ? --=20 -S=F8ren