mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Rolf Evers-Fischer <embedded24@evers-fischer.de>
To: barebox@lists.infradead.org
Subject: Beaglebone white: Kernel doesn't start with barebox-2014.03.0
Date: Tue, 15 Apr 2014 13:28:02 +0200 (CEST)	[thread overview]
Message-ID: <832723417.563292.1397561282646.open-xchange@email.1und1.de> (raw)

Dear all,
after update to barebox-2014.03.0, the kernel on my beaglebone-white doesn't
start anymore.
The last line, which appears, is "booting kernel with devicetree".
I discovered that the problem is caused by the commit [1]. When I revert this
commit, everything works fine.

Here is some more info, which I gathered with additional printfs:
Without this commit, the '__do_bootm_linux()' function is called with
 data->initrd_address = 0xffffffff
 data->os_res->start = 0x80008000
 data->os_entry = 0
 swap = 0
Finally it invokes the 'start_linux()' function with
 kernel = 0x80008000
 swap = 0
 initrd_start = 0x80808000
 initrd_size = 0
 data->oftree = 0x8b1e0000

With this commit (i.e. when the kernel doesn't start), the '__do_bootm_linux()'
function is called with the same parameters as above plus
 free_mem = 0x8041f000
It invokes the 'start_linux()' function with
 kernel = 0x80008000
 swap = 0
 initrd_start = 0x8041f000
 initrd_size = 0
 data->oftree = 0x8041f000

Do you have any idea, how to fix this problem? For now I will continue using
barebox-2014.03.0 without the problematic commit.

[1] http://www.spinics.net/lists/u-boot-v2/msg17345.html
    "ARM: bootm: pass free memory to __do_bootm_linux"

Best regards,
 Rolf

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2014-04-15 11:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 11:28 Rolf Evers-Fischer [this message]
2014-04-16 15:35 ` Lucas Stach
2014-04-16 20:02   ` Uwe Kleine-König
2014-04-21 15:24     ` Lucas Stach
2014-04-22  7:08       ` Rolf Evers-Fischer
2014-04-22  8:26         ` Lucas Stach
2014-04-22 10:34           ` Rolf Evers-Fischer

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=832723417.563292.1397561282646.open-xchange@email.1und1.de \
    --to=embedded24@evers-fischer.de \
    --cc=barebox@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