From owner-freebsd-arm@freebsd.org  Sun Jan 31 01:27:51 2016
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05AC3A73BED
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Sun, 31 Jan 2016 01:27:51 +0000 (UTC)
 (envelope-from fbsd@www.zefox.net)
Received: from www.zefox.net (www.zefox.net [69.239.235.194])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C5BF31C06
 for <freebsd-arm@freebsd.org>; Sun, 31 Jan 2016 01:27:50 +0000 (UTC)
 (envelope-from fbsd@www.zefox.net)
Received: from www.zefox.net (localhost [127.0.0.1])
 by www.zefox.net (8.14.9/8.14.5) with ESMTP id u0V1OmxT077146;
 Sat, 30 Jan 2016 17:24:49 -0800 (PST)
 (envelope-from fbsd@www.zefox.net)
Received: (from fbsd@localhost)
 by www.zefox.net (8.14.9/8.14.5/Submit) id u0V1OmdG077145;
 Sat, 30 Jan 2016 17:24:48 -0800 (PST) (envelope-from fbsd)
Date: Sat, 30 Jan 2016 17:24:48 -0800
From: bob prohaska <fbsd@www.zefox.net>
To: freebsd-arm@freebsd.org
Subject: Files needed to analyze kernel panic
Message-ID: <20160131012448.GB75928@www.zefox.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Jan 2016 01:27:51 -0000

Hi all,

It's  possible to reliably crash an RPI2 running 11-CURRENT using stress2.
In most cases the crash occurs during the syscall tests and then usually the opening
line is of the form "translation fault L2" [sometimes L1].

What information is useful to collect for purposes of debugging by others off-host?
So far I'm aware of backtrace, kernel and modules, vmcore, core.txt and recently
kernel.debug (three places). One update/build/test/crash cycle per day is possible. 


Thanks for reading, and any guidance.

bob prohaska