From owner-freebsd-current Sun Jun 27 18:19:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mom.hooked.net (mom.hooked.net [206.80.6.10]) by hub.freebsd.org (Postfix) with ESMTP id 4CB831527E for ; Sun, 27 Jun 1999 18:19:12 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from fish.hooked.net (garbanzo@fish.hooked.net [206.80.6.48]) by mom.hooked.net (8.8.6/8.8.5) with SMTP id SAA25989; Sun, 27 Jun 1999 18:18:58 -0700 (PDT) Date: Sun, 27 Jun 1999 18:18:58 -0700 (PDT) From: Alex Zepeda To: Doug Cc: Peter Wemm , current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. In-Reply-To: <3776C7B1.AF90EF76@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Jun 1999, Doug wrote: > *nod* I will just hang out in windows for a while and check my commit > mail. If it doesn't get fixed by the time I am ready to go back to beating > on my serial console project, I'll do just that. Hah, well some of us aren't quite that lucky :) I managed to reproduce the "netscape crashes the box" thing a few times. And then, triggered a crash (probably the same one) at the command prompt by compiling a few things (got a trace from that one). Savecore didn't want to cooperate however, so I recompiled it, and decided to manually panic the box, which worked fine but the kernel panic'd at savecore (same lockmgr: pid xxx not exclusive... unlocking as I got on the cmd line). Oddly enough, the pid was -2 when savecore tickled it. - alex who wonders who might be crazy enough to port fbsd to mack86k.. You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message