From owner-freebsd-current Wed Jul 17 10:38:14 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 DE03B37B400 for ; Wed, 17 Jul 2002 10:38:11 -0700 (PDT) Received: from mx2.datanet.hu (mx2.datanet.hu [194.149.13.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56BD843E42 for ; Wed, 17 Jul 2002 10:38:11 -0700 (PDT) (envelope-from sziszi@bsd.hu) Received: from fonix.adamsfamily.xx (nilus-667.adsl.datanet.hu [195.56.50.159]) by mx2.datanet.hu (DataNet) with ESMTP id 1BCDB5982 for ; Wed, 17 Jul 2002 19:38:10 +0200 (CEST) Received: from fonix.adamsfamily.xx (localhost [127.0.0.1]) by fonix.adamsfamily.xx (8.12.5/8.12.5) with ESMTP id g6HHcN6c008249 for ; Wed, 17 Jul 2002 19:38:23 +0200 (CEST) (envelope-from sziszi@bsd.hu) Received: (from cc@localhost) by fonix.adamsfamily.xx (8.12.5/8.12.5/Submit) id g6HHcNKi008248 for freebsd-current@FreeBSD.ORG; Wed, 17 Jul 2002 19:38:23 +0200 (CEST) X-Authentication-Warning: fonix.adamsfamily.xx: cc set sender to sziszi@bsd.hu using -f Date: Wed, 17 Jul 2002 19:38:22 +0200 From: Szilveszter Adam To: freebsd-current@FreeBSD.ORG Subject: Re: Interesting panic very early in the boot Message-ID: <20020717173822.GB1068@fonix.adamsfamily.xx> Mail-Followup-To: Szilveszter Adam , freebsd-current@FreeBSD.ORG References: <3D3508A0.B7D12818@mindspring.com> <200207171657.MAA28965@glatton.cnchost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200207171657.MAA28965@glatton.cnchost.com> User-Agent: Mutt/1.5.1i 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 On Wed, Jul 17, 2002 at 09:57:41AM -0700, Bakul Shah wrote: Terry suggested: > > 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. Ok, so it's time to speculate a bit more about this. Although I have been seeing this panic since Sunday, only one other person has reported it so far. Although it may be that this is due to the fact that developers do not run up-to-date -CURRENT and hence do not see problems that are this "new" (and I bet that the tinderbox only tests building, but does not try to actually run the stuff), perhaps there is a different explanation. Bakul mentioned that the panic happens on a PPro. For me, it's a PII. I am using a CPUTYPE setting of "p2" in /etc/make.conf. This gets converted to a "-march=pentiumpro" on the actual compile line. This may be the same for the PPro. This suggests a remote possibility that there might be a problem with this option, so this is the next thing that I am going to test. We'll see... -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message