From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Mitchell E Berger <mitchb@MIT.EDU>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: i686 vs i586 glibc segfault issue on 64-bit AMD Xen paravirt guests
Date: Wed, 02 Sep 2009 10:10:02 -0700 [thread overview]
Message-ID: <4A9EA6EA.2040304@goop.org> (raw)
In-Reply-To: <200909020810.n828AAUe002428@byte-me.mit.edu>
On 09/02/09 01:10, Mitchell E Berger wrote:
> I apologize for writing to you directly instead of through an officially
> supported channel.
No problem.
> I've filed a bug against glibc in Redhat's Bugzilla
> for an issue that only seems to surface on 64-bit Xen paravirt guests
> on AMD hosts. Filing this bug with the distro involved seemed to make
> sense, but thinking more about it, the bug may truly belong to Xen,
> and it seems wrong to cross-post a bug to two completely separate dev
> teams' bug trackers at the same time.
>
I think you're running into a known bug in current mainline Linux
kernels, in which 32-bit compat syscalls are not being handled properly
on AMD systems. The workaround is to boot with "vdso32=0" on the kernel
command line. Unfortunately nobody has taked the time to really work
out what's going on (I don't have an AMD system on hand, which makes it
awkward). It appears to be a problem with returning from a syscall,
rather than the syscall itself.
J
next parent reply other threads:[~2009-09-02 17:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909020810.n828AAUe002428@byte-me.mit.edu>
2009-09-02 17:10 ` Jeremy Fitzhardinge [this message]
2009-09-05 11:18 ` Errors when build 2.6.31-rc8 Boris Derzhavets
2009-09-05 11:24 ` Jun Koi
2009-09-05 11:31 ` Boris Derzhavets
2009-09-05 11:31 ` M A Young
2009-09-05 12:45 ` Boris Derzhavets
2009-09-05 13:03 ` djmagee
2009-09-05 15:48 ` Jeremy Fitzhardinge
2009-09-05 18:20 ` Boris Derzhavets
2009-09-06 16:56 ` Boris Derzhavets
2009-09-06 17:04 ` Re: [Xen-devel] " Boris Derzhavets
2009-09-06 17:10 ` [Fedora-xen] " Mr. Teo En Ming (Zhang Enming)
2009-09-06 18:37 ` Pasi Kärkkäinen
2009-09-07 4:49 ` Boris Derzhavets
2009-09-07 6:33 ` Re: [Xen-devel] " Boris Derzhavets
2009-09-07 6:57 ` [Fedora-xen] " Pasi Kärkkäinen
2009-09-07 7:25 ` Boris Derzhavets
2009-09-07 7:47 ` Boris Derzhavets
2009-09-07 10:36 ` Boris Derzhavets
2009-09-07 16:06 ` [Fedora-xen] " Boris Derzhavets
2009-09-07 21:11 ` [Fedora-xen] Re: Re: Errors when build 2.6.31-rc8 / compiles and works OK Pasi Kärkkäinen
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=4A9EA6EA.2040304@goop.org \
--to=jeremy@goop.org \
--cc=Christoph.Egger@amd.com \
--cc=mitchb@MIT.EDU \
--cc=xen-devel@lists.xensource.com \
/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.