From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1]
Date: Tue, 18 Jun 2013 11:20:00 -0400 [thread overview]
Message-ID: <cover.1371567827.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
Here's the integration of a change from Khem to fix the gcc 4.8 ARM
boot issues.
I'm still seeing some quasi random issues, but this definitely fixes
the issue at hand, gets us up and running and is much better than
what we had before.
The patch pretty much says everything else:
linux-yocto/3.8: fix gcc 4.8 ARM boot issues
Updating the linux-yocto-3.8 SRCREVs to fix a boot issue with ARM boards
when gcc 4.8 is used.
Without the following mainline backports:
f200475 ARM: 7670/1: fix the memset fix
8215b0e ARM: 7668/1: fix memset-related crashes caused by recent GCC (4.7.2) optimizations
The following trap will be seen on boot:
[<c00fc3b8>] (kmem_cache_alloc_trace+0x54/0x210) from [<c039f074>] (con_insert_unipair+0xcc/0x11c)
[<c039f074>] (con_insert_unipair+0xcc/0x11c) from [<c039fec8>] (con_set_default_unimap+0xfc/0x198)
[<c039fec8>] (con_set_default_unimap+0xfc/0x198) from [<c07ee258>] (console_map_init+0x44/0x58)
[<c07ee258>] (console_map_init+0x44/0x58) from [<c07ee738>] (vty_init+0x16c/0x1b0)
[<c07ee738>] (vty_init+0x16c/0x1b0) from [<c07edb68>] (tty_init+0x108/0x148)
[<c07edb68>] (tty_init+0x108/0x148) from [<c07eead0>] (chr_dev_init+0xb4/0xd8)
[<c07eead0>] (chr_dev_init+0xb4/0xd8) from [<c0008a18>] (do_one_initcall+0x11c/0x18c)
[<c0008a18>] (do_one_initcall+0x11c/0x18c) from [<c07d89d0>] (kernel_init_freeable+0x16c/0x254)
[<c07d89d0>] (kernel_init_freeable+0x16c/0x254) from [<c05a3810>] (kernel_init+0x18/0x160)
[<c05a3810>] (kernel_init+0x18/0x160) from [<c000e530>] (ret_from_fork+0x14/0x20)
Code: e593a000 e35a0000 0a000020 e5943014 (e79a1003)
---[ end trace e6c62de166779f86 ]---
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Moderate stress and board testing shows the fix to hold, and it is good for
broader testing.
[YOCTO #4549]
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Cheers,
Bruce
The following changes since commit 1dd643b142c69ac9035e29bff11d02201638dc65:
licences: Add SGI license (2013-06-17 16:45:37 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (1):
linux-yocto/3.8: fix gcc 4.8 ARM boot issues
meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_3.8.bb | 14 +++++++-------
3 files changed, 12 insertions(+), 12 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-06-18 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 15:20 Bruce Ashfield [this message]
2013-06-18 15:20 ` [PATCH 1/1] linux-yocto/3.8: fix gcc 4.8 ARM boot issues Bruce Ashfield
2013-06-18 15:22 ` [PATCH 0/1] Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2017-10-30 21:56 Amanda Brindle
2017-11-21 0:21 Amanda Brindle
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=cover.1371567827.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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