Date: Mon, 9 Nov 1998 19:19:54 +0000 (GMT) From: Phillip Salzman <psalzman@gamefish.pcola.gulf.net> To: "David E. Cross" <crossd@cs.rpi.edu> Cc: Archie Cobbs <archie@whistle.com>, Eivind Eklund <eivind@yes.no>, jfieber@indiana.edu, current@FreeBSD.ORG Subject: Re: The infamous dying daemons bug Message-ID: <Pine.BSF.4.05.9811091907350.7784-100000@gamefish.pcola.gulf.net> In-Reply-To: <Pine.SGI.4.05.9811091124580.5731-100000@o2.cs.rpi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm having a problem that I believe is related to this. Any kernel above 3.0-RELEASE does not work correctly. Things happen, such as fsck dying on signal 11 -- other things on signal 6. X doesn't start, the computer locks up when I try. I've limited the commit that caused this to sometime around the 3.0-RELEASE tag. I'm sure some VM code has been commited around that time... I'm going to search it more. Right now i'm living with -BETA -- Phillip Salzman On Mon, 9 Nov 1998, David E. Cross wrote: > > > > Eivind Eklund writes: > > > > Does this happen to everyone, I personally have *never* seen it happen, > > > > and I have run quite a few systems run with full memory utilization. > > > > > > No. Unfortunately, we've not found any (or I at least don't know of > > > any) common factors between all the machines that have this problem. > > > > Has the use of memory mapping been ruled out as a possible common factor? > Maybe if someone who is having this problem could donate the machine to a > core member? > > -- > David Cross > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9811091907350.7784-100000>