From owner-freebsd-sparc64@FreeBSD.ORG Wed Jan 11 19:41:52 2012 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BDD11065672 for ; Wed, 11 Jan 2012 19:41:52 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id DA8728FC0A for ; Wed, 11 Jan 2012 19:41:51 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.4/8.14.4/ALCHEMY.FRANKEN.DE) with ESMTP id q0BJfYG5049345; Wed, 11 Jan 2012 20:41:35 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.4/8.14.4/Submit) id q0BJfYop049344; Wed, 11 Jan 2012 20:41:34 +0100 (CET) (envelope-from marius) Date: Wed, 11 Jan 2012 20:41:34 +0100 From: Marius Strobl To: Anton Shterenlikht Message-ID: <20120111194134.GC44286@alchemy.franken.de> References: <20111216084048.GA98967@mech-cluster241.men.bris.ac.uk> <20111216103720.GA853@alchemy.franken.de> <20111216111922.GA99512@mech-cluster241.men.bris.ac.uk> <20111216161031.GA2371@alchemy.franken.de> <20120106112126.GA69964@mech-cluster241.men.bris.ac.uk> <20120110134600.GA7617@mech-cluster241.men.bris.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120110134600.GA7617@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: r223378 panic [Re: sparc64 r228561 panic: kmem_suballoc: bad status return of 3] 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: Wed, 11 Jan 2012 19:41:52 -0000 On Tue, Jan 10, 2012 at 01:46:01PM +0000, Anton Shterenlikht wrote: > On Fri, Jan 06, 2012 at 11:21:27AM +0000, Anton Shterenlikht wrote: > > On Fri, Dec 16, 2011 at 05:10:31PM +0100, Marius Strobl wrote: > > > On Fri, Dec 16, 2011 at 11:19:22AM +0000, Anton Shterenlikht wrote: > > > > On Fri, Dec 16, 2011 at 11:37:20AM +0100, Marius Strobl wrote: > > > > > On Fri, Dec 16, 2011 at 08:40:48AM +0000, Anton Shterenlikht wrote: > > > > > > Updating from r216048 to r228561 on sparc64, > > > > > > with sys/conf/newvers.sh changed to REVISION="9.9". > > > > > > > > > > > > Trinscribed by hand: > > > > > > > > > > > > FreeBSD 9.9-CURRENT #3 r228561M: > > > > > > > > > > > > panic: kmem_suballoc: bad status return of 3 > > > > > > KDB: enter: panic > > > > > > [ thread pid 0 tid 0 ] > > > > > > Stopped at 0x02937e0: ta %xcc,1 > > > > > > db> > > > > > > > > > > > > The keyboard froze, couldn't get a bt, > > > > > > required a cold reboot. > > > > > > > > > > > > My /etc/make.conf and kernel config files are below. > > > > > > > > > > > > Any advice? > > > > > > > > > > > > > > > > Hrm, doesn't look like I can reproduce this. What machine model is > > > > > that and how much RAM does it have? > > > > > > > > >From dmesg: > > > > > > > > real memory = 2147483648 (2048 MB) > > > > avail memory = 2079449088 (1983 MB) > > > > cpu0: Sun Microsystems UltraSparc-IIIi Processor (1503.00 MHz CPU) > > > > > > > > > Do you use any loader tuneables? > > > > > > > > I don't think so. You mean like /boot/loader.conf? > > > > I haven't got this file at all. > > > > > > > > > > Even with a Blade 1500, which is the closest match to your machine > > > that I have, and a kernel built with your configuration file I can't > > > reproduce this using r228583. I'd suggest to test with a kernel built > > > using an empty object directory and without any local modifications. > > > If that still doesn't solve the problem given that there isn't even > > > a backtrace I just can suggest to do a binary search for the offending > > > commit, probably accounting especially for the changes to the VM > > > within the window of revisions in question. > > > > It took a while. > > > > 223377 - ok > > 223378 - panic > > > > # svn up -r 223378 > > Updating '.': > > U sys/sparc64/include/tsb.h > > U sys/sparc64/include/vmparam.h > > Updated to revision 223378. > > > > # svn diff -c 223378 > > Index: sys/sparc64/include/tsb.h > > =================================================================== > > --- sys/sparc64/include/tsb.h (revision 223377) > > +++ sys/sparc64/include/tsb.h (revision 223378) > > @@ -50,7 +50,6 @@ > > extern vm_size_t tsb_kernel_mask; > > extern vm_size_t tsb_kernel_size; > > extern vm_paddr_t tsb_kernel_phys; > > -extern u_int tsb_kernel_ldd_phys; > > > > static __inline struct tte * > > tsb_vpntobucket(pmap_t pm, vm_offset_t vpn) > > Index: sys/sparc64/include/vmparam.h > > =================================================================== > > --- sys/sparc64/include/vmparam.h (revision 223377) > > +++ sys/sparc64/include/vmparam.h (revision 223378) > > @@ -218,7 +218,7 @@ > > * is the total KVA space allocated for kmem_map. > > */ > > #ifndef VM_KMEM_SIZE_SCALE > > -#define VM_KMEM_SIZE_SCALE (3) > > +#define VM_KMEM_SIZE_SCALE (tsb_kernel_ldd_phys == 0 ? 3 : 1) > > #endif > > > > /* > > @@ -238,6 +238,7 @@ > > > > #define UMA_MD_SMALL_ALLOC > > > > +extern u_int tsb_kernel_ldd_phys; > > extern vm_offset_t vm_max_kernel_address; > > > > /* > > > > I just realised that I have another blade 1500 silver, > which runs 226827: > > FreeBSD 9.0-RC1 #2 r226827: Thu Oct 27 15:51:42 BST 2011 > root@mech-as222.men.bris.ac.uk:/usr/obj/usr/src/sys/DALET sparc64 > WARNING: WITNESS option enabled, expect reduced performance. > real memory = 5368709120 (5120 MB) > avail memory = 5230305280 (4988 MB) > cpu0: Sun Microsystems UltraSparc-IIIi Processor (1503.00 MHz CPU) > > However, if I try to use that revision on the > problem box, I still get this panic. What's going on? > So far I didn't have time to look into this. I suspect the issue has to do with the holes USIIIi machines tend to have in their physical memory layout. For a b1k5 with 2GB RAM such a hole might be large enough to trigger some bug in the VM but not trigger with 4GB or as in my case with 1GB. Marius