From: Sascha Hauer <s.hauer@pengutronix.de>
To: Josh Beavers <josh.beavers@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: barebox 2017.05 freezes on VirtualBox x86 boot with "BAREBOX JMP"
Date: Tue, 9 May 2017 07:52:32 +0200 [thread overview]
Message-ID: <20170509055231.sz4jplgkom47m3ww@pengutronix.de> (raw)
In-Reply-To: <CAE=AiOPuC_YytvYSQoBnL4DGPypZ7_35zTmMWB5NMcbad2WPcw@mail.gmail.com>
Hi Josh,
On Mon, May 08, 2017 at 04:49:05AM -0400, Josh Beavers wrote:
> Greetings,
>
> I am trying to boot barebox on x86. I have tried barebox 2016.06.0
> and 2017.05, both of which produce the same result. I see the same
> thing as this thread from 2016, except the message has now been
> upgraded to "BAREBOX JMP":
>
> http://lists.infradead.org/pipermail/barebox/2016-November/028631.html
>
>
> As far as I can tell by adding a pr_err() call, start_barebox() from
> common/startup.c does not get called at all. Instead, something is
> locking up the system between the jump out of boot_hdisk.S and the
> startup code. I am using VirtualBox as a generic 64-bit x86 system in
> case that matters.
>
> Any suggestions about what to investigate would be appreciated.
The barebox x86 port was probably only compile tested the last five
years, so I am not wondering at all. The EFI port should work fine and
is tested, but plain old x86 never reached a level in barebox that could
be called mature or usable.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-05-09 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 8:49 Josh Beavers
2017-05-09 5:52 ` Sascha Hauer [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=20170509055231.sz4jplgkom47m3ww@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=josh.beavers@gmail.com \
/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