From: Jeremy Fitzhardinge Subject: Re: 32bit binaries on x86_64/Xen segfaults in syscall-vdso Date: Thu, 03 Sep 2009 15:06:32 -0700 Message-ID: <4AA03DE8.40706@goop.org> References: <20090830181637.GA7155@wavehammer.waldi.eu.org> <4AA02C57.30106@goop.org> <20090903220252.GA19309@wavehammer.waldi.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090903220252.GA19309@wavehammer.waldi.eu.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Bastian Blank , linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com, 544145@bugs.debian.org, Keir Fraser List-Id: xen-devel@lists.xenproject.org On 09/03/09 15:02, Bastian Blank wrote: > AFAIK only AMD support the syscall instruction, so yes it is an AMD > machine. And yes, disabling the only thing that make the glibc call this > instruction works around it. > The bug actually appears to be in xen_sysret32, ie the crash happens on the way out of the kernel. J