From owner-freebsd-current Sun Jan 21 3:14:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 23F1537B400 for ; Sun, 21 Jan 2001 03:13:56 -0800 (PST) Received: (qmail 51076 invoked by uid 1142); 21 Jan 2001 11:13:51 -0000 From: jasone@magnesium.net Date: 21 Jan 2001 03:13:51 -0800 Date: Sun, 21 Jan 2001 03:13:37 -0800 To: current@freebsd.org Subject: Fixed (was Re: HEADS UP: Strange booting lockups) Message-ID: <20010121031337.T69199@canonware.com> References: <20010121023238.S69199@canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010121023238.S69199@canonware.com>; from jasone@canonware.com on Sun, Jan 21, 2001 at 02:32:38AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 02:32:38AM -0800, Jason Evans wrote: > We don't know why this is happening, and at this point the primary > suspicion is that this problem has been lurking for quite some time, and > we've recently committed a combination of changes that causes the problem > to exhibit itself more consistently. Jake Burkholder, Peter Wemm, and I > all checked in changes that were independently tested and confirmed to > work, yet the combination of the changes seems to be bad, even though none > of them appear to touch code that is executed so early during boot. It was my fault. I tested my changes, and during review, one of the review comments was a request to change the order of fields in struct mtx. I didn't change the order in a static initializer though. Yay for last minute changes without repeated testing. Thanks go to Jake for finding the problem. In my tired and frantic state, I was about to resort to backing the whole thing out. =) > There is a report (that just came to my attention) of this problem existing > for one person at least two weeks ago, so it isn't clear yet what > conditions cause the problem to manifest itself. I'm not sure what caused the problem as mentioned in the above paragraph, but Donald Maddox may have the explanation for it in another email in this thread. Wearing the pointy hat, Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message