From owner-freebsd-stable Mon Oct 7 9:40:26 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87DA937B401 for ; Mon, 7 Oct 2002 09:40:25 -0700 (PDT) Received: from zrtps0kn.nortelnetworks.com (zrtps0kn.nortelnetworks.com [47.140.192.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id B246443E77 for ; Mon, 7 Oct 2002 09:40:24 -0700 (PDT) (envelope-from bwithrow@nortelnetworks.com) Received: from zrtps0m6.us.nortel.com (zrtps0m6.us.nortel.com [47.140.192.58]) by zrtps0kn.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g97GeCf01885; Mon, 7 Oct 2002 12:40:12 -0400 (EDT) Received: from tuva.engeast.baynetworks.com (tuva.engeast.baynetworks.com [47.17.140.84]) by zrtps0m6.us.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g97Ge3916110; Mon, 7 Oct 2002 12:40:09 -0400 (EDT) Message-Id: <200210071640.g97Ge3916110@zrtps0m6.us.nortel.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: inbox To: Clive Lin Cc: "Robert Withrow" , freebsd-stable@freebsd.org, tlambert2@mindspring.com Subject: Re: Segfaults and bus errors in 4.6.2? In-Reply-To: Message from Clive Lin of "Thu, 03 Oct 2002 04:33:03 +0800." <20021002203303.GA8608@epaper.eslitebooks.com> Mime-Version: 1.0 Content-Type: text/plain Date: Mon, 07 Oct 2002 12:40:03 -0400 From: "Robert Withrow" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG clive@tongi.org said: :- try :- options DISABLE_PSE :- options DISABLE_PG_G I did so, and launched on several days worth of continuous rebuilding of code and the above seems to have mitigated the problem. I received not a *single* process crash from Wednesday last week to today with the system doing massive "portugrade -f" stuff. It used to get several per hour. Also, apparently, the DISABLE_PG_G option doesn't exist on 4.6.2, at least according to find and grep, so I suspect only the DISABLE_PSE option is needed. :- This reminds me a hot thread on -current several months ago, I went back and read this thread and it sorta petered out before Terry got to explain exactly what the problem is and how DISABLE_PSE mitigates it. Terry? Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message