Date: Mon, 3 Jan 2000 14:21:18 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: George Cox <gjvc@extremis.demon.co.uk> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Repeated softupdates panics in 3.3-STABLE Message-ID: <200001032221.OAA09560@apollo.backplane.com> References: <20000103162905.A13617@osaka.louisville.edu> <20000103220555.C97693@extremis.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
: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. :-(
Well, in Keith's case the locking-against-myself panic is not the
cause, but the effect of the 'softdep_fsync: pending ops' panic
that occured just before it.
I've never seeing a pending ops panic before, this is going to be
one for Kirk to track down. Be sure to keep your core dump and
your debug kernel. In fact, if you could gzip them both up and make
them available to me and Kirk via a hidden ftp or hidden URL I
would appreciate it. NOTE! Kernel core dumps often contain
sensitive information such as pieces of the password file, do not
make your core available to the general lists!
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001032221.OAA09560>