Date: Mon, 06 May 1996 18:16:24 -0500 From: Randy Terbush <randy@zyzzyva.com> To: davidg@root.com Cc: current@freebsd.org, stable@freebsd.org Subject: Re: MBUFs leaking? Message-ID: <199605062316.SAA09096@sierra.zyzzyva.com> In-Reply-To: davidg's message of Mon, 06 May 1996 13:23:10 -0700. <199605062023.NAA07341@Root.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> Alan Cox writes: > >> > >> > I've had a similar problem. However, I hadn't noticed any correlation > >> > with NMBCLUSTERS. Try rolling back your pmap.c to the -RELEASE version. > >> > That "solved" the problem for me. > >> > >> Are you running with the associated new ld.so ? If not, try installing it > >> instead of backing out pmap.c, > >> > >> michael > > > >I assume this hasn't been commited to -stable? > > > >I'm beginning to think that I need to run -current to get around > >much of the instability I am running into.... > > This is the first I've heard about instability problems with the -stable > pmap.c. You're going to need to provide a lot more information before I'll > be able to diagnose the problem. Also make sure you are running with the most > recent version (1.58.4.3). > I can't be sure it is pmap.c. See my followup debug trace on a system crash from another -stable system. As I mentioned in earlier mail, I have a Tyan 133mhz Pentium with 64 MB RAM that will crash if attempting to run X on a kernel with the NMBCLUSTERS=4096 define. This sounds suspiciously like the problem that ... Date: Mon, 6 May 1996 16:16:37 -0400 (EDT) From: Charles Owens <owensc@enc.edu> To: stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Followup: signal 11 problem solved by yanking DDB! just posted about signal 11's with DDB compiled in. I have also compiled a -g /bin/sh on my system because I was getting coredumps from /bin/sh for no apparent reason compiling some of the ports. Since rebuilding with -g...no dumps... My comment about -current stability stems from my relative newness to the group, and my reading of many Emails from people say "this dongle patch from -current" fixed up my problem...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605062316.SAA09096>