From owner-freebsd-mips@FreeBSD.ORG Sun Feb 2 03:13:39 2014 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9FA228B0; Sun, 2 Feb 2014 03:13:39 +0000 (UTC) Received: from mail.lhr1.as41113.net (mail.lhr1.as41113.net [91.208.177.22]) by mx1.freebsd.org (Postfix) with ESMTP id 619331673; Sun, 2 Feb 2014 03:13:38 +0000 (UTC) Received: from [10.193.246.16] (unknown [91.208.177.186]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.lhr1.as41113.net (Postfix) with ESMTPS id 3fGy170fwcz7vXM; Sun, 2 Feb 2014 03:13:31 +0000 (UTC) Message-ID: <52EDB7D8.50808@rewt.org.uk> Date: Sun, 02 Feb 2014 03:13:28 +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: Sun, 02 Feb 2014 03:13:39 -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 tried to get a backtrace (it fell on its arse within 10 hrs of being booted), doing minimal traffic (3 meg at most) and basic pf nat... I actually have one from a few months ago that is fine on 10.0-CURRENT, doing 100+ meg so something must have changed. Since this is my only access to the internet here it is a bit of a PITA when it breaks and I couldn't actually get a useful backtrace as it just spewed multiple pages of perhaps relevant info but I didn't have the ability to capture it then, will try again next time...