From owner-freebsd-hackers Mon Jan 3 14:16:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with SMTP id 6F4D014DE2 for ; Mon, 3 Jan 2000 14:16:13 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: (qmail 98176 invoked by uid 1010); 3 Jan 2000 22:05:55 -0000 Date: Mon, 3 Jan 2000 22:05:55 +0000 From: George Cox To: freebsd-hackers@freebsd.org Subject: Re: Repeated softupdates panics in 3.3-STABLE Message-ID: <20000103220555.C97693@extremis.demon.co.uk> References: <20000103162905.A13617@osaka.louisville.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: <20000103162905.A13617@osaka.louisville.edu>; from k.stevenson@louisville.edu on Mon, Jan 03, 2000 at 04:29:06PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03/01 16:29, Keith Stevenson wrote: > It looks like I may have spoken too soon when I mentioned that I had no > problems with softupdates on my postfix based mail server. I have now had > two panics in the last month with a panicstr of "softdep_lock: locking > against myself". I thought that the first one might have been a fluke until > it repeated itself today. I too have seen this "softdep_lock: locking against myself" panic on a Postfix server. I was able to trigger it I think maybe twice by issuing a 'postfix flush' command. :-/ This _was_ some months ago, when there was the odd commit to the softupdates code going in, which suggests it's kind of a long standing bug. :-( (yes I know this isn't particularly useful -- I'm just trying to say "ME TOO!!!" in a quasi-intelligent way. :-) ) best; gjvc -- [gjvc] \\ "...limited as I am by the sequential nature \\ of human communication." -- E. W. Dijkstra To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message