Date: Mon, 11 Sep 95 22:07:21 EDT From: jleppek@suw2k.ess.harris.com (James Leppek) To: freebsd-current@freefall.FreeBSD.org, dyson@freefall.FreeBSD.org Subject: Re: Progress so far on the Sig-11 problem Message-ID: <9509120207.AA03373@borg.ess.harris.com>
next in thread | raw e-mail | index | archive | help
I have a 16meg 486 system and all I need to do is start X. all xterms after initial startup die with sig 11 then after a few tries the xterms start to work but xarchie keeps faulting sig 6. It may be that all X and X apps will need to be rebuilt...ouch I realize everyone using current is definitely at risk but I do not think there is any question now that current is very broken. Well, maybe this message/thread is enough since everyone supping current should be reading this list :-) It looks like the packaged version of xarchie (dated may 16) will always sig 6 for me. You may want to try it to see if it helps isolate things. Jim Leppek > From owner-freebsd-current@freefall.freebsd.org Mon Sep 11 18:40:32 1995 > Date: Sun, 10 Sep 1995 17:51:33 -0700 > From: John Dyson <dyson@freefall.freebsd.org> > To: current@freebsd.org > Subject: Progress so far on the Sig-11 problem > Sender: current-owner@freebsd.org > > > I am having problems reproducing the problem. It takes quite-a-while to > get it to happen, and only appears when I am running in less than 8MB. > I have verified that the pre-zero code is not the culprit (but have done some > minor cleanups.) Another major change is that the original vnode_pager_haspage > was not correct (on the *very* conservative side) on the estimate of the > cluster size. That problem was *fixed* with another bug being introduced. > The bug has been fixed in -current, but I am not sure that the Sig-11 > problems were related. I am still searching for it... > > John > dyson@freebsd.org >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9509120207.AA03373>