From owner-freebsd-current@FreeBSD.ORG Wed May 12 08:05:23 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 A9D0616A4CE for ; Wed, 12 May 2004 08:05:23 -0700 (PDT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0762D43D45 for ; Wed, 12 May 2004 08:05:23 -0700 (PDT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id DD8691FFDD6; Wed, 12 May 2004 17:05:21 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 02FBD1FFDD5; Wed, 12 May 2004 17:05:19 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 0943D154FC; Wed, 12 May 2004 15:05:04 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id F269B154E5; Wed, 12 May 2004 15:05:04 +0000 (UTC) Date: Wed, 12 May 2004 15:05:04 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= In-Reply-To: <40A2387E.1050208@DeepCore.dk> Message-ID: References: <20040512145212.62e7db1e@it.buh.cameradicommercio.ro> <40A2387E.1050208@DeepCore.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de 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 15:05:23 -0000 On Wed, 12 May 2004, S=F8ren Schmidt wrote: > Bjoern A. Zeeb 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... > > > > > > as postend to freebsd-amd64 I am getting far too many of those and > > they won't stop. > > > > From time to time there is also > > ad10: WARNING - WRITE_DMA interrupt was seen but taskqueue stalled LBA= =3D... > > between all the ${subject} lines. > > Hmm, something is keeping the taskqueue busy, and its not ATA... but the thing starts with ${subject} and only after some dozen logs (multi monitor pages) I get one or two taskqueue stalled; afterwards ${subject} keeps scrolling again and everything starts from the beginning. Further more I can only reproduce it with heavy IO HDD traffic; it doesn't happen for network trafic, it doesn't happen when only working on a 512MB md0 memory disk I think. It happens once I copy sources to HDD, have src or obj on HDD and compiling world. The strange thing that made makes me thinking is that I also get it when using atacontrol and set the channel to PIO0 BIOSPIO; it's on amd64 with 5.2.1R; I am currently cross compiling HEAD for that machine. is there any way how I could get to know what's keeping the taskqueue busy ? if scrolling starts no user interaction is possible anymore. --=20 Bjoern A. Zeeb=09=09=09=09bzeeb at Zabbadoz dot NeT 56 69 73 69 74=09=09=09=09http://www.zabbadoz.net/