[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AA02C57.30106@goop.org>
Date: Thu, 03 Sep 2009 13:51:35 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Bastian Blank <waldi@...ian.org>, linux-kernel@...r.kernel.org,
xen-devel@...ts.xensource.com, 544145@...s.debian.org,
Keir Fraser <keir.fraser@...citrix.com>
Subject: Re: 32bit binaries on x86_64/Xen segfaults in syscall-vdso
On 08/30/09 11:16, Bastian Blank wrote:
> Hi folks
>
> I upgraded one of my 32bit chroots on a x86-64 machine runing under Xen
> lately. All binaries started to segfault. Some extensive checks later
> show the vdso as the culprit. Later I found <gpe0vg$j67$1@....gmane.org>
> with the same problem. The full story can be found in the Debian bug
> 544145[1].
>
> It happens with Linux 2.6.30 and 2.6.31-rc8 on Xen 3.2 and 3.4.
>
> For the tests I set the vdso to compat mode to have it loaded on a fixed
> location.
>
> The following program is a minimal test case for the vdso in compat
> mode, it can be compiled against dietlibc to minimize other effects.
>
Is this an AMD machine? Does booting with vdso32=0 on the kernel
command line work around the problem?
J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists