From: "Marc Marí" <marc.mari.barcelo@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] VersatilePB bug (or undefined behaviour)
Date: Tue, 27 Jan 2015 21:04:17 +0100 [thread overview]
Message-ID: <20150127210417.3e4704c5@crunchbang> (raw)
Hi
I was investigating a bit with a versatilepb machine, and I was trying
to boot a Linux system with a root file system through NFS. It worked
with Linux 3.2, but it didn't work with any later Linux version. This
was the error:
[ 0.594471] smc91x: not found (-16).
[ 0.595555] smc91x: probe of smc91x.0 failed with error -16
(Error -16 is EBUSY).
I debugged the error, and I found that the region was being marked as
"System RAM".
The problem was mine, I specified (because I did not change if from
previous boots) 1G as memory for the Versatile machine, which only has
256 MB of RAM
Should this be a bug, or is undefined behaviour? I think it is not very
difficult to check for the memory the user requests so it can be
limited to 256 MB and issue a warning if it is exceeded.
Thanks
Marc
next reply other threads:[~2015-01-27 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 20:04 Marc Marí [this message]
2015-01-27 20:58 ` [Qemu-devel] VersatilePB bug (or undefined behaviour) Peter Maydell
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=20150127210417.3e4704c5@crunchbang \
--to=marc.mari.barcelo@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).