From owner-freebsd-alpha Thu Jan 10 21:14: 5 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from madeline.boneyard.lawrence.ks.us (madeline.boneyard.lawrence.ks.us [24.124.26.25]) by hub.freebsd.org (Postfix) with ESMTP id 67FD637B402 for ; Thu, 10 Jan 2002 21:14:01 -0800 (PST) Received: from madeline.boneyard.lawrence.ks.us (madeline.boneyard.lawrence.ks.us [24.124.26.25]) by madeline.boneyard.lawrence.ks.us (8.11.1/8.11.1) with ESMTP id g0B5DxF48352 for ; Thu, 10 Jan 2002 23:14:00 -0600 (CST) (envelope-from bsd-alpha@boneyard.lawrence.ks.us) Date: Thu, 10 Jan 2002 23:13:59 -0600 (CST) From: "Stephen D. Spencer" To: freebsd-alpha@freebsd.org Subject: /boot/loader failure 4.5-PR Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Resetting I/O buses... ewa0: link up : Negotiated 100BaseTX: full duplex (boot dqa0.0.0.13.0 -flags a) block 0 of dqa0.0.0.13.0 is a valid boot block reading 15 blocks from dqa0.0.0.13.0 bootstrap code read in base = 200000, image_start = 0, image_bytes = 1e00 initializing HWRPB at 2000 initializing page table at 17f3e000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code Loading /boot/loader - halted CPU 0 halt code = 2 kernel stack not valid halt PC = 545532080018 boot failure This is a DS10/466 running -stable as of today. This issue started, I believe, between the 4th and 7th of January. Monday's build was the first to exhibit this behavior. I was able to recover by installing the boot programs from a 4.4-R disk. There are no compiler related options defined in /etc/make.conf. The cputype was left at the default (ev4) on a second build/install cycle to verify that nothing goofy was happening there. Please let me know if there is any other information I can provide. This is easily replicable. On another topic, I am looking for any documentation that might assist me in understanding the source and [ more specific ] nature of these unaligned access errors that are disturbingly cropping up in base OS utilities such as ifconfig. I've traced it down to where it's running a logic operator (if) on the if_msghdr struct called ifm in the ifconfig.c status(). Now, I understand machine language concepts (ex. w/ 6502, 8088 and Z80); how- ever I am not familar with the alpha instructions. I think I understand the nature of these misaligned access errors (all memory access must occur on a 64-bit word boundry?). Is it a matter of hunting down the offending variable in the faulty data structure and widening its data type? Regards, Stephen -- Stephen Spencer UNIX Systems Administrator Electrical Engineering and Computer Science Dept. University of Kansas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message