From owner-freebsd-sparc64@FreeBSD.ORG Fri Aug 19 06:17:32 2005 Return-Path: X-Original-To: freebsd-sparc64@freebsd.org Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA0E016A41F for ; Fri, 19 Aug 2005 06:17:32 +0000 (GMT) (envelope-from john@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 954F743D45 for ; Fri, 19 Aug 2005 06:17:30 +0000 (GMT) (envelope-from john@jnielsen.net) Received: from stealth.local (pcp09741457pcs.goosck01.sc.comcast.net [69.241.83.8]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id j7J6HLsh013968; Thu, 18 Aug 2005 23:17:24 -0700 (PDT) (envelope-from john@jnielsen.net) From: John Nielsen To: pyunyh@gmail.com Date: Fri, 19 Aug 2005 02:17:15 -0400 User-Agent: KMail/1.8.1 References: <200508110931.13802.john@jnielsen.net> <200508180924.59562.john@jnielsen.net> <20050819043026.GC10519@rndsoft.co.kr> In-Reply-To: <20050819043026.GC10519@rndsoft.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508190217.15943.john@jnielsen.net> X-Virus-Scanned: ClamAV 0.85.1/1034/Thu Aug 18 13:07:58 2005 on ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-sparc64@freebsd.org Subject: Re: "fast data access mmu miss" on kernels w/o "makeoptions DEBUG=-g" X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2005 06:17:33 -0000 On Friday 19 August 2005 12:30 am, Pyun YongHyeon wrote: > On Thu, Aug 18, 2005 at 09:24:58AM -0400, John Nielsen wrote: > > On Wednesday 17 August 2005 16:59, Marius Strobl wrote: > > > On Mon, Aug 15, 2005 at 10:42:36AM -0400, John Nielsen wrote: > > > > On Friday 12 August 2005 00:53, Andrew Belashov wrote: > > > > > John Nielsen wrote: > > > > > > Can anyone say why removing "makeoptions DEBUG=-g" from a > > > > > > kernel would make it unreliable? I'm on an Ultra 5, and it's > > > > > > quite stable with either GENERIC or the kernel specified > > > > > > below. However, commenting out the "makeoptions DEBUG=-g" > > > > > > line builds a kernel that boots but then panics right after > > > > > > mounting /: > > > > > > > > > > > > Entropy harvesting: interrupts ethernet point_to_pointpanic: > > > > > > trap: fast data access mmu miss > > > > > > Uptime:2s > > > > > > Dumping 512 MB (2 chunks) > > > > > > > > > > Try to clean rebuild kernel (remove build directory > > > > > /usr/obj/usr/src/sys/KERNCONF or /sys/compile/KERNCONF). > > > > > > > > No change even after a fresh buildworld (using RELENG_6): > > > > > > > > cvsup /etc/supfile-src && rm -r /usr/obj/* && cd /usr/src && make > > > > make && make clean && make cleandir && make cleandir && make > > > > buildworld && make buildkernel && make installkernel && make > > > > installworld && mergemaster > > > > > > > > I don't mind leaving the option in the kernel, but it does seem > > > > like a strange bug. Let me know if anyone has any other ideas. > > > > Thanks, > > > > > > When the DEBUG make option is defined the compiler optimization > > > flags (COPTFLAGS) default to '-O -pipe' whereas without DEBUG the > > > default is '-O2 -pipe' ('-O2' can cause bogus stack traces so it's > > > not the default for debugging kernels). So in case you also get a > > > panic with a kernel having both: > > > makeoptions DEBUG=-g > > > and: > > > makeoptions COPTFLAGS="-O2 -pipe" > > > this probably means that there's bogus code that breaks at higher > > > optimization levels or a compiler bug. A stack trace from such a > > > panic might help to track this down in case it's not screwed due > > > to the '-O2'. > > > > That's what it was. A kernel with only > > makeoptions COPTFLAGS="-O -pipe" > > builds and runs just fine. > > Are you sure that GENERIC kernel panics too? > I couldn't verify it(I'm on a business trip) but I guess you should > remove smbfs related kernel options. smbfs never worked on sparc64 > and it needs more clean up on various places. > If you encounter the panic again would you post stack traces? Yes, I built about 20 kernels trying to track it down, including GENERIC sans makeoptions DEBUG=-g (but with WITNESS, etc). I haven't actually tried to use SMBFS yet, but simply having it in the kernel doesn't seem to be affecting anything. I'll see if I can get a stacktrace from an existing dump. JN