From owner-freebsd-alpha Fri Jan 11 10:11: 2 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 2A10237B41B for ; Fri, 11 Jan 2002 10:10:47 -0800 (PST) Received: (qmail 14755 invoked from network); 11 Jan 2002 18:10:46 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 11 Jan 2002 18:10:46 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 11 Jan 2002 10:10:12 -0800 (PST) From: John Baldwin To: "Stephen D. Spencer" Subject: RE: /boot/loader failure 4.5-PR Cc: freebsd-alpha@FreeBSD.ORG 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 On 11-Jan-02 Stephen D. Spencer wrote: > On Fri, 11 Jan 2002, John Baldwin wrote: > >> > [...] >> > halt code = 2 >> > kernel stack not valid halt >> > PC = 545532080018 >> > boot failure >> >> Works fine on my DS20 here: >> >> FreeBSD/alpha SRM disk boot, Revision 1.0 >> (john@sema.baldwin.cx, Wed Jan 9 11:58:18 PST 2002) >> Memory: 1048576 k >> Loading /boot/defaults/loader.conf >> /kernel data=0x2ad7d8+0x23e02 syms=[0x8+0x39f90+0x8+0x2a0f5] >> >> Your PC is way wacked out. What's your SP and RA? ("e sp", "e ra" at the >> SRM >> prompt) >> > > Just for kicks, I rolled my source tree back to Sept. 16 (the day the 4.4-R > ISO's were created) and recompiled /boot/loader. It still exhibits the > same problem. > > Here is the information you requested: > > PC = 545532080018 > boot failure >>>>e sp > gpr: 1E ( R30) 0000000020044000 >>>>e ra > gpr: 1A ( R26) 000000002000073C > > I'm going to take a hard look at the build process for the loader binary > to try to ascertain what might be borked on this box. Are there any known > issues with using CPU flags for compiling world (such as ev6 or ev56) When > I rebuilt this system yesterday, it was done with a compiler/world that > was compiled with it set to ev6 (even though the build was ev4) Hmm, none that I know of. Can you do this, can you build a debug loader (clean sys/boot and then compile it with -g in CFLAGS). Strip the loader before you install it though, and then repeat this and get the ra again (ra is the return address), then reboot the system, fire up gdb on the debug loader binary with all the symbols, and do 'l *0x'. For example, in this case you would do 'l *0x2000073C' except that your loader binary probably doesn't have symbols. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message