Date: Mon, 22 Apr 2002 22:43:43 +0300 (EEST) From: Adrian Penisoara <ady@freebsd.ady.ro> To: Bruce Evans <bde@zeta.org.au> Cc: "Jacques A. Vidrine" <nectar@FreeBSD.ORG>, alfred@FreeBSD.ORG, phk@FreeBSD.ORG, Maxim Konovalov <maxim@macomnet.ru>, freebsd-current@FreeBSD.ORG Subject: Re: panic:bremfree with today's current and linux-netscape Message-ID: <Pine.BSF.4.10.10204222237120.10937-100000@ady.warpnet.ro> In-Reply-To: <20020422231049.V8742-100000@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Mon, 22 Apr 2002, Bruce Evans wrote: > Yes; I forgot to write the clause about it only being equivalent to a > panic if certain options (mainly INVARIANTS) are configured. > > > do see that falloc does lock the file descriptor table too, though --- > > I wonder how it ever worked. > > INVARIANTS causes a check of an assertion that non-recursive locks > like fd_mtx aren't actually misused recursively. The check causes more > panics than the misuse since the misuse is rarely fatal. I may be > missing something since I rarely use INVARIANTS and haven't checked > that it causes the panic deterministically. I think you're talking about the WITNESS option rather than INVARIANTS, that's the one who's at least documented in GENERIC as being responsible for mutex and deadlock checks. And this is somewhat confirmed by the face that an alternative kernel that I built doesn't panic and the difference between them two is that WITNESS is disabled in the non-panicking one. Happy debuggin' Ady (@freebsd.ady.ro) _______________________________________________________________________ | Programming in BASIC causes brain damage. | | (Edsger Wybe Dijkstra) | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10204222237120.10937-100000>