From: Antoine Martin <antoine@nagafix.co.uk>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] do_syscall_stub: syscall 9 failed
Date: Tue, 30 Jan 2007 18:36:15 +0000 [thread overview]
Message-ID: <45BF901F.40206@nagafix.co.uk> (raw)
Just caught this in `dmesg`
[42977596.520000] Adding 131064k swap on /dev/ubdb. Priority:-1
extents:1 across:131064k
[42980169.290000] do_syscall_stub : ret = -12, offset = 548682067984,
data = 0000000060b16010
[42980169.290000] do_syscall_stub: syscall 9 failed, return value =
0xfffffffffffffff4, expected return value = 0x477a000
[42980169.290000] syscall parameters: 0x477a000 0x1000 0x7 0x11 0x3
0xad0c000
[42980169.290000] fix_range_common: failed, killing current process
Whilst trying to compile gcc (big beast) on a 64-bit UML instance.
Earlier it had failed and triggered OOM, which is why I added the swap,
now it may still not have enough (compilation crashed in a similar
manner) but this time there is no OOM message.
Any ideas what this is?
Cheers
Antoine
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2007-01-30 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 18:36 Antoine Martin [this message]
2007-01-30 19:41 ` [uml-devel] do_syscall_stub: syscall 9 failed Antoine Martin
2007-01-30 21:42 ` Jeff Dike
2007-01-31 9:18 ` Antoine Martin
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=45BF901F.40206@nagafix.co.uk \
--to=antoine@nagafix.co.uk \
--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 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).