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:26:01 +0200 [thread overview]
Message-ID: <44703229.20702@feuerpokemon.de> (raw)
In-Reply-To: <20060521091139.GB3468@taniwha.stupidest.org>
Chris Wedgwood wrote:
> On Sun, May 21, 2006 at 11:06:26AM +0200, dragoran wrote:
>
>
>> ok but what does this do and what happens to this apps?
>>
>
> my guess is they fallback to something else and still work, but it's
> only a guess
>
>
>> I did but got no reply yet
>>
>
> does it happen with a mainline kernel? a quick scan of the code shows
> that syscall is wired up
>
>
>
the weird thing is that it suddenly started to appear (no kernel update)
can it be prelink related?
next prev parent reply other threads:[~2006-05-21 9:26 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
2006-05-21 9:11 ` Chris Wedgwood
2006-05-21 9:26 ` dragoran [this message]
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=44703229.20702@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 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.