From: Denys Dmytriyenko <denys@ti.com>
To: Chris Larson <clarson@kergoth.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: Stumped. Can't get 2.6.37 TI kernel to boot when built with toolchain from denzil or Linaro gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_linux/
Date: Thu, 15 Aug 2013 15:06:00 -0400 [thread overview]
Message-ID: <20130815190600.GF2190@edge> (raw)
In-Reply-To: <CABcZANkNbqisKRLHTGmRSs=mbR4VBg2TqfV+CJp54R3G2eNUng@mail.gmail.com>
On Thu, Aug 15, 2013 at 09:25:38AM -0700, Chris Larson wrote:
> On Thu, Aug 15, 2013 at 8:52 AM, Brian Hutchinson <b.hutchman@gmail.com>wrote:
>
> > I have a custom TI816x board that uses a modified kernel from the TI PSP.
> > Kernel is of the 2.6.37 flavor. I'm trying to migrate to OE Core
> > environment and I'm having trouble with getting the kernel to work.
> >
> > With the toolchain in denzil (gcc version 4.6.4 20120303), kernel will at
> > least boot but will die with:
> >
> > Unable to handle kernel NULL pointer dereference at virtual address
> > 00000002
> > pgd = c0004000
> > [00000002] *pgd=00000000
> > Internal error: Oops: 5 [#1]
> >
> > Any of the more modern toolchains (poky/meta-ti master or Linaro
> > (gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_linux) are used, the kernel
> > won't even make a peep ... nothing is displayed.
> >
>
> I haven't seen the panic, but I have seen a complete silent boot hang when
> moving from 4.6 to 4.7 or 4.8 on my OMAP5 EVM board. The gcc-linaro
> toolchain worked, as did a 2012.03 sourcery toolchain, but neither the
> 2013.05 toolchain nor the internal built yocto toolchain from 1.5/master
> resulted in a successful boot. I got past that issue by cherry picking
> these two commits from a more recent kernel:
>
> 455bd4c430b0c0a361f38e8658a0d6cb469942b5 - ARM: 7668/1: fix memset-related
> crashes caused by recent GCC (4.7.2) optimizations
> 418df63adac56841ef6b0f1fcf435bc64d4ed177 - ARM: 7670/1: fix the memset fix
>
> See also
> http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/39864
>
> Presumably you may need more than just that since you're also hitting a
> panic with 4.6, but it may be worth trying those as a starting point. Good
> luck!
Yes, it is often a PITA to get old kernels build and work properly with new
toolchains. E.g. you are aware of the alignment issue with 4.7, right?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-kernel/linux/files/0001-arm-fix-builds-with-gcc-4.7.patch
--
Denys
next prev parent reply other threads:[~2013-08-15 19:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 15:52 Stumped. Can't get 2.6.37 TI kernel to boot when built with toolchain from denzil or Linaro gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_linux/ Brian Hutchinson
2013-08-15 16:25 ` Chris Larson
2013-08-15 19:06 ` Denys Dmytriyenko [this message]
2013-08-15 19:14 ` Brian Hutchinson
2013-08-15 19:26 ` Brian Hutchinson
2013-08-15 19:34 ` Denys Dmytriyenko
2013-08-15 19:39 ` Brian Hutchinson
2013-08-15 19:10 ` Brian Hutchinson
2013-08-15 19:22 ` Denys Dmytriyenko
2013-08-15 19:32 ` Brian Hutchinson
2013-08-15 21:14 ` Brian Hutchinson
2013-08-15 21:32 ` Khem Raj
2013-08-15 21:41 ` Brian Hutchinson
2013-08-15 21:48 ` Brian Hutchinson
2013-08-15 21:33 ` Brian Hutchinson
2013-08-16 15:12 ` Brian Hutchinson
2013-08-16 15:37 ` Khem Raj
2013-08-16 16:25 ` Brian Hutchinson
2013-08-16 20:58 ` Brian Hutchinson
2013-08-16 21:33 ` Khem Raj
2013-08-16 21:04 ` Brian Hutchinson
2013-08-16 21:39 ` Brian Hutchinson
2013-08-16 21:44 ` Maupin, Chase
2013-08-16 21:46 ` Brian Hutchinson
2013-08-16 21:59 ` Khem Raj
2013-08-21 1:42 ` Brian Hutchinson
2013-08-21 4:11 ` Khem Raj
2013-08-21 16:51 ` Brian Hutchinson
2013-08-22 2:46 ` Denys Dmytriyenko
2013-08-22 15:23 ` Brian Hutchinson
2013-08-22 15:38 ` Denys Dmytriyenko
2013-08-22 17:08 ` Brian Hutchinson
2013-08-22 18:41 ` Brian Hutchinson
2013-08-22 18:54 ` Denys Dmytriyenko
2013-08-22 19:35 ` Brian Hutchinson
2013-08-22 20:13 ` Brian Hutchinson
2013-08-16 22:00 ` Khem Raj
2013-08-17 21:45 ` Denys Dmytriyenko
2013-08-17 22:20 ` Brian Hutchinson
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=20130815190600.GF2190@edge \
--to=denys@ti.com \
--cc=clarson@kergoth.com \
--cc=meta-ti@yoctoproject.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.