It would be great if you guys could re-test with the pmap fix
(/usr/src/sys/i386/i386/pmap.c r1.326). I believe that the pmap
bug was to blame for all of these issues but I need verification before
I have the comfort level necessary to do the MFC I intended to do.
:>Date: Thu, 27 Jun 2002 16:33:36 +0200
:>From: Sheldon Hearn <[EMAIL PROTECTED]>
:>> Wed Jun 26 19:00:10 PDT 2002
:>> /usr/libexec/ld-elf.so.1: /usr/bin/cvs: Shared object has no run-time symbol table
:>I got this testing the RMEM_LIMIT patches, but it only crops up after
:>about an hour of heavy ports building. You'll get this for just any
:>binary that uses mmap().
:I managed to get it while building today's -CURRENT (running -CURRENT
:Backing down to the previous day's kernel allowed me to get through the
:build process. (It had died during "stage 4: populating
:/usr/obj/usr/src/i386/usr/include," and I'm well byond that for the
:present build -- I'm in the install phase.)
:>Unfortunately, I haven't had time to produce any useful debugging
:>information, so I can't be sure it's really the RMEM_LIMIT patches.
:Well, the following is a list of each file under /usr/src/sys that
:changed between the two kernels:
:so I have a fair degree of confidence that changes to some subset of the
:above files was responsible. And this is on a PIII, so the sparc64
:files are unlikely to have been to blame.... :-}
:david (links to my resume at http://www.catwhisker.org/~david)
:David H. Wolfskill [EMAIL PROTECTED]
:Trying to support or use Microsoft products makes about as much sense
:as painting the outside of a house with watercolors.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message