From owner-freebsd-smp Fri Oct 6 18:10:37 2000 Delivered-To: freebsd-smp@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id E4D7937B503; Fri, 6 Oct 2000 18:10:32 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id EF85728AAF; Sat, 7 Oct 2000 08:10:27 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id E7DA328645; Sat, 7 Oct 2000 08:10:27 +0700 (ALMST) Date: Sat, 7 Oct 2000 08:10:27 +0700 (ALMST) From: Boris Popov To: John Baldwin Cc: freebsd-smp@FreeBSD.org Subject: RE: Problems with kthread_exit() and SMPng In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 6 Oct 2000, Boris Popov wrote: > > It should have died much earlier if you had INVARIANTS turned on. :( It > > looks like you are releasing a mutex you probably do not own because > > cpu_exit() (called by exit1() -> exit() -> kthread_exit()) releases Giant > > as one of its final tasks. > > This is probably the bug somewhere in the diagnostic code. I have > INVARIANTS/INVARIANT_SUPPORT/DIAGNOSTIC turned on and UP machine just > panics in the mtx_exit_hard() while SMP machine silently reboots :( Actually, this is happens because #ifdef INVARIANTS is hidden behind #ifdef SMP_DEBUG which looks slightly misleading. Eg: if one decides to compile kernel with INVARIANTS then he expects sanity checks in the all core subsystems. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message