From owner-freebsd-current Wed Jul 17 9:57:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B1C037B400 for ; Wed, 17 Jul 2002 09:57:48 -0700 (PDT) Received: from glatton.cnchost.com (glatton.cnchost.com [207.155.248.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80C2A43E64 for ; Wed, 17 Jul 2002 09:57:47 -0700 (PDT) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (adsl-209-204-185-216.sonic.net [209.204.185.216]) by glatton.cnchost.com id MAA28965; Wed, 17 Jul 2002 12:57:42 -0400 (EDT) [ConcentricHost SMTP Relay 1.14] Message-ID: <200207171657.MAA28965@glatton.cnchost.com> To: Terry Lambert Cc: Szilveszter Adam , freebsd-current@FreeBSD.ORG Subject: Re: Interesting panic very early in the boot In-reply-to: Your message of "Tue, 16 Jul 2002 23:03:12 PDT." <3D3508A0.B7D12818@mindspring.com> Date: Wed, 17 Jul 2002 09:57:41 -0700 From: Bakul Shah Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I believe setting DISABLE_PSE in the config file and rebuilding > will make this go away. Terry, thanks for the suggestion but that didn't do it. Time to review recent changes and single step the kernel. BTW, how do you stop the kernel before it panics? It panics so early that there is no time for sending a break. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message