From owner-freebsd-current@FreeBSD.ORG Wed May 12 05:43:40 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 5D95216A4CE for ; Wed, 12 May 2004 05:43:40 -0700 (PDT) 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 EC91B43D39 for ; Wed, 12 May 2004 05:43:38 -0700 (PDT) (envelope-from sos@DeepCore.dk) Received: from DeepCore.dk (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i4CChUtb034080; Wed, 12 May 2004 14:43:35 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <40A21BF1.4080502@DeepCore.dk> Date: Wed, 12 May 2004 14:43:29 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.5 (X11/20040329) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ion-Mihai Tetcu References: <20040512145212.62e7db1e@it.buh.cameradicommercio.ro> In-Reply-To: <20040512145212.62e7db1e@it.buh.cameradicommercio.ro> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-current@freebsd.org Subject: Re: ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=21267353 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: Wed, 12 May 2004 12:43:40 -0000 Ion-Mihai Tetcu wrote: > Could someone tell me what this means (-CURRENT)? The WRITE operation was signalled done by the disk by issueing an interrupt and the finished request was put on a taskqueue to have it return status to the system. However the timeout code fired because the taskqueue hadn't been executed yet (it will wait one ome timeout period before the result is forced through).. So there is no harm done, but the taskqueue was slow to respond... -- -Søren