From: jon-hunter@ti.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: Beagleboard B6 woes
Date: Mon, 31 Aug 2009 11:24:58 -0500 [thread overview]
Message-ID: <4A9BF95A.8000404@ti.com> (raw)
In-Reply-To: <20090831093810.GE4927@fitfioullt278>
Mikko Rapeli wrote:
> Hello,
>
> I'd like to test out newer kernel on a Beagleboard B6 but latest
> trees from Linus, linux-omap and linux-omap/for-next seem to be failing at
> early boot [1] with omap3_beagle_defconfig.
>
> Some bisecting shows that ARM_UNWIND broke something in the defconfig since
> kernels before adf8b37bafc1495393201a2ae4235846371870d0 "[ARM] 5386/2:
> unwind: Add Makefile and Kconfig entries for ARM stack unwinding" work.
If UNWIND is breaking it, then the most likely cause is that you are
using an older toolchain, such as code-sourcery 2007q3. If you are using
2007q3, upgrade to a 2008 or 2009 release. More details here:
http://marc.info/?l=linux-omap&m=124175324604568&w=2
> On the other hand, setting ARM_UNWIND to n which falls back to FRAME_POINTERs
> work until 84e250ffa76dddc1bad84e04248a27f442c25986 "musb: proper hookup to
> transceiver drivers".
You could trying enabling "CONFIG_TWL4030_USB" to see if this helps.
Jon
parent reply other threads:[~2009-08-31 16:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20090831093810.GE4927@fitfioullt278>]
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=4A9BF95A.8000404@ti.com \
--to=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).