On Wed, Mar 24, 2004 at  2:49pm, sgimips NetBSD list wrote:
> Subject: Re: Newer kernels not booting all the way & maximum RAM problems

it turns out that the releng snapshot dated 20040105 is actually a Jan 26 
build:

NetBSD 1.6ZG (INSTALL32_IP3x) #0: Mon Jan 26 05:44:57 UTC 2004
        cyber@tgm.netbsd.org:/autobuild/HEAD/sgimips/OBJ/autobuild/HEAD/src/sys/arch/sgimips/compile/INSTALL32_IP3x

Thus, the break must have happened between the Jan 26 releng build and the Jan 28
releng build (Which actually says Jan 31 in the kernel?!?):

NetBSD 1.6ZI (INSTALL32_IP3x) #0: Sat Jan 31 06:04:41 UTC 2004
        cyber@tgm.netbsd.org:/autobuild/HEAD/sgimips/OBJ/autobuild/HEAD/src/sys/arch/sgimips/compile/INSTALL32_IP3x

Don't know what's happened to the timestamps on releng, but the 1.6ZG kernel boots
both for INSTALL and GENERIC IP32, and the 1.6ZI kernels do not.

-scott

> On Wed, Mar 24, 2004 at 11:50am, Rafal Boni wrote:
> > Subject: Re: Newer kernels not booting all the way & maximum RAM problems
> 
> > In message <20040324051226.GB23417@seekingfire.com>, you write: 
> > 
> > -> 1. I'm unable to boot any kernel from releng.netbsd.org newer than the
> > -> 20040103 build. They all boot, to an extent, but freeze at this point: 
> > -> 
> > -> (snip)
> > -> root file system type: ffs
> > -> Tue Mar 23 22:59
> > 
> > ENOCLUE here.  My O2 hasn't been on in entirely too long...
> 
> I can confirm that all the snapshots beginning with the releng Jan 28 snapshots
> will not boot on the O2 (both R5K and R10K).  The INSTALL kernels hang in the
> middle of the "Terminal type?" message, and the GENERIC kernels hang in the
> middle of the "Enter pathname of shell or RETURN for /bin/sh:" message.
> I've built a kernel cvs'd today and the problem still exists.  the Jan 5 releng
> build is the last working snapshot there.
> 
> So, something committed between the Jan 5 and the Jan 28 builds has broken the
> O2/IP32 support.
> 
> -scott
>-- End of excerpt from sgimips NetBSD list