From owner-freebsd-bugs  Sat Apr 26 16:20:02 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA16084
          for bugs-outgoing; Sat, 26 Apr 1997 16:20:02 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA16072;
          Sat, 26 Apr 1997 16:20:01 -0700 (PDT)
Date: Sat, 26 Apr 1997 16:20:01 -0700 (PDT)
Message-Id: <199704262320.QAA16072@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Don Schmidt <yensid@coke.imsa.edu>
Subject: Re: kern/3391: Pentium optimizations in default bootdisk breaks some 486's 
Reply-To: Don Schmidt <yensid@coke.imsa.edu>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/3391; it has been noted by GNATS.

From: Don Schmidt <yensid@coke.imsa.edu>
To: Bruce Evans <bde@zeta.org.au>
Cc: yensid@imsa.edu, FreeBSD-gnats-submit@FreeBSD.org,
        yensid@postoffice.imsa.edu
Subject: Re: kern/3391: Pentium optimizations in default bootdisk breaks some 486's 
Date: Sat, 26 Apr 1997 18:12:54 -0500

 In message <199704260740.RAA30350@godzilla.zeta.org.au>, Bruce Evans writes:
 >>>>	On all current boot disks, on certain 486's (mine, at least)
 >>>...
 >>>This can't have anything to do with i586 optimizations.  There are no i586
 
 >Also a CPU mixup? :-)  i586 optimizations are not used on 486's.
 >
 >This decides whether the i586 copying optimizations are used.  They are
 >only used on i586's, and then only if they aren't disabled.  There is no
 >need to recompile without I586_CPU to control them.  So if recompiling
 >without i586_CPU makes a difference, then the problem must have nothing
 >to do with known problems with i586 optimizations :-).
 
 	Again, when I first asked for help, It was indicated to me that
 "586 optimizations caused problems on some 486's" and that I could fix the
 problem by passing the flag 0x1 to the npx driver, which appears to disable
 the bzero optimizations.  I can't do that, though, because my screen gets
 mucked up before I can get to the configuration screen.
 
 	Assuming that this isn't the problem, though, would you have any
 suggestions as to what is wrong?  I just want to be able to boot! :)
 Thanks!
 
 ===============================================================================
 Don Schmidt					  Network Systems Administrator
 yensid@imsa.edu				      Illinois Math and Science Academy
 ----------You can build a Mainframe from the things you find at home!----------