Re: What exactly does this mean? (ld: size of symbol changed)
On Thu, Aug 10, 2000 at 04:12:23PM -0400, James Housley wrote:
> My guess is that you (or someone) have redefined the function warn().
Good guess, but no cigar :-)
warn is defined once in libc, and once in errwarn.c. This is OK
normally, but I've screwed up something in the build.
> errwarn.c is dhclient. Are you compiling dhclient from
> /usr/src/contrib/isc-dhcp instead of /usr/src/sbin/dhclient? The second
> is the correct locaion.
src/sbin/dhclient as I mentioned in my first message.
Could `CFLAGS+= -I${.OBJDIR}' in src/lib/libc/net/Makefile.inc cause me
to lose in this fashion? If so, how else might I get to a generated file
(i.e. header output from yacc)?
Thanks,
--
Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: What exactly does this mean? (ld: size of symbol changed)
"Jacques A. Vidrine" wrote: > > I hope someone might be able to clue me in. I'm having a hard time tracking > this down. I've added some code to libc, and while building the world I get > this misery in src/sbin/dhclient: > > cc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes >-I/usr/src/sbin/dhclient/../../contrib/isc-dhcp >-DCLIENT_PATH='"PATH=/sbin:/bin:/usr/sbin:/usr/bin"'-static -o dhclient clparse.o >dhclient.o alloc.o bpf.o conflex.o convert.o dispatch.o errwarn.o ethernet.o hash.o >icmp.o inet.o inet_addr.o memory.o nit.o options.o packet.o parse.o print.o raw.o >socket.o tables.o tree.o upf.o > /usr/lib/libc.a(err.o): In function `warn': > err.o(.text+0x1e0): multiple definition of `warn' > errwarn.o(.text+0xd8): first defined here > /usr/libexec/elf/ld: Warning: size of symbol `warn' changed from 141 to 30 >in err.o > *** Error code 1 > My guess is that you (or someone) have redefined the function warn(). errwarn.c is dhclient. Are you compiling dhclient from /usr/src/contrib/isc-dhcp instead of /usr/src/sbin/dhclient? The second is the correct locaion. Jim -- Studies show that 1 out of every 4 Americans suffer some form of mental illness. So look at your three best friends, if they are okay it is YOU! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
What exactly does this mean? (ld: size of symbol changed)
I hope someone might be able to clue me in. I'm having a hard time tracking this down. I've added some code to libc, and while building the world I get this misery in src/sbin/dhclient: cc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp -DCLIENT_PATH='"PATH=/sbin:/bin:/usr/sbin:/usr/bin"'-static -o dhclient clparse.o dhclient.o alloc.o bpf.o conflex.o convert.o dispatch.o errwarn.o ethernet.o hash.o icmp.o inet.o inet_addr.o memory.o nit.o options.o packet.o parse.o print.o raw.o socket.o tables.o tree.o upf.o /usr/lib/libc.a(err.o): In function `warn': err.o(.text+0x1e0): multiple definition of `warn' errwarn.o(.text+0xd8): first defined here /usr/libexec/elf/ld: Warning: size of symbol `warn' changed from 141 to 30 in err.o *** Error code 1 I guess I just don't understand exactly what the linker is trying to tell me. BTW, this is ~ 4.1-RELEASE. Thanks, -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What, exactly, does this mean?
On Sun, 11 Jun 2000, Kris Kennaway wrote: > On Sun, 11 Jun 2000, Dave Hayes wrote: > > > Kelly Yancey <[EMAIL PROTECTED]> writes: > > > If you up PMAP_SHPGPERPROC, you increase the number of > > > pv_entries created at boot time. However, I am not informed enough > > > to say how high you can safely increase PMAP_SHPGPERPROC. > > > > What is the upper bound related to? What are the dangers in increasing > > it too much? > > At a guess, running out of kernel memory. > > Kris > Yep. Dave, the default value is 200, perhaps you can try 'easing' it up by 25 or so at a time until you stop seeing the messages. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What, exactly, does this mean?
On Sun, 11 Jun 2000, Dave Hayes wrote: > Kelly Yancey <[EMAIL PROTECTED]> writes: > > If you up PMAP_SHPGPERPROC, you increase the number of > > pv_entries created at boot time. However, I am not informed enough > > to say how high you can safely increase PMAP_SHPGPERPROC. > > What is the upper bound related to? What are the dangers in increasing > it too much? At a guess, running out of kernel memory. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What, exactly, does this mean?
Kelly Yancey <[EMAIL PROTECTED]> writes: > If you up PMAP_SHPGPERPROC, you increase the number of > pv_entries created at boot time. However, I am not informed enough > to say how high you can safely increase PMAP_SHPGPERPROC. What is the upper bound related to? What are the dangers in increasing it too much? -- Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED] >>> The opinions expressed above are entirely my own <<< "What's so special about the Net? People -still- don't listen..." -The Unknown Drummer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What, exactly, does this mean?
On Sat, 10 Jun 2000, Dave Hayes wrote: > [ Please CC me on responses. Thank you. ] > > On 3.3-STABLE the following kernel message appeared recently: > >pmap_collect: collecting pv entries -- suggest increasing PMAP_SHPGPERPROC > > Is there a place I can get more specific information as to what this > means, so I can perhaps embark on the road to a correct solution > and/or interpretation of what happened? Alternatively, can someone > explain? > Sounds like you are running some programs that make heavy use of shared memory. Do as it says. Basically, pv_entries map logical address to physical addresses. With lots of shared memory segments, lots of pv_entries exist to map all of the per-process address mappings to the physical memory backing it. There are only a certain number of pv_entries that exist in the kernel, and you are running out (actually, you get this warning when over 90% of them are used). If you up PMAP_SHPGPERPROC, you increase the number of pv_entries created at boot time. However, I am not informed enough to say how high you can safely increase PMAP_SHPGPERPROC. > On a related note, I took a look at the code and saw the following > disturbing thing: > [code snipped] > > The machine in question has 57 days of uptime. This code appears to > imply that I only get to see this 5 times during this period. :) How many times do you need to be told? :) -- Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
What, exactly, does this mean?
[ Please CC me on responses. Thank you. ]
On 3.3-STABLE the following kernel message appeared recently:
pmap_collect: collecting pv entries -- suggest increasing PMAP_SHPGPERPROC
Is there a place I can get more specific information as to what this
means, so I can perhaps embark on the road to a correct solution
and/or interpretation of what happened? Alternatively, can someone
explain?
On a related note, I took a look at the code and saw the following
disturbing thing:
void
pmap_collect() {
...
static int warningdone=0;
...
if (warningdone < 5) {
printf("pmap_collect: collecting pv entries -- suggest
increasing PMAP_SHPGPERPROC\n");
warningdone++;
}
The machine in question has 57 days of uptime. This code appears to
imply that I only get to see this 5 times during this period. :)
Was this intentional?
--
Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED]
>>> The opinions expressed above are entirely my own <<<
A person being delivered from the danger of a fierce lion does not object
whether this service is performed by unknown or illustrious individuals.
Why, therefore, do people seek knowledge from celebrities?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
