From owner-freebsd-current@FreeBSD.ORG Wed May 12 09:10:11 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 79CF016A4CE for ; Wed, 12 May 2004 09:10:11 -0700 (PDT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0F5D43D48 for ; Wed, 12 May 2004 09:10:10 -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 2B1B81FFDD6; Wed, 12 May 2004 18:10:09 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 5A0881FFDD5; Wed, 12 May 2004 18:10:07 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 086C1154FC; Wed, 12 May 2004 16:09:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id F0984154E5; Wed, 12 May 2004 16:09:25 +0000 (UTC) Date: Wed, 12 May 2004 16:09:25 +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: <40A23FEE.3020109@DeepCore.dk> Message-ID: References: <20040512145212.62e7db1e@it.buh.cameradicommercio.ro> <40A23FEE.3020109@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 16:10:11 -0000 On Wed, 12 May 2004, S=F8ren Schmidt wrote: > >>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. > > It always start like that, the stalled warning is the final operation > after 3 timeouts. Thanks, that had been the glue record I missed. > its bits when this fails, but it cannot get results returned back to the > system via the taskqueue subsystem. When the "stalled" warning shows up > ATA forces the result back circumventing the taskqueues. > > > 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. > > Instrumenting the queue code ? If I could get the machine to be actually usable recompiling HEAD or a kernel wouldn't be that hard. Looking forward for my cross build to finish and hopefully be able to install a kernel and world via NFS without triggering the problem. Shall see. --=20 Bjoern A. Zeeb=09=09=09=09bzeeb at Zabbadoz dot NeT 56 69 73 69 74=09=09=09=09http://www.zabbadoz.net/