Date: Sun, 27 Oct 2002 08:47:08 -0800 From: Maxime Henrion <mux@freebsd.org> To: Jake Burkholder <jake@locore.ca> Cc: marius@alchemy.franken.de, freebsd-sparc@FreeBSD.ORG Subject: Re: kldxref: bad address Message-ID: <20021027164708.GW26605@elvis.mu.org> In-Reply-To: <20021027114453.G89245@locore.ca> References: <20021027160506.GA30274@newtrinity.zeist.de> <20021027114453.G89245@locore.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Jake Burkholder wrote: > Apparently, On Sun, Oct 27, 2002 at 05:05:06PM +0100, > marius@alchemy.franken.de said words to the effect of; > > > > > While updating from a October 20 -current to a October 27 one I got > > the following error at the installkernel-stage: > > > > ===> xl > > install -o root -g wheel -m 555 if_xl.ko /boot/kernel > > kldxref /boot/kernel > > kldxref: error while reading /boot/kernel/3dfx.ko: Bad address > > kldxref: error while reading /boot/kernel/accf_data.ko: Bad address > > kldxref: error while reading /boot/kernel/accf_http.ko: Bad address > > kldxref: error while reading /boot/kernel/agp.ko: Bad address > > kldxref: error while reading /boot/kernel/aha.ko: Bad address > > kldxref: error while reading /boot/kernel/aio.ko: Bad address > > <...> > > > > This problem persists after the update when installing a kernel > > built the usual way (`config`, `make depend all install`). > > This is a known problem. kldxref is making invalid assumptions about > reading variables from object files before they are relocated. Due to > the way that kldxref was written this is not entirely easy to fix. You can set the NO_XREF variable in your /etc/make.conf to work around this problem until it has been fixed. Cheers, Maxime To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021027164708.GW26605>