Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 May 2002 16:38:04 +0200
From:      Bernd Walter <ticso@cicely5.cicely.de>
To:        Dag-Erling Smorgrav <des@ofug.org>
Cc:        alpha@FreeBSD.ORG, current@FreeBSD.ORG
Subject:   Re: loader failure
Message-ID:  <20020515143803.GF4401@cicely5.cicely.de>
In-Reply-To: <xzpd6vxzjmb.fsf@flood.ping.uio.no>
References:  <xzpd6vxzjmb.fsf@flood.ping.uio.no>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 15, 2002 at 02:22:04PM +0200, Dag-Erling Smorgrav wrote:
> Trying to boot with a newly-built loader (make world earlier today
> from fresh sources) results in:
> 
> FreeBSD/alpha SRM disk boot, Revision 1.2
> (des@dsa.thinksec.com, Wed May 15 08:01:43 CEST 2002)
> Memory: 262144 k
> Loading /boot/defaults/loader.conf
> /boot/kernel/kernel data=0x283780+0x63670 /
> 
> Hit [Enter] to boot immediately, or any other key for command prompt.
> Booting [/boot/kernel/kernel]...
> Entering /boot/kernel/kernel at 0xfffffc000032e740...
> 
> halted CPU 0
> 
> halt code = 2
> kernel stack not valid halt
> PC = 200000000
> boot failure
> 
> no matter which kernel I try to boot.  Booting my new kernel with the
> old loader (from the DP1 dist) works fine until it tries to start
> init(8):
> 
> spec_getpages: preposterous offset 0xfff80000f4460000
> exec /sbin/init: error 5
> spec_getpages: preposterous offset 0xfff800001426c000
> exec /sbin/init.bak: error 5
> spec_getpages: preposterous offset 0xfff80000c86c0000
> exec /stand/sysinstall: error 5
> init: not found in path /sbin/init:/sbin/oinit:/sbin/init.bak:/stand/sysinstall
> panic: no init
> panic
> Stopped at      Debugger+0x34:  zapnot  v0,#0xf,v0      <v0=0x0>
> 
> Booting DP1's GENERIC with the old loader and the new userland works
> fine.
> 
> Clean tree, no funny stuff in make.conf (unless 'CPUTYPE?=ev56' counts
> as funny stuff)

I'm running 11th May -current with ev4 on NoName and since yesterday
with ev56 on PC164.
No problems with /boot/loader.

On the PC164 I had an dup alloc ufs panic yesterday :(
The filesystem was checked with fsck -y directly after updating.
Debugging options in kernel were disabled.

> <guess type="wild">The loader problem is possibly a compiler issue
> (since DP1 was built with gcc 2.95 while my world was built with 3.1).
> The init problem is probably a UFS2 f*up; the code has obviously not
> been tested on a 64-bit architecture (the UFS2 stuff broke the kernel
> build).</guess>

Some UFS2 preparation parts were commited after I checked out my
source, IIRC also a part influencing loader.

-- 
B.Walter              COSMO-Project         http://www.cosmo-project.de
ticso@cicely.de         Usergroup           info@cosmo-project.de


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020515143803.GF4401>