From owner-freebsd-current Wed Jul 17 11:36:31 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 E612137B400 for ; Wed, 17 Jul 2002 11:36:28 -0700 (PDT) Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4934743E64 for ; Wed, 17 Jul 2002 11:36:28 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0460.cvx22-bradley.dialup.earthlink.net ([209.179.199.205] helo=mindspring.com) by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17Uteu-0000Mr-00; Wed, 17 Jul 2002 11:36:21 -0700 Message-ID: <3D35B8F7.9915A14D@mindspring.com> Date: Wed, 17 Jul 2002 11:35:35 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Szilveszter Adam Cc: freebsd-current@FreeBSD.ORG Subject: Re: Interesting panic very early in the boot References: <3D3508A0.B7D12818@mindspring.com> <200207171657.MAA28965@glatton.cnchost.com> <20020717173822.GB1068@fonix.adamsfamily.xx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Szilveszter Adam wrote: > 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... My bet on the root cause, if I am correct, means that if you change the amount of physical RAM installed in the machine, the problem will go away, and that the problem is probably rare because it depends on certain things that are more complicated, after Matt's changes after my complaints about machdep.c reservations on large memory machines, as the amount of physical RAM approaches the size of the address space. My suggestion for DISABLE_PSE was intended to mask the problem, not fix it, because the root problem I was thinking of isn't really related to that. That change masking the problem would have been information. The change *not* masking the problem is *not* information; i.e. the masking as a side effect would have been prrof of the theory, but lack of masking doesn't disprove the theory. Finding a gremlin body squished in the gears is proof of gremlins, but not finding one doesn't prove the non-existance of gremlins... ;^). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message