From owner-freebsd-current Fri Jan 30 05:44:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01186 for current-outgoing; Fri, 30 Jan 1998 05:44:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sphinx.lovett.com (root@sphinx.lovett.com [38.155.241.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA01181; Fri, 30 Jan 1998 05:44:28 -0800 (PST) (envelope-from ade@demon.net) Received: from gorgon.lovett.com [38.155.241.3] (ade) by sphinx.lovett.com with esmtp (Exim 1.82 #1) id 0xyGk7-0000QQ-00; Fri, 30 Jan 1998 07:44:27 -0600 To: dyson@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: Current and X11R6 3.3 get Signal 11 abort Organization: Demon Internet Reply-To: ade@demon.net In-reply-to: Your message of "Fri, 30 Jan 1998 01:54:05 EST." <199801300654.BAA09622@dyson.iquest.net> Date: Fri, 30 Jan 1998 07:44:27 -0600 From: Ade Lovett Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" "John S. Dyson" writes: > >Good!!! It is wise to be prepared to back-off to the latest "stable" -current, >when breakage like I have likely caused, happens!!! Thing is, though. After your suggested boot-time tweak to set vfs.ioopt to 0, I've had no problems with random SIGBUS's, to the extent that I've completely rebuilt a couple of machines (a 96Mb K6/200 and a 128Mb dual-P133) from scratch, including X11 and all the other ports that I use. I notice that recent -current's (I'm using 980127 here) seem to set vfs.ioopt to 0 by themselves (negating the need for the sysctl in /etc/rc) Is this just a kludge to revert back to old (unbroken?) behavior (the previous problematic value was 2)? -aDe -- Ade Lovett, Demon Internet, Austin, Texas.