From: Tony Lindgren <tony@atomide.com>
To: Sebastian Reichel <sre@debian.org>
Cc: linux-omap@vger.kernel.org
Subject: Re: problem with "undefined instruction"
Date: Tue, 7 Jun 2011 14:53:31 +0300 [thread overview]
Message-ID: <20110607115331.GZ8696@atomide.com> (raw)
In-Reply-To: <20110606125600.GB20909@earth.universe>
* Sebastian Reichel <sre@debian.org> [110606 15:51]:
> On Sat, Apr 30, 2011 at 06:23:57PM +0200, Sebastian Reichel wrote:
> > 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.
>
> I found the source of this problem. VFPv3 support is not working
> correctly when OMAP2 (and thus CPU_V6) is enabled in the kernel
> config.
>
> I guess this should be mentioned in the kernel config (or fixed if
> possible).
This should be easy to fix now. Do you have a minimal test program that
triggers this?
Tony
next prev parent reply other threads:[~2011-06-07 11:53 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
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 [this message]
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=20110607115331.GZ8696@atomide.com \
--to=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox