Bad mode in undefined instruction handler detected

[Russell King - ARM Linux]

On Tue, Mar 29, 2016 at 03:18:08PM -0400, Patrick Doyle wrote:
> On Tue, Mar 29, 2016 at 2:29 PM, Russell King - ARM Linux
> <linux at arm.linux.org.uk> wrote:
> > THUMB2_KERNEL is an option, which I believe you already have disabled.
> > So, the offending option is probably ARM_UNWIND.  You are provided with
> > the ARM_UNWIND option, and you need to say no to that.  Don't try to
> > build a kenrel with frame pointers and unwinding together - it'll
> > probably fail, or if you succeed in building it, it probably won't
> > work correctly since that's a combination we don't support.
> >
> Right, I can confirm that building with both produces a kernel that
> doesn't boot (for me anyway).  Unfortunately, enabling FRAME_POINTER
> instead of ARM_UNWIND produced a kernel which, when it crashed only
> told me:
> 
> Unable to handle kernel paging request at virtual address e5912144
> pgd = c0004000
> [e5912144] *pgd=00000000
> Internal error: Oops: 5 [#1] ARM
> 
> Is there something else I need to enable to get a more verbose dump?

Sounds like you're getting memory corruption, and this time it's
(possibly) overwriting bits of the kernel responsible for dumping
this data.

If it only happens when using the camera, it sounds to me (at least)
as though the camera driver is buggy, and that's outside of my
expertise.  That's guess-work though.

I'm afraid that I don't think I can help in this case, sorry.

-- 
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.