From owner-freebsd-mips@FreeBSD.ORG Tue Jan 28 10:09:20 2014 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB123320; Tue, 28 Jan 2014 10:09:20 +0000 (UTC) Received: from mail.lhr1.as41113.net (mail.lhr1.as41113.net [91.208.177.22]) by mx1.freebsd.org (Postfix) with ESMTP id 8BA6C1D2E; Tue, 28 Jan 2014 10:09:19 +0000 (UTC) Received: from [10.16.240.11] (unknown [212.9.98.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: lists@rewt.org.uk) by mail.lhr1.as41113.net (Postfix) with ESMTPSA id 3fD3T41FxSz7vbZ; Tue, 28 Jan 2014 10:09:12 +0000 (UTC) Message-ID: <52E781C6.2050308@rewt.org.uk> Date: Tue, 28 Jan 2014 10:09:10 +0000 From: Joe Holden User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Adrian Chadd , Warner Losh Subject: Re: More trapframe panics References: <52E42A1B.3040907@rewt.org.uk> <6354182D-B1D3-4B2E-BEEC-37A2A725A099@bsdimp.com> <52E67F45.20402@rewt.org.uk> <2912AEFA-AA0C-456A-A814-363478BFC900@bsdimp.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-mips@freebsd.org" X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 10:09:20 -0000 On 27/01/2014 17:03, Adrian Chadd wrote: > Hi joe, > > Can you post the backtrace? And resolve the symbol names for each of > the stackframes that show up? > > It could be that there's some code doing dumb crap with stack frames > that we can fix in the source. > > > > -a > I'll try, wondering if this box also has ram problems as even though I regularly see page fault kernel messages on these, they don't usually lead to a userland crash. Always helpful when fsck leaves the filesystem in a worse state than it started because it crashed :D Will get debug kernel built and try and tickle it again, perl built fine in the end but libgcrypt upset it... is it worth applying those patches from CheriBSD?