From: dragoran <dragoran@feuerpokemon.de>
To: Chris Wedgwood <cw@f00f.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IA32 syscall 311 not implemented on x86_64
Date: Sun, 21 May 2006 11:06:26 +0200 [thread overview]
Message-ID: <44702D92.3050607@feuerpokemon.de> (raw)
In-Reply-To: <20060521085015.GB2535@taniwha.stupidest.org>
Chris Wedgwood wrote:
> On Sun, May 21, 2006 at 10:35:28AM +0200, dragoran wrote:
>
>
>> IA32 syscall 311 from mozilla-xremote not implemented
>> IA32 syscall 311 from firefox-bin not implemented
>> IA32 syscall 311 from mplayer not implemented
>> what is syscall 311 and what effect does this have?
>>
>
> sys_set_robust_list, I think it's futex related
>
ok but what does this do and what happens to this apps?
>
>> I am using 2.6.16-1.2111_FC5 (2.6.16.14)
>>
>
> probably best to bitch to Red Hat about this
>
>
>
I did but got no reply yet
next prev parent reply other threads:[~2006-05-21 9:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 8:35 IA32 syscall 311 not implemented on x86_64 dragoran
2006-05-21 8:50 ` Chris Wedgwood
2006-05-21 9:06 ` dragoran [this message]
2006-05-21 9:11 ` Chris Wedgwood
2006-05-21 9:26 ` dragoran
2006-05-21 9:54 ` dragoran
2006-05-21 16:03 ` Dave Jones
2006-05-21 18:35 ` Ulrich Drepper
2006-05-21 18:50 ` Dave Jones
2006-05-21 18:56 ` Dave Jones
2006-05-21 19:38 ` Adrian Bunk
2006-05-21 19:47 ` Dave Jones
2006-05-22 0:17 ` [2.6 patch] x86_64: don't printk for unimplemented 32bit syscalls Adrian Bunk
2006-05-21 22:19 ` IA32 syscall 311 not implemented on x86_64 Andi Kleen
2006-05-21 22:28 ` Dave Jones
2006-05-21 22:37 ` Andi Kleen
2006-05-21 23:48 ` Dave Jones
2006-05-21 23:51 ` Chris Wedgwood
2006-05-22 5:59 ` dragoran
2006-05-22 12:41 ` Dave Jones
2006-05-23 14:30 ` Denis Vlasenko
2006-05-21 23:09 ` Andrew Morton
2006-05-21 19:35 ` Chris Wedgwood
2006-05-21 19:38 ` Dave Jones
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=44702D92.3050607@feuerpokemon.de \
--to=dragoran@feuerpokemon.de \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.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