Hi!

After being away from my favourite uVAX II, recently I tried to upgrade
from 1.0A to 1.2A.

The machine was running 1.0A fine (couple of panic daily :-).

I've downloaded the latest binaries, and first tried to boot a
new kernel. My TK50 is broke, so i copied the tk-50 miniroot
to the swap partition and copied the new /boot and /netbsd.

After booting the new kernel:

	---------------> Visual console copy <------------
KA 630-A V1.3

netbsd
621568+32768+85720 start 0x8b388
Copyright ...

NetBSD 1.2_ALPHA (GENERIC) #1: Thu Jun 20 17:27:54 MET DST 1996
	ragge@urgoriyf:/usr/src/sys/arch/vac/compile/GENERIC

realmem = 13630464
availmem = 10558464
using 665 buffers containing 680960 bytes of memory
decplane0 (root)
cpu0 at backplane0: MicroVAX II
sbi0 at backplane0 Q22: 
uba0 at sbi0 tr0
uda0 at uba0 csr 172150 vec 774, ipl 17
uda0: version 9 model 7
uda0: dma burst size set to 4
ra1 at uda0 slave1: rd53, size=263008 sectors
qe0 at uda0 csr 174440 vec 770, ipl 17
qe0: DEQUNA, Hardware address 08:00:2b:05:97:54
root device? ra1a

Segv in kernel mode: rv1

P0BR	8060f000	P1BR	7fe0e400	P0LR	220	P1LR	1fff00
KSP	82da1330	ISP	80142aec	USP	7fffde3c
R0	0		R1	81ca8140	R2	81cafa00	R3	81ca81a0
R4	ffffffff	R3	15		R6	81ca81a0	R7	14
R8	80098cac	R9	81cafa00	R10	82da1360	R11	82da13b4
FP	80142b88	AP	80142b9c	PC	80015863	PSL	4150004
panic: trap: adr0
stopped at 0x80091a80: bbs $6,60(r6),0x80091a88
db> trace
db_stack_trace_cmd -addr 80091a80, have_addr 0, count ffffffff, modif 80142908
db>

         -------------------------------------------------

In one word, I can't boot this kernel, but can boot the old one.

Should I upgrade the userland binaries? I suspect that shouldn't cause
a panic.

Any help appreciated.


Thanks,
	
	szabolcs