From owner-freebsd-current@FreeBSD.ORG Sat Nov 13 10:30:09 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 4539116A4CE; Sat, 13 Nov 2004 10:30:09 +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 9678C43D1D; Sat, 13 Nov 2004 10:30:08 +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 iADAU4NQ090087; Sat, 13 Nov 2004 11:30:06 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <4195E1FF.5090906@DeepCore.dk> Date: Sat, 13 Nov 2004 11:29:19 +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: <25983.1100341229@critter.freebsd.dk> In-Reply-To: <25983.1100341229@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:30:09 -0000 Poul-Henning Kamp wrote: > In message <4195DB3E.2040807@DeepCore.dk>, =3D?ISO-8859-1?Q?S=3DF8ren_S= chmidt?=3D wri > tes: >=20 >=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= =2E >> >>Timeout is 5 secs, which is a pretty long time in this context IMHO.. >=20 > Five seconds counted from when ? Now thats the nasty part :) ATA starts the timeout when the request is issued to the device, so=20 theoretically the disk could take 4.9999 secs to complete the request=20 and then the timeout fires before the taskqueue gets its chance at it,=20 but IMHO thats pretty unlikely... Anyhow, I can just remove the warning from ATA if that makes anyone=20 happy, since its just a warning and ATA doesn't do anything with it at al= l. However, IMNHO this points at a problem somewhere that we should better=20 understand and fix instead. --=20 -S=F8ren