From owner-freebsd-current@FreeBSD.ORG Sat May 1 12:49:38 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E5A32106566C for ; Sat, 1 May 2010 12:49:38 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nschwmtas01p.mx.bigpond.com (nschwmtas01p.mx.bigpond.com [61.9.189.137]) by mx1.freebsd.org (Postfix) with ESMTP id 52CAD8FC0A for ; Sat, 1 May 2010 12:49:37 +0000 (UTC) Received: from nschwotgx03p.mx.bigpond.com ([124.188.161.100]) by nschwmtas01p.mx.bigpond.com with ESMTP id <20100501124936.YIAB17427.nschwmtas01p.mx.bigpond.com@nschwotgx03p.mx.bigpond.com>; Sat, 1 May 2010 12:49:36 +0000 Received: from duncan.reilly.home ([124.188.161.100]) by nschwotgx03p.mx.bigpond.com with ESMTP id <20100501124936.HGWJ2192.nschwotgx03p.mx.bigpond.com@duncan.reilly.home>; Sat, 1 May 2010 12:49:36 +0000 Date: Sat, 1 May 2010 22:49:35 +1000 From: Andrew Reilly To: "K. Macy" Message-ID: <20100501124935.GA2542@duncan.reilly.home> References: <20100430161953.GW96847@bunrab.catwhisker.org> <20100430231240.GA28805@duncan.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at nschwotgx03p.mx.bigpond.com from [124.188.161.100] using ID areilly@bigpond.net.au at Sat, 1 May 2010 12:49:35 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150205.4BDC2360.006A,ss=1,fgs=0 X-SIH-MSG-ID: rxs6GdL5TAD0zmQs0WyzOwJxyArnqyN48Z4QX81loRIGTUDCp8DeQ9rAIudRvN+vxC5NJhuHNGUpaa/iTY3Rs9mK Cc: current@freebsd.org Subject: Re: Panic @r207433: "System call fork returning with the following locks held" 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: Sat, 01 May 2010 12:49:39 -0000 Hi Kip, Sorry for the delay: it's been a tussle... On Fri, Apr 30, 2010 at 04:42:12PM -0700, K. Macy wrote: > Does FBSDID get expanded when checking out with csup? Looks like it: > __FBSDID("$FreeBSD: head/sys/vm/vm_pageout.c 207452 2010-04-30 > 22:31:37Z kmacy $"); My version says: __FBSDID("$FreeBSD: src/sys/vm/vm_pageout.c,v 1.316 2010/04/30 22:31:37 kmacy Exp $"); > line 451 is part of a KASSERT on this version. Yep. About half an hour after sending the previous message my system siezed up again, and I've been coaxing it back to health since. Must make a note to myself to be more careful... I managed to find a boot configuration that was stable enough to grab the latest updates off the local cvs server. Then back to single-user mode to build the kernel, and all was sweetness and puppies after that. Thanks for the fixes! All? Not quite: about simultaneous with the vm_pageout weirdness (which means something (else?) committed in the last week), my courier-authdaemond has been dying on startup thusly: May 1 22:29:06 duncan authdaemond: /var/run/authdaemond/socket: Cross-device link It never used to die like that before, and I haven't changed anything in its configuration. The socket in question is presumably the one listed: instead there's a socket in that directory called socket.tmp, but the process itself is long gone. I don't suppose that that rings a bell? Anything change with respect to unix-domain sockets or in the last week? Cheers, -- Andrew