From owner-freebsd-sparc Sun Dec 23 12:45:35 2001 Delivered-To: freebsd-sparc@freebsd.org Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31]) by hub.freebsd.org (Postfix) with ESMTP id 5A0E037B416 for ; Sun, 23 Dec 2001 12:45:31 -0800 (PST) Received: from esunmail ([129.147.58.121]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA04236 for ; Sun, 23 Dec 2001 13:46:22 -0700 (MST) Received: from smi.sun.com ([127.0.0.1]) by esunmail.central.sun.com (iPlanet Messaging Server 5.1 (built Sep 5 2001)) with ESMTP id <0GOT00E41DJPQ5@esunmail.central.sun.com> for freebsd-sparc@freebsd.org; Sun, 23 Dec 2001 13:43:01 -0700 (MST) Received: from [192.18.102.132] by esunmail.central.sun.com (mshttpd); Sun, 23 Dec 2001 12:43:01 -0800 Date: Sun, 23 Dec 2001 12:43:01 -0800 From: Jamey Wood Subject: Re: compiling a sparc64 kernel? To: freebsd-sparc@freebsd.org Message-id: <1513fe0e8.e0e81513f@smi.sun.com> MIME-version: 1.0 X-Mailer: iPlanet Webmail Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7BIT Content-disposition: inline X-Accept-Language: en Sender: owner-freebsd-sparc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Thanks for the responses and tips. A new cvsup does get things compiling for me, as you both suggested. > > Hmmm, well, it should get quite a bit farther. Can you please > post a > > backtrace of that panic? > > Hmm, indeed. The end=0x0 is puzzling and might cause problems. I'm new at a lot of this, so I hope this is the trace info you guys need (from Thomas's kernel): /kernel data=0x202fb8+0xdfdc0 syms=[0x8+0x36210+0x8+0x2887c] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/kernel]... calling autoload nothing to autoload yet. post autoload jumping to kernel entry at 0xc0030000. sparc64_init: mdp=0xc0344000 kmdp=0xc0344000 boothowto=0 envp=0xc0342000 end=0x0 panic: trap_dmmu_miss: vmspace NULL Debugger("panic") Stopped at 0xc018479c: ta %xcc, 1 db> trace (null)() at 0xc00ca80c (null)() at 0xc018a2e8 (null)() at 0xc0189e78 (null)() at 0xc00310d4 (null)() at 0xc0031300 (null)() at 0xc0183ffc (null)() at 0xc0030034 > A kernel from cvs should work ok, except it won't have support for pci > devices (which I imagine you don't need anyway). You may need to add > support for the openfirmware console to GENERIC, device ofw_console. > If it doesn't drop to the prom, but you don't get any output past the > loader, try that. After adding defice ofw_console, I do get a little output from my custom kernel on boot: /kernel data=0x1352b8+0x4d2f8 syms=[0x8+0x257e8+0x8+0x1b762] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/kernel]... calling autoload nothing to autoload yet. post autoload jumping to kernel entry at 0xc0028000. sparc64_init: mdp=0xc01c6000 kmdp=0xc01c6000 boothowto=0 envp=0xc01c4000 end=0x0 Copyrigh It just hangs right there, however. I tried sening a break, hoping to get to the ok or db prompt to do a trace, but even that didn't work. I had to power-cycle the U1 to get out of that wedged state. And trying it all again gives the same result. > I'm away from home for a few days (holidays, back on the 26th), so > I don't > have full access to my test machine, but I'll do what I can to help. Thanks. I'm just about to leave home for the same period, so I won't be online at all until the 26th. > To do development you really want the code from perforce. I've > requested that > the sparc64 branch be exported via cvsup on cvsup10, but I don't > know how long > that will take to get setup. Okay. I'll keep an eye out for news on this. --Jamey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message