From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Sebastian Reichel <sre@debian.org>
Cc: linux-omap@vger.kernel.org
Subject: Re: problem with "undefined instruction"
Date: Sat, 30 Apr 2011 22:12:46 +0530 [thread overview]
Message-ID: <4DBC3C06.9010306@ti.com> (raw)
In-Reply-To: <20110430162357.GA14287@earth.universe>
On 4/30/2011 9:53 PM, Sebastian Reichel wrote:
> Hi,
>
> I'm currently trying to get a mainline based kernel running on my pandaboard.
> The problem is, that it's crashing very early during the init phase because of
> "undefined instruction" exceptions:
>
> [ 1.867980] udevd (56): undefined instruction: pc=401e6ed4
> [ 1.874603] Code: 9cd0 fffe e92d 4ff0 (ed2d)
> [ 1.977752] modprobe (69): undefined instruction: pc=400c6ed4
> [ 1.977783] Code: 9cd0 fffe e92d 4ff0 (ed2d)
> [ 1.978240] init (1): undefined instruction: pc=40149ed4
> [ 1.978240] Code: 9cd0 fffe e92d 4ff0 (ed2d)
> [ 2.005706] Kernel panic - not syncing: Attempted to kill init!
>
> Exactly the same userland boots fine with the original 2.6.35 kernel, so it's
> probably not the userland's fault. But I searched for the byte combination
> anyway and found it in libc.so:
>
> 32ecc: 9cd0 ldr r4, [sp, #832] ; 0x340
> 32ece: fffe e92d vtbl.8 d30, {d14-d15}, d29
>
> 00032ed0<_IO_vfprintf>:
> 32ed0: e92d 4ff0 stmdb sp!, {r4, r5, r6, r7, r8, r9, sl, fp, lr}
> 32ed4: ed2d 8b02 vpush {d8}
>
Looks like NEON instructions are taking an exception. Can you disable
VFP, NEON and give a one more shot.
> Can you please tell me what's missing in my kernel? I uploaded
> .config and full boot messages here:
>
Config seems to enable needed NEON/VFP options.
Regards
Santosh
next prev parent reply other threads:[~2011-04-30 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 16:23 problem with "undefined instruction" Sebastian Reichel
2011-04-30 16:42 ` Santosh Shilimkar [this message]
2011-04-30 16:44 ` Måns Rullgård
2011-04-30 16:57 ` Santosh Shilimkar
2011-04-30 17:09 ` Måns Rullgård
2011-06-06 12:56 ` Sebastian Reichel
2011-06-07 11:53 ` Tony Lindgren
2011-06-23 19:53 ` Sebastian Reichel
2011-06-27 12:12 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DBC3C06.9010306@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=sre@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.