Thanks, Warner and Donn.  I have been successfully building a new world and
kernel every day, except with the latest perl problems the last two days.
Today's world is in process and looks like it is going to be successful.
This means that everything is up to date.   I haven't been able to boot any
of the kernels since the configuration changes.  My old, as
suggested in the changes email, is keeping me going. I'm beginning to think
about and look for conflicts from very old current stuff that may be
obsolete.  (I've been running current on this machine for two years with a
daily cvsup and make world.)  I am also thinking that this may be processor
specific.  The machine is an older K6-2 at 300 Mhz.

I haven't optimized the compilation.  As I mentioned before, I wish that
were the problem.

Thanks very much for the suggestions and help.

Donn Miller wrote:

> On Wed, 28 Jun 2000, Warner Losh wrote:
> > In message <[EMAIL PROTECTED]> Edwin Culp writes:
> > : int=0000000d err=00000000 eft=00010046 eip=000092eb
> > : eax=000000fb ebx=00000000 ecx=00000152 edx=000003f6
> > : esi=000fbc92 edi=000f0000 ebp=000017b4 esp=000017b4
> > : cs:eip=0f 32 89 45 1c 89 55 14-46 eb cf 80 65 31 fd eb
> > : ss:esp=08 00 00 00 1c 9c 00 00-fe 0e 00 00 d4 17 00 00
> > : System halted
> > :
> > : I copied this manually since I don't have a console on the laptop.
> >
> > I'd try booting the old kernel and seeing if doing a completely clean
> > build fixes this.  I'd also try to reboot after power off.
> It looks like the optimization bug that's been biting kernel builds
> lately.  When Peter Wemm made the overhaul to the kernel config, strange
> things started happening when optimization higher than -O was used to
> build the kernel.  For example, I got a Fatal Trap 12 immediately after
> the probe for available memory.  I was using -Os to compile my kernel at
> the time.  Backing down to -O for kernel builds solved this, and boots
> proceeded normally.
> - Donn
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to