From owner-freebsd-current@FreeBSD.ORG Sun Sep 5 19:43:45 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 1655016A4CE for ; Sun, 5 Sep 2004 19:43:45 +0000 (GMT) Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC3D043D41 for ; Sun, 5 Sep 2004 19:43:44 +0000 (GMT) (envelope-from dsyphers@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) ESMTP id i85JhioX014283 for ; Sun, 5 Sep 2004 12:43:44 -0700 Received: from [192.168.1.101] (c-24-18-235-11.client.comcast.net [24.18.235.11]) (authenticated bits=0)i85JhhOS009126 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Sun, 5 Sep 2004 12:43:44 -0700 From: David Syphers To: freebsd-current@freebsd.org Date: Sun, 5 Sep 2004 12:43:44 -0700 User-Agent: KMail/1.6.2 References: <007701c48e5b$530485f0$2508473e@sad.syncrontech.com> In-Reply-To: <007701c48e5b$530485f0$2508473e@sad.syncrontech.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409051243.44374.dsyphers@u.washington.edu> Subject: Still a problem (was: ATA write-dma interrupt was seen but timeout fired LBA=53346288) 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: Sun, 05 Sep 2004 19:43:45 -0000 On Sunday 29 August 2004 11:33 pm, Ari Suutari wrote: > >> ATA write-dma interrupt was seen but timeout fired LBA=53346288 > >> ATA write-dma interrupt was seen but timeout fired LBA=53346288 > >> ATA write-dma interrupt was seen but taskqueue stalled LBA=53346288 > > > > I updated my old Compaq 1500c from 4.10 to -current last week. > > I'm seeing similar messages after resume and the system hangs > > eventually. > > Otherwise the system seems to work ok. > > Updated to recent current (28.8) seems to fix this. I haven't seen any > ATA interrupt/timeout messages after update. I assume that these > changes are not on RELENG_5 branch yet, since it looked like it > still suffers from the problems above. This is still a problem on 5.3-BETA3... immediately after the taskqueue failure I get dropped into db with the panic panic: Duplicate free of item 0xc12e7e76 from zone 0xc11cb000(g_bio) When I first tried this I installed the apache package, and on boot it would panic before I could log in. I just did a minimal install, and I can log in and do stuff for a few seconds before panic. 5.2.1-R installs and boots fine on this system. As noted above, -CURRENT also would probably work, although I'd like to run RELENG_5. On a side note, I'm appreciating the irony that I've run oh-so-unstable -CURRENT without a single problem for 2 years, and suddenly when 5-CURRENT is frozen for transition to -STABLE, I can't even boot it. (Probably because in -CURRENT fixes happen very fast, but even very critical fixes are taking a long time to make it to RELENG_5 these days...) Why are we even releasing BETAs when there are huge problems like this that have fixes in HEAD? -David -- +++ Divide By Cucumber Error. Please Reinstall Universe And Reboot. +++