Date: Fri, 30 Jan 1998 16:25:22 -0500 (EST) From: "John S. Dyson" <toor@dyson.iquest.net> To: ade@demon.net Cc: dyson@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Current and X11R6 3.3 get Signal 11 abort Message-ID: <199801302125.QAA03713@dyson.iquest.net> In-Reply-To: <E0xyGk7-0000QQ-00@sphinx.lovett.com> from Ade Lovett at "Jan 30, 98 07:44:27 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Ade Lovett said: > "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)? > Yes. I still am having problems figuring out the trouble. Right now, I am busy working on things specifically for work. (We are using another OS at work also, and it is giving us fits...) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801302125.QAA03713>