From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: omap3430 fails to boot
Date: Thu, 9 May 2013 08:20:48 -0700 [thread overview]
Message-ID: <20130509152047.GA32546@atomide.com> (raw)
In-Reply-To: <20130509084906.GL21614@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [130509 01:54]:
> I've not looked into the reason why yet, so this is a heads-up. I
> notice this morning that the LDP3430 failed to boot last night,
> whereas it worked the previous night. However, SDP4430 looks fine.
>
> Nothing obvious in the diffstat between the two... but then the patch
> between the two kernels is almost 1.5MB. The arch/arm changes are
> quite small though:
>
> arch/arm/Kconfig | 1 +
> arch/arm/boot/dts/Makefile | 4 +-
> arch/arm/boot/dts/xenvm-4.2.dts | 13 +
> arch/arm/include/asm/xen/hypercall.h | 1 +
> arch/arm/mach-msm/last_radio_log.c | 2 +-
> arch/arm/mach-omap2/board-4430sdp.c | 2 +-
> arch/arm/mach-omap2/board-omap4panda.c | 2 +-
> arch/arm/mach-omap2/timer.c | 4 +
> arch/arm/mach-vexpress/v2m.c | 1 -
> arch/arm/mach-virt/virt.c | 1 +
Since one boots and one won't, you're probably missing this one:
956e46ef mm/slab: Fix crash during slab init
Looking at your diffstat you probably have this as otherwise
nothing boots:
9affd6be arm: fix mismerge of arch/arm/mach-omap2/timer.c
Let me know if you still have the issue after updating to 956e46ef.
Regards,
Tony
prev parent reply other threads:[~2013-05-09 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 8:49 omap3430 fails to boot Russell King - ARM Linux
2013-05-09 15:20 ` Tony Lindgren [this message]
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=20130509152047.GA32546@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).