(was Re: HEADS UP! MAJOR change to FreeBSD/sparc64) Boot failure on rebuild

On Thu, Mar 11, 2004 at 09:05:47AM -0800, Marcel Moolenaar wrote:
> On Thu, Mar 11, 2004 at 10:56:39AM -0600, Tillman Hodgson wrote:
> > On Wed, Mar 10, 2004 at 01:00:07PM -0500, Garance A Drosihn wrote:
> > > 
> > > The long-threatened change for FreeBSD/sparc64 has now been
> > > committed.  This changes time_t to be a 64-bit quantity, the
> > > same as it is for the AMD64 and IA64 architectures.  People
> > > running FreeBSD/sparc64 *will* have to read the UPDATING.64BTT
> > > file for instructions on how to safely build and install this
> > > change.
> > 
> > For folks that are already using 64bTT, are any special instructions
> > required to going back to following -current (which now has the change
> > committed)?
> 
> No. Just double-check that the local patch to _types.h doesn't
> create a conflict when you sync your tree.

Ok, I cvsup'ed, 'make buildworld', 'make buildkernel', 'mergemaster -p',
'make installworld', 'make installkernel' and 'mergemaster'.  And ...
hrrm. It did not Go As Planned:

FreeBSD 5.2-CURRENT #0: Thu Mar 11 18:44:21 CST 2004
    toor_at_caliban.rospa.ca:/usr/obj/usr/src/sys/CALIBAN
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0506000.
Timecounter "tick" frequency 360000000 Hz quality 0
real memory  = 402653184 (384 MB)
avail memory = 376864768 (359 MB)
cpu0: Sun Microsystems UltraSparc-IIi Processor (360.00 MHz CPU)
nexus0: <OpenFirmware Nexus device>
cpu0 on nexus0
Timecounters tick every 0.976 msec
ipfw2 initialized, divert enabled, rule-based forwarding enabled,
default to accept, logging limited to 5 packets/entry by default
IPsec: Initialized Security Association Processing.
IP Filter: v3.4.31 initialized.  Default = pass all, Logging = enabled
Mounting root from ufs:/dev/ad0a
setrootbyname failed
ffs_mountroot: can't find rootvp
Root mount failed: 6
Manual root filesystem specification:
  <fstype>:<device>  Mount <device> using filesystem <fstype>
                       eg. ufs:/dev/da0a
  ?                  List valid disk boot devices
  <empty line>       Abort manual input
mountroot> ?
List of GEOM managed disk devices:

^^^
Blank list, naturally.

It's a good thing I have a serial-over-ethernet terminal server :-)

Any suggestions? This looks like a geom boot disk thing rather than a
64bTT thing, but what with the timing I thought I'd better explore all
scenarios.

-T


-- 
 function createLimmerick(){ var scanning=terriblySlick; if(lines==5)
&&rhyme=="live" do(laugh(); performNewTrick();)}
	- Geek limerick from BBSpot