Date: Sun, 2 Feb 2014 10:14:20 -0800 From: John-Mark Gurney <jmg@funkthat.com> To: Michael Tuexen <tuexen@freebsd.org> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: panic Message-ID: <20140202181420.GC93141@funkthat.com> In-Reply-To: <B6C771EC-B635-4392-9088-1CFC640329EB@freebsd.org> References: <14E59004-FC13-48DD-B789-AA78767C6871@freebsd.org> <20140202120509.5d1e0f64@bender.Home> <B6C771EC-B635-4392-9088-1CFC640329EB@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Tuexen wrote this message on Sun, Feb 02, 2014 at 13:11 +0100:
> On Feb 2, 2014, at 1:05 PM, Andrew Turner <andrew@fubar.geek.nz> wrote:
>
> > On Fri, 31 Jan 2014 06:36:43 +0100
> > Michael Tuexen <tuexen@freebsd.org> 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...
As long as you didn't compile a new kernel, just do:
objdump -d --start-address=0xc048ec50 /boot/kernel/kernel
And send us the lines between 0xc048ec50 and 0xc048ec70...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140202181420.GC93141>