From owner-freebsd-arm@FreeBSD.ORG Sun Feb 2 12:11:44 2014 Return-Path: Delivered-To: freebsd-arm@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 10A0FF1F for ; Sun, 2 Feb 2014 12:11:44 +0000 (UTC) Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9A87E1760 for ; Sun, 2 Feb 2014 12:11:43 +0000 (UTC) Received: from [192.168.1.102] (p54819D5A.dip0.t-ipconnect.de [84.129.157.90]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 84A911C0E9796; Sun, 2 Feb 2014 13:11:40 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: panic From: Michael Tuexen In-Reply-To: <20140202120509.5d1e0f64@bender.Home> Date: Sun, 2 Feb 2014 13:11:40 +0100 Content-Transfer-Encoding: 7bit Message-Id: References: <14E59004-FC13-48DD-B789-AA78767C6871@freebsd.org> <20140202120509.5d1e0f64@bender.Home> To: Andrew Turner X-Mailer: Apple Mail (2.1510) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Feb 2014 12:11:44 -0000 On Feb 2, 2014, at 1:05 PM, Andrew Turner wrote: > On Fri, 31 Jan 2014 06:36:43 +0100 > Michael Tuexen wrote: > >> Dear all, >> >> while building the or xcb-util-renderutil-0.3.8 port I got >> panic: Undefined instruction in kernel. >> when running r261186 on a RPI-B. I could successfully build >> ports for cvs, subversion, git... > > Can you get the opcodes in your kernel around 0xc048ec60. There are two > instructions that may be the problem and depending on which one you are > hitting it would indicate a different problem. > > Also if possible can you get more of the kernel output from around the > panic. There are a few kernel printf calls that would narrow down what > is happening. Hi Andrew, I'm sorry, I rebooted the pi in the meantime... Best regards Michael > > Andrew >