From owner-freebsd-smp Mon Oct 2 9:59:51 2000 Delivered-To: freebsd-smp@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id C0E3037B502 for ; Mon, 2 Oct 2000 09:59:46 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13g8wJ-000G3p-00; Mon, 2 Oct 2000 18:59:44 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e92Gxoj01904; Mon, 2 Oct 2000 18:59:50 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200010021659.e92Gxoj01904@grimreaper.grondar.za> To: Steve Kargl Cc: freebsd-smp@FreeBSD.ORG Subject: Re: 2 panics with MP kernels References: <200010021651.e92Gpml13396@troutmask.apl.washington.edu> In-Reply-To: <200010021651.e92Gpml13396@troutmask.apl.washington.edu> ; from Steve Kargl "Mon, 02 Oct 2000 09:51:48 MST." Date: Mon, 02 Oct 2000 18:59:50 +0200 From: Mark Murray Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ Sorry - I fat-fingered the other one ] > If you can't find my original email, the panic message is > below my .sig. This is for a MP kernel from a few days > ago. The panic is probably in the new mutex code, but > /dev/random starts the trace in db. I've never seen that actual one. I have seen similar mutex panics, though. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message