From: hauke@hauke-m.de (Hauke Mehrtens)
To: linux-arm-kernel@lists.infradead.org
Subject: bcm4708-smartrg-sr400ac boot failures in next-20150918+
Date: Mon, 12 Oct 2015 00:49:44 +0200 [thread overview]
Message-ID: <561AE788.6030701@hauke-m.de> (raw)
In-Reply-To: <560DA9B9.80404@hauke-m.de>
Adding the arm List.
On 10/01/2015 11:46 PM, Hauke Mehrtens wrote:
> On 10/01/2015 07:50 PM, Tyler Baker wrote:
>> Hi Hauke, Rafal,
>>
>> The kernelci.org bot has been reporting complete boot failures[1]
>> since next-20150918. I've bisected[2] the issue and found "ARM:
>> 8422/1: enable imprecise aborts during early kernel startup" is the
>> offending patch. Reverting this on top of -next fixes the boot issue.
>>
>> Apologies for sending this off list, but I want to make sure you can
>> confirm this issue before we raise it.
>>
>> Cheers,
>>
>> Tyler
>>
>> [1] http://kernelci.org/boot/bcm4708-smartrg-sr400ac/
>> [2] http://hastebin.com/mirunerobi.vhdl
>>
> Hi Tyler,
>
> Thanks for the info, the broken bootloader causes some problems when
> booting the kernel, we already had to ignore some exceptions. I will
> look into this at the weekend.
>
> Hauke
>
Hi,
The commit "ARM: 8422/1: enable imprecise aborts during early kernel
startup" breaks bcm53xx devices with a broken boot loader, this is a
regression. There are probably millions of these devices shipped with
this boot loader called CFE.
For BCM53xx we install a fault handler in the init_early callback of
DT_MACHINE_START to ignore the faults produced by the boot loader in
http://lxr.free-electrons.com/source/arch/arm/mach-bcm/bcm_5301x.c#L40 ,
but init_early is called after local_abt_enable() gets called and this
causes a kernel panic because of any unhandled CPU fault. The reserve()
callback in DT_MACHINE_START was the only callback I could find which
gets called before local_abt_enable(), should I move the code which
installs the fault handler there?
This is causing the problems in kernelci with linux next kernels on this
board: http://kernelci.org/boot/bcm4708-smartrg-sr400ac/
Hauke
next parent reply other threads:[~2015-10-11 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANMBJr5FnRQxv01CbAiSD43dGn+Ea4tjEWSsV1FywHJZYLnG_A@mail.gmail.com>
[not found] ` <560DA9B9.80404@hauke-m.de>
2015-10-11 22:49 ` Hauke Mehrtens [this message]
2015-10-13 18:49 ` bcm4708-smartrg-sr400ac boot failures in next-20150918+ Tyler Baker
2015-10-14 9:48 ` Lucas Stach
2015-10-14 9:56 ` Russell King - ARM Linux
2015-10-14 10:04 ` Lucas Stach
2015-10-14 22:07 ` Hauke Mehrtens
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=561AE788.6030701@hauke-m.de \
--to=hauke@hauke-m.de \
--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).