Re: port-amd64/45197: failing to load secondary boot

[dieter roelants <dieter.NetBSD%pandora.be@localhost>]

The following reply was made to PR port-amd64/45197; it has been noted by GNATS.

From: dieter roelants <dieter.NetBSD%pandora.be@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: Joerg Sonnenberger <joerg%netbsd.org@localhost>
Subject: Re: port-amd64/45197: failing to load secondary boot
Date: Sun, 26 Feb 2012 19:14:29 +0100

 On Wed, 10 Aug 2011 22:55:04 +0000 (UTC)
 Dan McMahill <dmcmahill%NetBSD.org@localhost> wrote:
 
 >  Then once I found I could boot using the 5.1 CD, I booted to sysinst and
 >  reinstalled the boot blocks on the hard drive and now can boot from the
 >  hard drive.  I suppose this means either boot, installboot, or
 >  bootxx_ffsv1 is broken as opposed to something else. (hardware for example)
 
 I have what looks like the same problem on my oldish server. Both
 bootxx_ffsv1, and boot are affected, installboot is not. I narrowed the
 start of it down to last june 16th, probably one of the libsa commits:
 
        Add an optional MD calling convention flag for use in libsa
        when space optimisation is critical. Use this on i386 to switch
        to register passing calling convention for the file system
        entry points and most assembler call backs that have to
        preserve at least 3 registers.
 
 Dan, did you ever find/have luck with the BIOS update? I also have:
 
 cpu0 at mainbus0 apid 0: AMD Opteron(tm) Processor 244, id 0xf5a
 cpu0: erratum 101 present
 cpu0: WARNING: errata present, BIOS upgrade may be
 cpu0: WARNING: necessary to ensure reliable operation
 
 kind regards
 dieter