From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 13:00:32 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 C6D0516A546 for ; Tue, 27 Jan 2004 13:00:32 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A02243D64 for ; Tue, 27 Jan 2004 12:59:50 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i0RKuHUd048381; Tue, 27 Jan 2004 15:56:17 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i0RKuCRb048378; Tue, 27 Jan 2004 15:56:17 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Tue, 27 Jan 2004 15:56:12 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Chip Norkus In-Reply-To: <20040127195517.GA33225@teleri.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: RE: Processes blocked on ufs or getblk 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: Tue, 27 Jan 2004 21:00:33 -0000 On Tue, 27 Jan 2004, Chip Norkus wrote: > On Tue Jan 27, 2004; 10:36AM -0500 Robin P. Blanchard propagated the following: > > > [snip] > > > > > > As seen previously on this list, I'm also seeing processes getting stuck in > > in "getblk" state. I'm seeing this on a dell 2650 (smp enabled, acpi enabled, > > aac filesystem). I'm also more than willing to try out any patches anyone may > > cook up. > > > > Me too! I hate to bump this thread (again), but it seems like there is > almost zero interest in this particular bug, and it's pretty serious. > I've got a spare 2650 at work with a serial console and I'd be willing > to let some developers take a shot at it. The bug seems to be fairly > reproduceable on new filesystems/installations. There is interest in this bug, and a couple of people are running into it. Unfortunately, it's also a bug where the expertise necessary to explore/fix it in much detail is fairly narrowly distributed. I've seen at least one report that was sent to Jeff Roberson and Kirk McKusick. You might want to CC kirk@mckusick.com directly... We should get this on the 5.3-TODO list to make sure it's getting visibility. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research > > > --------------------------------------- > > Robin P. Blanchard > > Systems Integration Specialist > > Georgia Center for Continuing Education > > fon: 706.542.2404 < > fax: 706.542.6546 > > --------------------------------------- > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -chip > -- > personal: chip norkus; renaissance hacker; wd@teleri.net > work: systems engineer @ lunarpages, inc.; chip@lunarpages.com > info: finger wd@teleri.net for plan or keys; http://telekinesis.org > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >