From owner-freebsd-current@FreeBSD.ORG Wed Nov 10 08:12:22 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 6629816A4CE for ; Wed, 10 Nov 2004 08:12:22 +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 B80F443D3F for ; Wed, 10 Nov 2004 08:12:21 +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 iAA8CGPo033474; Wed, 10 Nov 2004 09:12:18 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <4191CD35.9040000@DeepCore.dk> Date: Wed, 10 Nov 2004 09:11:33 +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: Zoltan Frombach References: In-Reply-To: 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: freebsd-current@freebsd.org Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout - what does it mean? 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, 10 Nov 2004 08:12:22 -0000 Zoltan Frombach wrote: > I just upgraded to 5.3-RELEASE a few days ago. This morning this line=20 > got into my system log file: > Nov 9 06:14:03 www kernel: ad0: WARNING - WRITE_DMA interrupt was seen= =20 > but timeout fired LBA=3D2491143 >=20 > I've never seen this message before. Can someone please explain what it= =20 > means? With Thanks, It means that the disk has processed the write request (interrupt seen), = but that the system (the bio_taskqueue) hasn't been able to get the=20 result returned to the kernel. Your disk is not involved in this problem since it has done its part,=20 but the rest of the system is either busy with something else, or there=20 are bugs lurking that prohibits the bio_taskqueue from running. Either way its a WARNING not a FAILURE :) --=20 -S=F8ren