From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6794] New: Busybox compiled from buildroot hangs on pass from intiramfs to init
Date: Mon, 13 Jan 2014 21:26:15 +0000 (UTC) [thread overview]
Message-ID: <bug-6794-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6794
Summary: Busybox compiled from buildroot hangs on pass from
intiramfs to init
Product: buildroot
Version: 2013.11
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: anthonysepa at yahoo.ca
CC: buildroot at uclibc.org
Estimated Hours: 0.0
I use the same binary in a initramfs that processes an init script. At the time
that it passes off the processing to the busybox on my rootfs as /sbin/init it
hangs. If I replace the binaries with an "out of tree" compiled version it
works fine.
If I replace the installed binary with the binary in the
output/build/busybox-1.21.1 it works fine also. In trying to track down the
problem I noticed that the installed binary is different from the built binary
and was modified 3 minutes later in the build process.
I am cross compiling on a Ubuntu 64 bit machine for an arm gaming device.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-01-13 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 21:26 bugzilla at busybox.net [this message]
2014-02-07 8:27 ` [Buildroot] [Bug 6794] Busybox compiled from buildroot hangs on pass from intiramfs to init bugzilla at busybox.net
2014-02-23 14:48 ` bugzilla at busybox.net
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=bug-6794-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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