From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: bcm4708-smartrg-sr400ac boot failures in next/arm-soc
Date: Fri, 8 Jan 2016 22:50:32 +0000 [thread overview]
Message-ID: <20160108225032.GO19062@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CANMBJr6LW=y7g4_CCutHf4vu5NkzoeXt_RvPSJAsTE2nFpGwqw@mail.gmail.com>
On Fri, Jan 08, 2016 at 02:33:39PM -0800, Tyler Baker wrote:
> After a bit of investigation, I determined that CONFIG_BLK_DEV_RAM was
> causing the issue and disabling it fixed the boot issue. Essentially,
> the kernel cannot find the initrd that has been loaded into memory by
> CFE bootloader with this option enabled as I inject the following
> command line into the DT before it's loaded over tftp.
>
> Loaded in CFE by: 'load -raw -tftp -addr=0x4000000 -max=0x900000
> 192.168.2.2:tmpqC9zOv/ramdisk.cpio.gz'
>
> Kernel arguments injected into DT: 'console=ttyS0,115200
> initrd=0x4000000,8M root=/dev/ram0 ip=dhcp'
What is the problem that the kernel is reporting?
I'm asking because kernelci.org uses javascript, which is not elinks
friendly, and it otherwise means I need to walk over to a different
machine to look at it, and then return to a different machine to finish
writing the email - as a result, I hardly ever look at the kernelci.org
results, and just rely on Olof's results.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-01-08 22:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 22:33 bcm4708-smartrg-sr400ac boot failures in next/arm-soc Tyler Baker
2016-01-08 22:47 ` Arnd Bergmann
2016-01-08 22:50 ` Russell King - ARM Linux [this message]
2016-01-08 23:17 ` Tyler Baker
2016-01-08 23:44 ` Russell King - ARM Linux
2016-01-08 23:59 ` Tyler Baker
2016-01-09 0:07 ` Russell King - ARM Linux
2016-01-09 0:21 ` Tyler Baker
2016-01-09 0:58 ` Tyler Baker
2016-01-09 1:29 ` Russell King - ARM Linux
2016-01-09 1:50 ` Tyler Baker
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=20160108225032.GO19062@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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