PROBLEM: (82241, none) (PATCH ID: OSF510-036)
********
The problem corrected by this patch manifests itself only when an
attempt is made to boot a machine from a RIS/BOOTP server.
The RIS/BOOTP client may in some cases appear to load the
UNIX image but hang early on in the boot cycle.  Specifically, these
messages will appear:
>>>b ewb0

System will be reset prior to boot.

ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.
ef.ee.ed.ec.eb.ea.e9.f4.e8.e7.e6.e5.e4.
Digital AlphaStation 500/333
Console V7.2-2 Apr  4 2000 17:17:43

CPU 0 booting

(boot ewb0.0.0.12.0 -flags A)

Trying BOOTP boot.

Broadcasting BOOTP Request...
Received BOOTP Packet File Name is: /usr/tmp/vmunix.boot
local inet address: 16.140.32.113
remote inet address: 16.140.32.161
TFTP Read File Name: /usr/tmp/vmunix.boot
netmask = 255.255.255.0
Server is on same subnet as client.
......................................
.............................................
..................................
........................
bootstrap code read in
base = 14a000, image_start = 0, image_bytes = 8c6950
initializing HWRPB at 2000
initializing page table at 13c000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

Secondary boot program - Thursday September 14, 2000

Loading vmunix ...
Loading at 0xffffffff00000000

Sizes:
text =  7107200
data =  1971920
bss  =  2314608
Starting at 0xffffffff0000f780

Broadcasting BOOTP Request

(the system will hang at this point)

What should appear instead at this point is
 the normal UNIX boot banner.


This problem is more likely to be seen on faster processors (better
than 700MHz), and then only when attempting to boot such a machine
via RIS/BOOTP with a V5.1 kernel image.