From: Sam Nazarko <samnazarko@stmteam.com>
To: buildroot@busybox.net
Subject: [Buildroot] Can't boot with 2011.05
Date: Tue, 26 Jul 2011 20:50:21 +0100 [thread overview]
Message-ID: <000e01cc4bcd$4094e360$c1beaa20$@com> (raw)
Since the 2011.05 Buildroot release I've not been able to get a bootable
system even with the simplest of options and I haven't a clue why. In
2011.02 if I was to have some simple options of a i386 build platform
targeting i686 to generate an initramfs system (everything else default,
kernel with i386 defconfig) the system would boot fine in QEMU or VirtualBox
and give me a login prompt. Trying a similar approach on 2011.05 either
chucks a "Adjusting TSC clocksource" and hang or a "ip used greatest stack
depth" and hang. I assume this is not the actual cause of the hang but what
I see before the problem, which I think is to do with mounting the root file
system.
I am wondering what's changed that might be causing this,
Thanks
Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110726/8cfd8755/attachment-0001.html>
next reply other threads:[~2011-07-26 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 19:50 Sam Nazarko [this message]
2011-07-26 21:14 ` [Buildroot] Can't boot with 2011.05 Michael S. Zick
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='000e01cc4bcd$4094e360$c1beaa20$@com' \
--to=samnazarko@stmteam.com \
--cc=buildroot@busybox.net \
/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