Subject: port-alpha/17682: NetBSD/alpha netboot from 1.6_BETA4 fails
To: None <gnats-bugs@gnats.netbsd.org>
From: None <he@netbsd.org>
List: netbsd-bugs
Date: 07/23/2002 01:51:46
>Number:         17682
>Category:       port-alpha
>Synopsis:       NetBSD/alpha netboot from 1.6_BETA4 fails
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    port-alpha-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 22 16:52:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Havard Eidnes
>Release:        NetBSD 1.6_BETA4
>Organization:
>Environment:
	
	
System: NetBSD kveite.urc.uninett.no 1.6_BETA4 NetBSD 1.6_BETA4 (GENERIC.cs20) #0: Tue Jul 23 00:31:11 CEST 2002     he@honey.urc.uninett.no:/usr/src/sys/arch/alpha/compile/GENERIC.cs20 alpha
Architecture: alpha
Machine: alpha
>Description:
	The NetBSD/alpha netboot code fails.	Attemts to use it on
	an Api CS20 resulted in:

P00>>>boot eia0
(boot eia0.0.0.3.1 -flags 0)

Trying BOOTP boot.

Broadcasting BOOTP Request...
Received BOOTP Packet File Name is: /tftpboot/netboot.alpha
local inet address: 158.38.152.46
remote inet address: 158.38.152.30
TFTP Read File Name: /tftpboot/netboot.alpha
netmask = 255.255.0.0
Server is on same subnet as client.
..
bootstrap code read in
base = 200000, image_start = 0, image_bytes = f9f0
initializing HWRPB at 2000
initializing page table at 3ff4c000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

NetBSD/alpha 1.6_BETA4 Network Bootstrap, Revision 1.9
(he@honey.urc.uninett.no, Mon Jul 22 11:46:25 CEST 2002)


halted CPU 0

halt code = 2
kernel stack not valid halt
PC = ffff800000000080
P00>>>

	I also hear that Nathan Williams has experienced similar
	lossage on a recent install of earlier NetBSD/alpha beta
	code.

>How-To-Repeat:
	Try to netboot an alpha system using the 1.6_BETA4 netboot
	binary, watch it fail.

>Fix:
	A possible workaround is to use the netboot code from either
	1.5.2 or 1.5.3.

	Sorry, don't know how to fix this properly.
>Release-Note:
>Audit-Trail:
>Unformatted: