From owner-freebsd-current@FreeBSD.ORG Mon Sep 26 09:02:04 2005 Return-Path: X-Original-To: current@FreeBSD.org 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 93CEE16A41F for ; Mon, 26 Sep 2005 09:02:04 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5063F43D48 for ; Mon, 26 Sep 2005 09:02:04 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id AB3FF46B24; Mon, 26 Sep 2005 05:02:03 -0400 (EDT) Date: Mon, 26 Sep 2005 10:02:03 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Kris Kennaway In-Reply-To: <20050926003353.GA73440@xor.obsecurity.org> Message-ID: <20050926100058.Q34322@fledge.watson.org> References: <20050924034322.GA1636@xor.obsecurity.org> <20050926003353.GA73440@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@FreeBSD.org Subject: Re: deadlock in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 26 Sep 2005 09:02:04 -0000 On Sun, 25 Sep 2005, Kris Kennaway wrote: > On Fri, Sep 23, 2005 at 11:43:22PM -0400, Kris Kennaway wrote: >> Since updating my (UP i386) machines yesterday they're all hanging >> after a few hours of load with all processes in the following states: >> >> db> ps >> pid proc uid ppid pgrp flag stat wmesg wchan cmd >> 28397 c5267a3c 0 28396 28397 0000110 [SLPQ vmmaps 0xc1027178][SLP] cron >> 28396 c5267c48 0 386 386 0000000 [SLPQ ppwait 0xc5267c48][SLP] cron > > [...] > > This is still broken. Someone must have broken this in the past few > days, but I don't have time right now to do a binary search. Please, > everyone review your recent commits to see if you could be the > originator. You could try backing this out locally: 1.127 +16 -3 src/sys/fs/fifofs/fifo_vnops.c But I'm pretty sure it's not the source of the problem you've been seeing. If you were using process accounting, it could be the recent kern_acct.c change to convert NULL's to curthread's (even more unlikely), but I'm pretty sure you're not running process accounting. Robert N M Watson