From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: why would i get "Out of memory" error in a sandbox build?
Date: Wed, 2 Jul 2014 15:50:36 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407021543560.7005@localhost> (raw)
playing around with an absolutely generic sandbox build and i ran
into the following issue. i built sandbox on my fedora rawhide system
with no customization whatsoever, and executed it with no root
privilege, so i definitely expected some things not to work. i got the
following:
$ ./barebox
barebox 2014.06.0-00365-g96c53b1 #1 Wed Jul 2 15:03:37 EDT 2014
Board: barebox sandbox
could not open /dev/net/tun: Permission denied
tap tap0: probe failed: Operation not permitted
malloc space: 0x7f249f5e9010 -> 0x7f249fde900f (size 8 MiB)
environment load /dev/env0: No such file or directory
Maybe you have to create the partition.
no valid environment found on /dev/env0. Using default environment
running /env/bin/init...
\nHit any key to stop autoboot: 0
booting net
ifup: Cannot find device eth0
ifup: No such file or directory
running automount command 'ifup eth0 && mount -t tftp $eth0.serverip
/mnt/tftp' failed
ifup: Cannot find device eth0
ifup: No such file or directory
running automount command 'ifup eth0 && mount -t tftp $eth0.serverip
/mnt/tftp' failed
could not open /mnt/tftp/none-linux-barebox: No such file or directory
Booting net failed: No such file or directory
booting net failed: No such file or directory
boot: No such file or directory
barebox@barebox sandbox:/
i'm actually good with this, it's about what i expected since i set
no environment or networking, etc. but just for fun, i "cd"ed down
into /mnt/tftp, knowing this shouldn't work, and here's what happened:
barebox@barebox sandbox:/ cd /mnt/tftp
ifup: Cannot find device eth0
ifup: No such file or directory
running automount command 'ifup eth0 && mount -t tftp $eth0.serverip
/mnt/tftp' failed
barebox@barebox sandbox:/mnt/tftp cd /
ERROR: out of memory
no stack data available
[rpjday@localhost barebox_build]$
in short, "cd"ing into /mnt/tftp failed as it should have, but just
trying to "cd" back to the root caused the "out of memory" error. it
seems entirely reproducible. should i have expected this?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-07-02 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 19:50 Robert P. J. Day [this message]
2014-07-03 6:26 ` Sascha Hauer
2014-07-03 11:23 ` Robert P. J. Day
2014-07-04 5:30 ` Sascha Hauer
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=alpine.LFD.2.11.1407021543560.7005@localhost \
--to=rpjday@crashcourse.ca \
--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