Date: Mon, 4 Nov 2002 16:32:30 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: freebsd-alpha@freebsd.org Subject: Borked loader Message-ID: <20021104053230.GA75624@server.c18609.belrs1.nsw.optusnet.com.au>
next in thread | raw e-mail | index | archive | help
I'm trying to upgrade a 6-month old -stable on an AlphaServer 400 to -stable from yesterday but the new /boot/loader dies. I've looked at changes since then but nothing seems to affect the loader. The new world was cross-built on a x86 box. This is the first time I've done that, so it could theoretically be a problem with cross- building but I'd need another day to build world on as AS400. I've repeated the cross-build and got a /boot/loader that is identical apart from the build time. Any suggestions? >>>show dev dka0.0.0.6.0 DKA0 RZ26N 0568 dka100.1.0.6.0 DKA100 RZ28M 0568 dka400.4.0.6.0 DKA400 RRD45 0436 dva0.0.0.0.1 DVA0 ewa0.0.0.11.0 EWA0 00-00-F8-22-E2-1B pka0.7.0.6.0 PKA0 SCSI Bus ID 7 >>>b dka100 -fl s (boot dka100.1.0.6.0 -flags s) block 0 of dka100.1.0.6.0 is a valid boot block reading 14 blocks from dka100.1.0.6.0 bootstrap code read in base = 1f2000, image_start = 0, image_bytes = 1c00 initializing HWRPB at 2000 initializing page table at 1e4000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code Console: SRM firmware console VMS PAL rev: 0x1000000010538 OSF PAL rev: 0x100000002012e Switch to OSF PAL code succeeded. FreeBSD/alpha SRM disk boot, Revision 1.0 (root@server.c18609.belrs1.nsw.optusnet.com.au, Sun Nov 3 12:19:16 EST 2002) Memory: 163840 k \ halted CPU 0 halt code = 2 kernel stack not valid halt PC = 144e4 >>> Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021104053230.GA75624>