Hi All
OK I completed a new non-SMP kernel (the GENERIC kernel with SMP
commented out)
built using 4.6.2 and ran installkernel KERNCONF=TOMZBOX10. The newer
bootblocks
and loader having been already installed.
The non-smp 5.0-CURRENT kernel chokes at the exact same point as before:
FreeBSD/alp
Hi All
Andrew Gallatin wrote:
> Tom Ponsford writes:
> > Hi All,
> >
> > I'm getting a machine check on my new-toy: an Alphaserver 2100A
4/275 RM.
> >
> > It boots and runs 4.6.2 fine with a single cpu. But after I
supped the
> > current 5.0 sources from
> > 10/29/2002 17:39 and did a b
On 05-Nov-2002 Andrew Gallatin wrote:
>
> Tom Ponsford writes:
> > Hi All,
> >
> > I'm getting a machine check on my new-toy: an Alphaserver 2100A 4/275 RM.
> >
> > It boots and runs 4.6.2 fine with a single cpu. But after I supped the
> > current 5.0 sources from
> > 10/29/2002 17:3
Tom Ponsford writes:
> Hi All,
>
> I'm getting a machine check on my new-toy: an Alphaserver 2100A 4/275 RM.
>
> It boots and runs 4.6.2 fine with a single cpu. But after I supped the
> current 5.0 sources from
> 10/29/2002 17:39 and did a buildworld and a Generic buildkernel, (plus
Hi All,
I'm getting a machine check on my new-toy: an Alphaserver 2100A 4/275 RM.
It boots and runs 4.6.2 fine with a single cpu. But after I supped the
current 5.0 sources from
10/29/2002 17:39 and did a buildworld and a Generic buildkernel, (plus
all the
other steps in UPDATING with the ex
