From owner-freebsd-smp Mon Oct 2 9:37:30 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 9154637B502 for ; Mon, 2 Oct 2000 09:37:24 -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 13g8aZ-000Fq3-00; Mon, 2 Oct 2000 18:37:15 +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 e92GbJj01791; Mon, 2 Oct 2000 18:37:19 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200010021637.e92GbJj01791@grimreaper.grondar.za> To: Steve Kargl Cc: freebsd-smp@FreeBSD.ORG Subject: Re: 2 panics with MP kernels References: <200010021544.e92FiNw13072@troutmask.apl.washington.edu> In-Reply-To: <200010021544.e92FiNw13072@troutmask.apl.washington.edu> ; from Steve Kargl "Mon, 02 Oct 2000 08:44:23 MST." Date: Mon, 02 Oct 2000 18:37:19 +0200 From: Mark Murray Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Take out 'options USER_LDT' and 'device random' and you should be able to > > get -CURRENT running. > > > > I can toss 'options USER_LDT', but isn't 'device random' > now mandatory? The 20000710 entry in src/UPDATING suggests > that crypto tools will break. The only unstableness about device random that I'm aware of is a guaranteed panic if you try to unload the module. If its built in, no problem. 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