All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stian Skjelstad <stian@nixia.no>
To: Jeff Dike <jdike@addtoit.com>
Cc: UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] syscall failed
Date: Mon, 31 Mar 2008 22:06:51 +0200	[thread overview]
Message-ID: <1206994011.6886.19.camel@localhost> (raw)
In-Reply-To: <20080331145036.GH6540@c2.user-mode-linux.org>

If this is a common issue/problem, perhaps an informativ error-message
can be written when this occure, hinting the user to a possible
solution.

Stian

On Mon, 2008-03-31 at 10:50 -0400, Jeff Dike wrote:
> On Fri, Mar 28, 2008 at 10:44:08PM +0000, Antoine Martin wrote:
> > [43492659.840000] syscall_stub_done : ret = -12, offset = 548682067984,
> > data = 000000007f115010
> > [43492659.840000] syscall_stub_done : syscall 9 failed, return value =
> > 0xfffffff4, expected return value = 0x47a0000
> 
> is just mmap returning -ENOMEM, which we've seen elsewhere with large
> UML processes hitting the host's /proc/sys/vm/max_map_count limit.
> Have you checked that?



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2008-03-31 20:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 22:44 [uml-devel] syscall failed Antoine Martin
2008-03-31 14:50 ` Jeff Dike
2008-03-31 20:06   ` Stian Skjelstad [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=1206994011.6886.19.camel@localhost \
    --to=stian@nixia.no \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.